chore(deps): bump score_itf to v0.5.0 - #307
Merged
Merged
Conversation
Update score_itf commit from bf5294d (v0.3.0) to 802e018 (v0.5.0) in known_good.json and regenerate the derived files via scripts/known_good/update_module_from_known_good.py. The consumed itf API (py_itf_test, plugins=, @score_itf//score/itf/plugins:*) is already on the 0.2+ layout, so no BUILD or Python changes are required.
antonkri
requested review from
AlexanderLanin,
FScholPer,
MaximilianSoerenPollak,
PiotrKorkus,
dcalavrezo-qorix,
lurtz,
nradakovic,
opajonk and
pawelrutkaq
as code owners
August 21, 2026 10:00
|
The created documentation from the pull request is available at: docu-html |
score_itf 0.5.0 (commit bb3a788 "docker: Create per-container bridge network") makes the Docker plugin create a dedicated bridge network score_itf_<rand> per container instead of joining the default docker0 bridge. As a consequence the hardcoded 172.17.0.1 host_ip/target_ip in feature_integration_tests/configs/dlt_config_x86_64.json no longer matches the container's actual gateway, so DLT UDP multicast (239.255. 42.99) is never delivered to the host-side dlt-receive and the two DLT tests fail with 'DLT TRACE FILE IS EMPTY'. Add a local conftest.py that overrides the session-scoped dlt_config fixture and pins host_ip/target_ip to target.get_gateway() when the target exposes it (Docker). QEMU targets (QNX) do not expose get_gateway; the static IPs from dlt_config_qnx_x86_64.json continue to be used unchanged there. Wire the new conftest.py into the py_itf_test data so it is present in the Bazel test sandbox next to the test sources. Refs: #307
lurtz
approved these changes
Aug 21, 2026
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
2 participants
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.
What
Bump
score_itffrom commitbf5294d(v0.3.0) to802e018(v0.5.0) inknown_good.jsonand regenerate the derived files viascripts/known_good/update_module_from_known_good.py.Why
Track the latest released ITF version (
v0.5.0, published 2026-07-10).Changes
known_good.json: bumptooling.score_itf.hash+ refresh timestampbazel_common/score_modules_tooling.MODULE.bazel: regenerated (new commit + timestamp)bazel_common/score_modules_target_sw.MODULE.bazel,rust_coverage/BUILD: regenerated (timestamp only, kept in sync with the generator's output)Compatibility
The ITF surface consumed by this repo (
py_itf_test,plugins=,@score_itf//score/itf/plugins:*) is already on the 0.2+ layout, so no BUILD or Python changes are required.Verification
bazel mod deps score_itfresolves cleanly against v0.5.0.bazel build //feature_integration_tests/itf:itfprogresses through all ITF-related loading and analysis without errors.