diff options
author | bors-servo <infra@servo.org> | 2023-07-04 13:51:28 +0200 |
---|---|---|
committer | GitHub <noreply@github.com> | 2023-07-04 13:51:28 +0200 |
commit | d931cf49aa4525d6f3d210e3966b503fec494934 (patch) | |
tree | 37068a6259db84bbb1d9cd3e3bca7dc5afdf73a1 /python/servo/build_commands.py | |
parent | dea28b51a2ed8487b462da59937a9a4c5ee7ec10 (diff) | |
parent | 69c830a6e0f11d6cdb3510d8bc3572eb8056d60d (diff) | |
download | servo-d931cf49aa4525d6f3d210e3966b503fec494934.tar.gz servo-d931cf49aa4525d6f3d210e3966b503fec494934.zip |
Auto merge of #29963 - mrobinson:run-unit-tests-when-using-try-platform, r=atbrakhi
When using "try-<platform>" trigger unit tests
There is currently no way to trigger unit tests using the bors-servo try
infrastructure. This change makes it so that using try-<platform>
triggers unit tests for that platform. This will be especially useful
when testing changes for Windows before trying to land them.
<!-- Please describe your changes on the following line: -->
---
<!-- Thank you for contributing to Servo! Please replace each `[ ]` by `[X]` when the step is complete, and replace `___` with appropriate data: -->
- [x] `./mach build -d` does not report any errors
- [x] `./mach test-tidy` does not report any errors
- [x] These changes do not require tests because they are just GitHub Actions changes.
<!-- Also, please make sure that "Allow edits from maintainers" checkbox is checked, so that we can help you if you get stuck somewhere along the way.-->
<!-- Pull requests that do not address these steps are welcome, but they will require additional verification as part of the review process. -->
Diffstat (limited to 'python/servo/build_commands.py')
0 files changed, 0 insertions, 0 deletions