ITF integration

[MaciejKaszynski]

This adds a framework to run component tests on a QEMU target using ITF

• Makes native test explicit to invoke by using --config=host .
• Currently copied and pasted the QEMU image definition from reference integration however this should be moved using os_images if that becomes the standard.

Note: This PR creates interfaces that looks like what the new ITF will be with changes from eclipse-score/itf#46 So it should be easy to replace when ITFs refactor is stable.

[github-actions]

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run //:license-check

Status: ⚠️ Needs Review

Click to expand output

[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.4.2) and connecting to it...
INFO: Invocation ID: 8a10dfe1-8a46-42fd-aab0-99f684cb6756
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
WARNING: For repository 'score_rust_policies', the root module requires module version score_rust_policies@0.0.3, but got score_rust_policies@0.0.5 in the resolved dependency graph. Please update the version in your MODULE.bazel or set --check_direct_dependencies=off
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)
Analyzing: target //:license-check (1 packages loaded, 0 targets configured)

Analyzing: target //:license-check (65 packages loaded, 10 targets configured)

Analyzing: target //:license-check (98 packages loaded, 24 targets configured)

Analyzing: target //:license-check (149 packages loaded, 2659 targets configured)

Analyzing: target //:license-check (157 packages loaded, 5265 targets configured)

Analyzing: target //:license-check (162 packages loaded, 5314 targets configured)

Analyzing: target //:license-check (162 packages loaded, 5314 targets configured)

Analyzing: target //:license-check (167 packages loaded, 7329 targets configured)

Analyzing: target //:license-check (168 packages loaded, 9927 targets configured)

Analyzing: target //:license-check (169 packages loaded, 9935 targets configured)

Analyzing: target //:license-check (169 packages loaded, 9935 targets configured)

Analyzing: target //:license-check (169 packages loaded, 9935 targets configured)

INFO: Analyzed target //:license-check (170 packages loaded, 10061 targets configured).
[12 / 16] JavaToolchainCompileClasses external/rules_java+/toolchains/platformclasspath_classes; 0s disk-cache, processwrapper-sandbox ... (2 actions running)
[14 / 16] JavaToolchainCompileBootClasspath external/rules_java+/toolchains/platformclasspath.jar; 0s disk-cache, processwrapper-sandbox
[15 / 16] Building license.check.license_check.jar (); 0s disk-cache, multiplex-worker
INFO: Found 1 target...
Target //:license.check.license_check up-to-date:
  bazel-bin/license.check.license_check
  bazel-bin/license.check.license_check.jar
INFO: Elapsed time: 33.880s, Critical Path: 2.68s
INFO: 16 processes: 12 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 16 total actions
INFO: Running command line: bazel-bin/license.check.license_check ./formatted.txt <args omitted>
usage: org.eclipse.dash.licenses.cli.Main [-batch <int>] [-cd <url>]
       [-confidence <int>] [-ef <url>] [-excludeSources <sources>] [-help] [-lic
       <url>] [-project <shortname>] [-repo <url>] [-review] [-summary <file>]
       [-timeout <seconds>] [-token <token>]

[github-actions]

The created documentation from the pull request is available at: docu-html

[pawelrutkaq]

would not mix test what shall be imho UT with integration tests. Also for linux, itf can simply use Docker as in reference integration.

[pawelrutkaq]

I would ask @ltekieli and @PiotrKorkus to have a look. Nevethless I think we shall push forward os_images to here only use an image from there and setup startup script/small build addons, and not need to copy-paste boilerplate scripts.

[PiotrKorkus]

Nevethless I think we shall push forward os_images to here only use an image from there and setup startup script/small build addons, and not need to copy-paste boilerplate scripts.

I agree. For now I would either put those tests in reference_integration repo or use os_iamges here. Otherwise we will introduce a lot of unnecessary files which should be dependencies not a part of lifecycle.

[MaciejKaszynski]

Nevethless I think we shall push forward os_images to here only use an image from there and setup startup script/small build addons, and not need to copy-paste boilerplate scripts.

I agree. For now I would either put those tests in reference_integration repo or use os_iamges here. Otherwise we will introduce a lot of unnecessary files which should be dependencies not a part of lifecycle.

Yep the end goal is to use the os_images in the end, this is why I made the test target easily changeable by just changing the target in https://github.com/eclipse-score/lifecycle/pull/75/changes#diff-c7986b2ae7b8b3c16507ee583c9a8cfaeff6e886bfb138be0a654b22d721191dR26 but this will be used until the os images has the qnx.

(there is a PR going on right nowhttps://github.com/eclipse-score/os_images/pull/5 however there are issues with the qnx SDP and we need some action from qnx team https://sdvworkinggroup.slack.com/archives/C0AEB5M5FUN/p1772461625738719)