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
mach: Make ./mach try
a little friendlier
#31290
Conversation
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.
If we are doing this could we also make git commands quiet using --quiet
.
981903e
to
a4728b9
Compare
@sagudev Thanks for the review. I've made the changes you've requested. |
aa42d10
to
8e2842a
Compare
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.
Something is wrong: https://github.com/sagudev/servo/actions/runs/7828494013/job/21358490263#step:5:54
I ran mach try webgpu full
1. Move `./mach try` to `testing_commands.py which is a bit more consistent. 2. Make `./mach try` print out the remote name always and properly form the URL for ssh repositories. 3. Print out the try configuration matrix to make it more obvious what is being triggered remotely. 4. Better error handling. Print and error and exit if the remote isn't on GitHub and also clean up properly if something fails after making the temporary commit.
8e2842a
to
61ef0d5
Compare
It seems there was a bug when the commit message was more than a single line. I think I've fixed that now. |
Here's an example of the same test you ran: https://github.com/mrobinson/servo/actions/runs/7828643293/job/21358950457 |
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.
Thanks for polishing mach try
Sure thing. Thanks for implementing it originally. It's really useful! |
1. Move `./mach try` to `testing_commands.py which is a bit more consistent. 2. Make `./mach try` print out the remote name always and properly form the URL for ssh repositories. 3. Print out the try configuration matrix to make it more obvious what is being triggered remotely. 4. Better error handling. Print and error and exit if the remote isn't on GitHub and also clean up properly if something fails after making the temporary commit.
./mach try
to `testing_commands.py which is a bit moreconsistent.
./mach try
print out the remote name always and properlyform the URL for ssh repositories.
what is being triggered remotely.
on GitHub and also clean up properly if something fails after making
the temporary commit.
./mach build -d
does not report any errors./mach test-tidy
does not report any errors