-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Take revision into account in non-incremental-mode // incremental
tests
#106053
Conversation
(rustbot has picked a reviewer for you, use r? to override) |
@bors r+ rollup=iffy |
☀️ Test successful - checks-actions |
Finished benchmarking commit (62cc869): comparison URL. Overall result: no relevant changes - no action needed@rustbot label: -perf-regression Instruction countThis benchmark run did not return any relevant results for this metric. Max RSS (memory usage)This benchmark run did not return any relevant results for this metric. CyclesThis benchmark run did not return any relevant results for this metric. |
…r=Mark-Simulacrum Take revision into account in non-incremental-mode `// incremental` tests A UI test I added in rust-lang#105983 confusingly [failed](rust-lang#106031 (comment)) in a merge because two different revisions raced with each other for the same incremental directory for a (non-incremental-mode, i.e. `src/test/ui`) UI test. Let's take the revision name into account when generating an incremental directory so that other UI tests that combine `// incremental` and `// revisions` won't race and cause possible flakiness in CI.
A UI test I added in #105983 confusingly failed in a merge because two different revisions raced with each other for the same incremental directory for a (non-incremental-mode, i.e.
src/test/ui
) UI test.Let's take the revision name into account when generating an incremental directory so that other UI tests that combine
// incremental
and// revisions
won't race and cause possible flakiness in CI.