-
Notifications
You must be signed in to change notification settings - Fork 211
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
[Merged by Bors] - CI for New System Tests #3121
Closed
Closed
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
tryBuild succeeded: |
bors try |
tryBuild succeeded: |
bors try |
tryBuild succeeded: |
dshulyak
approved these changes
Mar 16, 2022
moshababo
approved these changes
Mar 16, 2022
bors merge |
bors bot
pushed a commit
that referenced
this pull request
Mar 16, 2022
This PR is to run the new system tests in the CI. The new system tests are already merged to develop. It should run the tests during `bors try` and `bors merge` in our GCP kubernetes infra. Tasks: - [x] It builds the go-spacemesh and system tests docker images and pushes to dockerhub - [x] It runs the tests in a k8s cluster hosted on GCP - [x] After running the tests it prints the tests results and cleans all pods - [x] Run system tests only when bors try or bors merge is invoked - [x] Fail the CI when tests fail (read the status of kubernetes pod) Co-authored-by: Narayan Prusty <7037606+narayanprusty@users.noreply.github.com>
Build failed: |
bors merge |
bors bot
pushed a commit
that referenced
this pull request
Mar 17, 2022
This PR is to run the new system tests in the CI. The new system tests are already merged to develop. It should run the tests during `bors try` and `bors merge` in our GCP kubernetes infra. Tasks: - [x] It builds the go-spacemesh and system tests docker images and pushes to dockerhub - [x] It runs the tests in a k8s cluster hosted on GCP - [x] After running the tests it prints the tests results and cleans all pods - [x] Run system tests only when bors try or bors merge is invoked - [x] Fail the CI when tests fail (read the status of kubernetes pod) Co-authored-by: Narayan Prusty <7037606+narayanprusty@users.noreply.github.com>
bors try |
Pull request successfully merged into develop. Build succeeded: |
bors
bot
changed the title
CI for New System Tests
[Merged by Bors] - CI for New System Tests
Mar 17, 2022
tryBuild failed: |
dshulyak
added a commit
to dshulyak/go-spacemesh
that referenced
this pull request
Mar 27, 2022
* develop: nuke tests and outdated utilities (spacemeshos#3154) add duplicate TX check and some cleanup (spacemeshos#3148) Fix Gcloud Setup for Releases (spacemeshos#3151) Use Exit Code to Find Tests Status (spacemeshos#3146) CI for New System Tests (spacemeshos#3121)
This pull request was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR is to run the new system tests in the CI. The new system tests are already merged to develop. It should run the tests during
bors try
andbors merge
in our GCP kubernetes infra.Tasks: