Skip to content

Conversation

@paulquiring
Copy link
Contributor

@paulquiring paulquiring commented Feb 11, 2026

This pull request updates the Bazel build and module configuration to improve multi-platform support, streamline toolchain management, and update dependencies. The main changes include significant refactoring of .bazelrc and MODULE.bazel to support explicit platform and toolchain configurations for both Linux and QNX targets on x86_64 and arm64 architectures, as well as updates to workflow and dependency versions.

@github-actions
Copy link

github-actions bot commented Feb 11, 2026

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: ad27a2e5-ca7f-407b-8b87-ebcc712ef755
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: 
Loading: 0 packages loaded
    currently loading: 
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 (26 packages loaded, 9 targets configured)

Analyzing: target //:license-check (63 packages loaded, 9 targets configured)

Analyzing: target //:license-check (82 packages loaded, 16 targets configured)

Analyzing: target //:license-check (133 packages loaded, 2465 targets configured)

Analyzing: target //:license-check (134 packages loaded, 4853 targets configured)

Analyzing: target //:license-check (145 packages loaded, 6911 targets configured)

Analyzing: target //:license-check (145 packages loaded, 7267 targets configured)

Analyzing: target //:license-check (145 packages loaded, 7267 targets configured)

Analyzing: target //:license-check (148 packages loaded, 9277 targets configured)

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

INFO: Analyzed target //:license-check (150 packages loaded, 9527 targets configured).
[9 / 13] JavaToolchainCompileClasses external/rules_java+/toolchains/platformclasspath_classes; 0s disk-cache, processwrapper-sandbox
[11 / 13] JavaToolchainCompileBootClasspath external/rules_java+/toolchains/platformclasspath.jar; 0s disk-cache, processwrapper-sandbox
[12 / 13] 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: 28.338s, Critical Path: 2.66s
INFO: 13 processes: 9 internal, 3 processwrapper-sandbox, 1 worker.
INFO: Build completed successfully, 13 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
Copy link

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

@paulquiring paulquiring force-pushed the paulquiring/targets-and-toolchains branch from 3f4c927 to 9ac7bfe Compare February 11, 2026 12:49
@paulquiring paulquiring marked this pull request as ready for review February 11, 2026 13:12
@paulquiring
Copy link
Contributor Author

For the reviewers the failed check QNX8 Build / qnx-build / Build QNX target (pull_request_target) is because of a sporadic failure. One commit before this check passed no relevant files changed.

@pawelrutkaq
Copy link
Contributor

pawelrutkaq commented Feb 11, 2026

@paulquiring comments may be helpfull to fix qnx. Keep in mind that your chnages will only affect QNX CI only after merge so you shall test them locally .
IE bazel build --config x86_64-qnx //examples/... works
but bazel build --config x86_64-qnx //examples/rust_supervised_app does not

This means we need a collector in examples and mention it in CI/CD ?

@paulquiring
Copy link
Contributor Author

paulquiring commented Feb 12, 2026

@paulquiring comments may be helpfull to fix qnx. Keep in mind that your chnages will only affect QNX CI only after merge so you shall test them locally . IE bazel build --config x86_64-qnx //examples/... works but bazel build --config x86_64-qnx //examples/rust_supervised_app does not

This means we need a collector in examples and mention it in CI/CD ?

@pawelrutkaq I tested successfully locally and ensured that the examples are also build in the qnx workflow.

@pawelrutkaq
Copy link
Contributor

@paulquiring please fix CI

MODULE.bazel Outdated
remote = "https://github.com/eclipse-score/toolchains_rust.git",
module_name = "rules_rust",
remote = "https://github.com/pawelrutkaq/rules_rust.git", # To be fixed once rule_rust is in score bazel registry
commit = "d655071dfc8783bbdad4e27db349abd221ba170c",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use 293337fd6402ec3dfbeb8f2d589f38ad9124dadd

Copy link
Contributor

@pawelrutkaq pawelrutkaq left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fix red CI

@paulquiring paulquiring force-pushed the paulquiring/targets-and-toolchains branch from 33f4b69 to fa071ea Compare February 12, 2026 14:45
@paulquiring paulquiring deployed to workflow-approval February 12, 2026 14:45 — with GitHub Actions Active
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants