fix: QEMU: return correct PID for process under test - #127
Open
danth wants to merge 1 commit into
Open
Conversation
danth
added a commit
to etas-contrib/score_lifecycle
that referenced
this pull request
Aug 3, 2026
danth
added a commit
to etas-contrib/score_lifecycle
that referenced
this pull request
Aug 3, 2026
danth
added a commit
to etas-contrib/score_lifecycle
that referenced
this pull request
Aug 3, 2026
danth
added a commit
to etas-contrib/score_lifecycle
that referenced
this pull request
Aug 3, 2026
danth
added a commit
to etas-contrib/score_lifecycle
that referenced
this pull request
Aug 4, 2026
MaciejKaszynski
pushed a commit
to eclipse-score/lifecycle
that referenced
this pull request
Aug 4, 2026
* Run integration tests on QNX via QEMU * Avoid `junitparser` dependency in tests Our Bazel toolchain for Python does not work with QNX, so we need to use built-in libraries to parse the results instead. * Mark some build targets as incompatible with QNX * Work around QNX unit test flags breaking integration tests With proper use of Bazel platforms rather than configs, I think it would be possible to do this in a much cleaner way. However that would require deeper changes across our codebase and possibly in the test frameworks as well. * Work around eclipse-score/itf#125 * Mention QEMU tests in README * Work around eclipse-score/itf#127 * Always cleanly skip incompatible tests This decouples the choice of Docker/QEMU/native from the choice of Linux/QNX. Then, targets are marked as compatible only if the current combination is known to work. The existing bazelrc shortcuts are updated to set the new flags, so what you actually type at the command line has not changed. The benefit is that running QNX tests with the wrong shortcut will now just list them as skipped, rather than giving a cryptic error.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In lifecycle we use a signal to shut down our daemon gracefully at the end of each test.
Currently:
This makes it difficult to send the signal as we would have to detect which plugin is in use, then on QEMU run more commands to figure out the PID of the child.
This tiny change makes QEMU plugin behave the same as the Docker plugin in this regard.