compile_and_test_for_boards: Add no-compile flag#19817
compile_and_test_for_boards: Add no-compile flag#19817bors[bot] merged 1 commit intoRIOT-OS:masterfrom
Conversation
MrKevinWeiss
added
the
CI: skip compile test
MrKevinWeiss
force-pushed
the
pr/skipcompile
branch
2 times, most recently
from
13dcd27 to
97bad96
Compare
Since we have a no-test flag that prevents executing tests, I think a no-compile flag is a nice compliment. Why? Well if I want to use this script for running multiple boards at the same time, RIOT is not so great handling parallel compile steps with conflicts on lockfiles happening, mostly due to packages. With this I can compile a list of boards sequentially, then flash and run tests in parallel, skipping the compile step.
MrKevinWeiss
force-pushed
the
pr/skipcompile
branch
from
97bad96 to
d12d592
Compare
|
I reduced the usage string test requirement to handle difference in newlines/spaces, this should allow us to make it look pretty while still checking things are up-to-date. I also added a negative test to prove it is actually checking it. Reproducing the usage string in the docstring is also a bit redundant I find but that is another story. |
benpicco
added
the
CI: ready for build
MrKevinWeiss
removed
the
CI: skip compile test
|
bors try |
|
I am just using this to check some CI issues. |
|
bor try |
|
bors try |
tryAlready running a review |
tryBuild succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
|
bors try |
tryBuild succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
|
bors merge |
|
Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
|
Thanks! |
3 participants
Contribution description
Since we have a no-test flag that prevents executing tests, I think a no-compile flag is a nice compliment. Why? Well if I want to use this script for running multiple boards at the same time, RIOT is not so great handling parallel compile steps with conflicts on lockfiles happening, mostly due to packages. With this I can compile a list of boards sequentially, then flash and run tests in parallel, skipping the compile step.
Testing procedure
Run the following once to compile and clean:
Then try to run without the compile step and it should fail due to lack of the binary
Issues/PRs references