-
Notifications
You must be signed in to change notification settings - Fork 548
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
Remove peer reliability temp #10159
Remove peer reliability temp #10159
Conversation
@@ -20,6 +20,7 @@ let dirtyWhen = [ | |||
S.strictlyStart (S.contains "buildkite/src/Command/MinaArtifact"), | |||
S.exactly "buildkite/scripts/build-artifact" "sh", | |||
S.exactly "buildkite/scripts/connect-to-mainnet-on-compatible" "sh", | |||
S.strictlyStart (S.contains "buildkite/src/Jobs/Test/TestnetIntegrationTest"), |
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.
I think "buildkite/src/Jobs/Test" is probably a better filter here as most testing jobs depend on these artifacts (or individually list TestnetIntegrationTests, ReplayerTest, DeployTestnetAndDestroy, MigratedIntegrationTests, ConnectToTestnet). Similarly, "buildkite/src/Command" does not depend on these jobs but has the potential to break them, so they should be dirty.
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.
more correctly long term the answer is probably more folders for these jobs to better reflect dependency, like if these were all under "buildkite/src/Jobs/Test/Integration/" to separate from unit tests / static analysis.
temporarily remove the peer reliability test