Implement two-stage test execution with resolved dependencies - #20
Draft
Subramanian-K812 wants to merge 33 commits into
Draft
Subramanian-K812 wants to merge 33 commits into
Subramanian-K812 wants to merge 33 commits into
Conversation
Subramanian-K812
force-pushed
the
Subramanian-K812_test_execution_upgrade
branch
from
July 7, 2026 08:49
c9462ea to
fd3df76
Compare
* include release notes from v0.8 to main * update overall-status skill refs
Subramanian-K812
force-pushed
the
Subramanian-K812_test_execution_upgrade
branch
2 times, most recently
from
July 24, 2026 06:56
d293277 to
b6df34d
Compare
- use version working with `pull_request_target`
Subramanian-K812
force-pushed
the
Subramanian-K812_test_execution_upgrade
branch
2 times, most recently
from
August 3, 2026 03:26
e51b340 to
640dfee
Compare
Subramanian-K812
had a problem deploying
to
github-pages
August 3, 2026 07:03 — with
GitHub Actions
Failure
Subramanian-K812
had a problem deploying
to
github-pages
August 4, 2026 09:07 — with
GitHub Actions
Failure
Subramanian-K812
had a problem deploying
to
github-pages
August 4, 2026 10:16 — with
GitHub Actions
Failure
Subramanian-K812
had a problem deploying
to
github-pages
August 4, 2026 13:43 — with
GitHub Actions
Failure
Subramanian-K812
force-pushed
the
Subramanian-K812_test_execution_upgrade
branch
from
August 6, 2026 13:14
b960a5a to
a1b3db2
Compare
Subramanian-K812
had a problem deploying
to
github-pages
August 6, 2026 13:24 — with
GitHub Actions
Failure
Subramanian-K812
had a problem deploying
to
github-pages
August 7, 2026 06:52 — with
GitHub Actions
Failure
Subramanian-K812
had a problem deploying
to
github-pages
August 9, 2026 05:50 — with
GitHub Actions
Failure
Subramanian-K812
force-pushed
the
Subramanian-K812_test_execution_upgrade
branch
from
August 9, 2026 14:36
46125ba to
15090a8
Compare
Subramanian-K812
had a problem deploying
to
github-pages
August 10, 2026 02:04 — with
GitHub Actions
Failure
Subramanian-K812
had a problem deploying
to
github-pages
August 10, 2026 05:49 — with
GitHub Actions
Failure
Subramanian-K812
force-pushed
the
Subramanian-K812_test_execution_upgrade
branch
from
August 10, 2026 07:26
75e4c57 to
cb3fbcc
Compare
Subramanian-K812
had a problem deploying
to
github-pages
August 10, 2026 07:32 — with
GitHub Actions
Failure
Subramanian-K812
changed the base branch from
main
to
Subramanian-K812_resolve_override_mechanism
August 10, 2026 08:59
Subramanian-K812
changed the base branch from
Subramanian-K812_resolve_override_mechanism
to
main
August 11, 2026 10:15
Subramanian-K812
force-pushed
the
Subramanian-K812_test_execution_upgrade
branch
from
August 11, 2026 10:22
04a7a73 to
e816620
Compare
Subramanian-K812
had a problem deploying
to
github-pages
August 11, 2026 12:08 — with
GitHub Actions
Failure
…ipse-score#299) * feat(deps): add score_config_management to reference integration Pin score_config_management to 49f26b74 and add a patch (sourced from config_management PR#37) fixing the ProxyFuture API migration and removing SOCAL/component_tests targets not present in the OSS build. * ci: re-trigger CI * ci: re-trigger CI * feat: add config_management showcase * docs: mark config_management showcase as non functional yet * ci: re-trigger CI
Subramanian-K812
force-pushed
the
Subramanian-K812_test_execution_upgrade
branch
from
August 18, 2026 11:02
1a9a26e to
913bc97
Compare
Subramanian-K812
force-pushed
the
Subramanian-K812_test_execution_upgrade
branch
2 times, most recently
from
August 21, 2026 09:58
b22c037 to
a992474
Compare
* chore(deps): bump score_itf to v0.5.0 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. * feature_integration_tests/itf: pin dlt_config to container gateway 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: eclipse-score#307
Subramanian-K812
force-pushed
the
Subramanian-K812_test_execution_upgrade
branch
from
August 25, 2026 04:05
587dcbb to
35d83cd
Compare
…ure (eclipse-score#312) With that `bazel test --lockfile_mode=error --config=linux-x86_64 //feature_integration_tests/itf` works. `bazel --output_base=build/linux-x86_64 run --config linux-x86_64 //images/linux_x86_64:run` for which the bind mount of the Docker socket was added, works as well.
…ule's own stale .bazelrc
Especially the flaky QNX download fails a lot in CI and causes builds to fail. Let bazel retry a few times before failing the build. This is already in use at e.g. https://github.com/eclipse-score/communication/blob/f5a5612c870781c87d786a77d2361d3eaa80574b/.bazelrc#L16-L22
There is a new release. Lets make use of that.
Orchestrator was scheduled for removal in 0.8
…pinned score_docs_as_code version; use '//:docs' instead (same CLI, still accepts --github_user/--github_repo). (eclipse-score#329)
Subramanian-K812
force-pushed
the
Subramanian-K812_test_execution_upgrade
branch
from
September 4, 2026 03:46
8b5251f to
891e471
Compare
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
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.
DR-008 Option 4: two-stage test-execution workflow (PR 2 of 2)
Closes eclipse-score#264. This is the second of two PRs. It is stacked on PR 1
(
Subramanian-K812_resolve_override_mechanism, "resolved-dependency resolve + overridemechanism") — please review/merge that one first. Until PR 1 merges, this PR's base branch
is the PR-1 branch, so the diff shown here is only the test-execution delta.
What this PR does
Rewires the quality workflow to the DR-008 Option 4 flow, using the resolve + override
mechanism added in PR 1:
exports the resolved dependency set as the
stage1-resolved-depsartifact(
resolved_versions.json).known_good.json(target_sw) — never hardcoded.known_goodcommit, overridesits
MODULE.bazelwith the Stage-1 resolved set (PR 1's mechanism), and runs themodule's own unit tests + coverage as the Bazel root (
//...).release-tag test-report ZIP).
Files
Workflow & runners
.github/workflows/test_and_docs.yml— two-stage restructure (+ parallel docs build)scripts/quality_runners.py— module-context mode (--module-dir/--resolved-deps); callsResolvedDependencies.overwritescripts/aggregate_quality_report.py— new, consolidated reportscripts/known_good/list_modules.py— new, dynamic Stage-2 matrix fromknown_good.jsonscripts/integration_test.py— derive build targets fromknown_good.json(dropbuild_config.json)Resolved pins + their config ripple (kept together so the tree is self-consistent)
known_good.json— pin bumps (baselibs, lifecycle) + per-modulebazel_config+ lifecyclecode_root_path/extra_test_configbazel_common/score_basic_bazel.MODULE.bazel— flatbuffers bumpbazel_common/score_modules_target_sw.MODULE.bazel— regenerated (baselibs, lifecycle)MODULE.bazel.lock— updated lockrust_coverage/BUILD— lifecycle query//src/...→//score/...(layout moved by the bump)showcases/simple_lifecycle/BUILD— lifecycle bin path//src/...→//score/launch_manager.bazelrc— coverage atomic-gcov /-no-coverage; eb-aarch64 outline-atomics link fixKnown Stage 2 integration findings (surfaced, not fixed here)
The workflow correctly surfaces two module-owned integration failures caused by the
baselibs bump (
score_loggingCheckSizeValidstaleuint8_tassumption;score_persistencyto_stringonstd::string_view).