ci: fix murdock tests after dwq change #20268
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
kaspar030
added
Type: bug
kaspar030
added
CI: ready for build
kaspar030
force-pushed
the
fix_murdock_tests_file
branch
from
ad32d49 to
8f43398
Compare
kaspar030
added
the
CI: ready for build
kaspar030
force-pushed
the
fix_murdock_tests_file
branch
from
8f43398 to
c84400e
Compare
|
Test failure was IMO unrelated: https://ci.riot-os.org/details/07c9eaaf954c48a29f29315634954c10/tests |
kaspar030
added
CI: ready for build
maribu
approved these changes
Jan 17, 2024
benpicco
approved these changes
Jan 17, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contribution description
With RIOT-OS/riotdocker#237 I broke murdock tests on the pifleet. This should fix them.
edit
So what happened here is that dwq dropped support for specifying the target path of a file sent along with a job.
That feature might come back.
In the meantime, this PR makes BINDIR match on compiler (mobi*, breeze, ...) and tester (pifleet).
(I've piggybacked a commit that makes the tester fail early if flashing returned an error code.)
Testing procedure
Issues/PRs references