Repository navigation
ci: run a fixed list of modules in the GraalVM nightly #15088
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,7 @@ | ||
| # Format: //devtools/kokoro/config/proto/build.proto | ||
|
|
||
| env_vars: { | ||
| key: "JOB_NUMBER" | ||
| value: "1" | ||
| } | ||
| # Kokoro reads the build config that is named after the job. All settings are in | ||
| # common.cfg. | ||
| # | ||
| # Each nightly job has this one child job. Kokoro retries a child job that it | ||
| # could not build, including one that never started, from the parent job. |
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,6 +1,7 @@ | ||
| # Format: //devtools/kokoro/config/proto/build.proto | ||
|
|
||
| env_vars: { | ||
| key: "JOB_NUMBER" | ||
| value: "1" | ||
| } | ||
| # Kokoro reads the build config that is named after the job. All settings are in | ||
| # common.cfg. | ||
| # | ||
| # Each nightly job has this one child job. Kokoro retries a child job that it | ||
| # could not build, including one that never started, from the parent job. |
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
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.
Using
grep -qin a pipeline (find ... | grep -q .) whenpipefailis enabled can lead to flaky test failures. As soon asgrep -qfinds a match, it exits successfully and closes the pipe. Iffindattempts to write further output, it will receive aSIGPIPE(exit status 141), causing the entire pipeline to fail with a non-zero exit code underpipefail.Additionally,
-quitis a GNUfindextension and is not portable (e.g., it will fail on macOS/BSDfindunless GNUfindis explicitly installed).To make this check robust, portable, and safe under
pipefail, you can use command substitution instead of a pipeline to check if any matching files exist.