-
Notifications
You must be signed in to change notification settings - Fork 13k
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
maintain the given order on step execution #127602
Conversation
This comment has been minimized.
This comment has been minimized.
4abd67f
to
45009fb
Compare
I will re-work on this later again. @rustbot author |
104e3f6
to
774af29
Compare
Simplified the solution without refactoring the entire internals about path resolution (which was the case initially). @rustbot ready |
I'm a bit confused by the original issue. It used |
That's not quite right. The logic below handles the step executions most of the time. The one you linked is supposed to handle specific test paths (like To debug the ordering, you can run this command:
and compare the CLI order to the executed steps. |
Ah, I see, thanks. I guess that I usually run specific test paths, so I didn't think of this. I'll test it locally. |
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.
This is the first time I actually saw dry run being useful :) However it was in the mode where it was enabled manually (--dry-run
), I'd still get rid of the double execution of all steps 😆
Previously step execution disregarded the CLI order and this change executes the given steps in the order specified on CLI. For example, running `x $kind a b c` will execute `$kind` step for `a`, then `b`, then `c` crates in the specified order. Signed-off-by: onur-ozkan <work@onurozkan.dev>
774af29
to
4ad753a
Compare
@bors r=Kobzol |
☀️ Test successful - checks-actions |
Finished benchmarking commit (3de0a7c): 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. Binary sizeThis benchmark run did not return any relevant results for this metric. Bootstrap: 768.259s -> 768.642s (0.05%) |
Previously step execution disregarded the CLI order and this change executes the given steps in the order specified on CLI.
For example, running
x $kind a b c
will execute$kind
step fora
, thenb
, thenc
crates in the specified order.Fixes #126165
cc @matthiaskrgr