-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix the workspace integration tests that need username in DB first #9628
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: JenTing Hsiao <[email protected]>
Signed-off-by: JenTing Hsiao <[email protected]>
Git config --user.name and git config --user.email, otherwise, git commit would fail. Signed-off-by: JenTing Hsiao <[email protected]>
jenting
force-pushed
the
fix-TestGitActions
branch
from
May 1, 2022 07:52
9799b3a
to
58cdcd7
Compare
jenting
changed the title
Fix broken integration test test TestGitActions
Fix the workspace integration tests that need username in DB first
May 1, 2022
@jenting I couldn't run the following command to review this PR😭 Do you know how to fix it? gitpod /workspace/gitpod (fix-TestGitActions) $ werft run github -f .werft/workspace-integration-tests-startup-cron.yaml
Error: rpc error: code = Internal desc = cannot resolve request: "rpc error: code = InvalidArgument desc = ref is empty"
tip: There seems to be a problem with your werft installation - please get in contact with whoever is operating this installation. |
Oops, command typo. Should be werft run github -j .werft/workspace-integration-tests-startup-cron.yaml |
utam0k
approved these changes
May 2, 2022
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
roboquat
added
deployed: workspace
Workspace team change is running in production
deployed
Change is completely running in production
labels
May 4, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
deployed: workspace
Workspace team change is running in production
deployed
Change is completely running in production
release-note-none
size/L
team: workspace
Issue belongs to the Workspace team
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fix the workspace integration tests that need a username in DB first
Related Issue(s)
Fixes #9627
How to test
Ref werft job result
Release Notes
Documentation
N/A