-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
build: fix bazel invocation of stress in github-pull-request-make #72379
Conversation
Every run of the stress and stressrace bazel CI jobs were failing with: [17:16:00][Run stress tests] /bin/bash: stress: command not found I haven't dug into the Git history enough to know why this was working before. Rather, I've just copied what the `dev` tool does for me and checked that the constructed `bazci` command does in fact work. Release note: None
This adds the ability to feed in package and test names via an environment variable rather than depending on GitHub. It also allows one to force a bazel build. I found this helpful when debugging a problem with this command. Release note: None
69f4fed
to
1940285
Compare
@@ -254,13 +303,13 @@ func main() { | |||
args = append(args, "--test_arg=-test.timeout", fmt.Sprintf("--test_arg=%s", timeout)) | |||
// Give the entire test 1 more minute than the duration to wrap up. | |||
args = append(args, fmt.Sprintf("--test_timeout=%d", int((duration+1*time.Minute).Seconds()))) | |||
// NB: stress and bazci are expected to be put in `PATH` by the caller. | |||
args = append(args, "--run_under", fmt.Sprintf("stress -stderr -maxfails 1 -maxtime %s -p %d", duration, parallelism)) | |||
args = append(args, "--run_under", fmt.Sprintf("%s -stderr -maxfails 1 -maxtime %s -p %d", bazelStressTarget, duration, parallelism)) |
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.
For reviewers, this is the important bit.
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.
Thank you! :)
no problemo, thanks for the review! The CI failures are all unrelated. bors r=rickystewart |
Build failed (retrying...): |
Build succeeded: |
Every run of the stress and stressrace bazel CI jobs were failing
with:
I haven't dug into the Git history enough to know why this was working
before. Rather, I've just copied what the
dev
tool does for me andchecked that the constructed
bazci
command does in fact work.Fixes #72321