Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

Don't run cargo-check-benches for master based downstream staging pipelines #12233

Merged
merged 1 commit into from
Sep 12, 2022

Conversation

rcny
Copy link
Contributor

@rcny rcny commented Sep 9, 2022

Running downstream pipelines for master with images other than the current production one could result in incorrect node-bench results and node-bench-regression-guard's false positives. This behavior could happen because of e.g. different stable Rust toolchains in these images. Any successful cargo-check-benches job (i.e. it doesn't matter if it was run with e.g. ci-linux:staging or ci-linux:production) will upload its results and this can result in incorrect performance regression detections.

@rcny rcny added A0-please_review Pull request needs code review. B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders. labels Sep 9, 2022
@rcny rcny requested a review from ggwpez September 9, 2022 21:40
@rcny rcny requested a review from a team as a code owner September 9, 2022 21:40
@rcny rcny self-assigned this Sep 9, 2022
@paritytech-ci paritytech-ci requested a review from a team September 12, 2022 16:19
@rcny rcny merged commit 7cb78ff into master Sep 12, 2022
@rcny rcny deleted the vi-no-check-benches-on-master-downstreams branch September 12, 2022 17:48
ark0f pushed a commit to gear-tech/substrate that referenced this pull request Feb 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
A0-please_review Pull request needs code review. B0-silent Changes should not be mentioned in any release notes C1-low PR touches the given topic and has a low impact on builders.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants