Skip to content

cryptoki: fix QNX build and tests - #196

Open
OliverHeilwagen wants to merge 1 commit into
eclipse-score:mainfrom
etas-contrib:fix_qnx_build_and_test_issues
Open

cryptoki: fix QNX build and tests#196
OliverHeilwagen wants to merge 1 commit into
eclipse-score:mainfrom
etas-contrib:fix_qnx_build_and_test_issues

Conversation

@OliverHeilwagen

Copy link
Copy Markdown
Contributor
  • Update score crates and related Bazel dependencies for QNX-compatible Rust platform resolution, regenerating the Bazel module lockfile.
  • Pin libc to the QNX-compatible 0.2.186 release.
  • Select the appropriate C++ runtime linker flags for Linux and QNX builds.
  • Use TEST_TMPDIR for QNX integration-test storage paths instead of /tmp.
  • Add a QNX-specific mtime workaround for token-object persistence tests.
  • Move optional user Bazel configuration loading after repository defaults.

@OliverHeilwagen

OliverHeilwagen commented Aug 27, 2026

Copy link
Copy Markdown
Contributor Author

@ShoroukRamzy I noticed that the former fix was skipping elements, now cryptoki lib is build and tests are running under QNX. Can you please check if my changes are valid?

@github-actions

github-actions Bot commented Aug 27, 2026

Copy link
Copy Markdown
Contributor

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //:license-check

Status: ⚠️ Needs Review

Click to expand output
[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.6.0) and connecting to it...
INFO: Invocation ID: 48856090-c83f-4bd5-85a6-b062b8bcbddb
Computing main repo mapping: 
Computing main repo mapping: 
DEBUG: Rule 'score_baselibs_rust+' indicated that a canonical reproducible form can be obtained by modifying arguments integrity = "sha256-4kzcXcvGi9xBEEnrPOiSEvteITZMPKmK3MNgJXQIGtY="
DEBUG: Repository score_baselibs_rust+ instantiated at:
  <builtin>: in <toplevel>
Repository rule http_archive defined at:
  /home/runner/.bazel/external/bazel_tools/tools/build_defs/repo/http.bzl:431:31: in <toplevel>
DEBUG: Rule 'score_logging+' indicated that a canonical reproducible form can be obtained by modifying arguments integrity = "sha256-/Q5+YfLkbMpz5PfvOkNS7qA3ehzth4emFhTcsk4q3zQ="
DEBUG: Repository score_logging+ instantiated at:
  <builtin>: in <toplevel>
Repository rule http_archive defined at:
  /home/runner/.bazel/external/bazel_tools/tools/build_defs/repo/http.bzl:431:31: in <toplevel>
DEBUG: Rule 'abseil-cpp+' indicated that a canonical reproducible form can be obtained by modifying arguments integrity = "sha256-m3oGQwXp/ZTRJP+mzDWFkutCtdpYj7TgfQklSqQAhts="
DEBUG: Repository abseil-cpp+ instantiated at:
  <builtin>: in <toplevel>
Repository rule http_archive defined at:
  /home/runner/.bazel/external/bazel_tools/tools/build_defs/repo/http.bzl:431:31: in <toplevel>
Computing main repo mapping: 
DEBUG: Rule 'protobuf+' indicated that a canonical reproducible form can be obtained by modifying arguments integrity = "sha256-w6Cp7OiTLjHDtzbi2xixxC5wcM2biBOIsm0BqnHiTKI="
DEBUG: Repository protobuf+ instantiated at:
  <builtin>: in <toplevel>
Repository rule http_archive defined at:
  /home/runner/.bazel/external/bazel_tools/tools/build_defs/repo/http.bzl:431:31: in <toplevel>
Computing main repo mapping: 
DEBUG: Rule 'grpc+' indicated that a canonical reproducible form can be obtained by modifying arguments integrity = "sha256-CvN7gAlTEwtHwHW1ZoPuYL3D7aPDf8YAQZP1tWl1ggQ="
DEBUG: Repository grpc+ instantiated at:
  <builtin>: in <toplevel>
Repository rule http_archive defined at:
  /home/runner/.bazel/external/bazel_tools/tools/build_defs/repo/http.bzl:431:31: in <toplevel>
Computing main repo mapping: 
Computing main repo mapping: 
Loading: 
Loading: 1 packages loaded
Loading: 1 packages loaded
    currently loading: 
Loading: 1 packages loaded
    currently loading: 
Loading: 1 packages loaded
    currently loading: 
Loading: 1 packages loaded
    currently loading: 
WARNING: Target pattern parsing failed.
ERROR: Skipping '//:license-check': no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/inc_security_crypto/inc_security_crypto/BUILD
ERROR: no such target '//:license-check': target 'license-check' not declared in package '' defined by /home/runner/work/inc_security_crypto/inc_security_crypto/BUILD
INFO: Elapsed time: 13.344s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

@OliverHeilwagen
OliverHeilwagen force-pushed the fix_qnx_build_and_test_issues branch from 55a0de9 to 29f23fb Compare August 27, 2026 08:35
@OliverHeilwagen
OliverHeilwagen deployed to workflow-approval August 27, 2026 08:36 — with GitHub Actions Active
@OliverHeilwagen
OliverHeilwagen deployed to workflow-approval August 27, 2026 08:36 — with GitHub Actions Active
@github-actions

Copy link
Copy Markdown
Contributor

Documentation preview for this pull request is available at:
pr-196: https://eclipse-score.github.io/inc_security_crypto/pr-196/

- Update score crates and related Bazel dependencies for QNX-compatible
  Rust platform resolution, regenerating the Bazel module lockfile.
- Pin libc to the QNX-compatible 0.2.186 release.
- Select the appropriate C++ runtime linker flags for Linux and QNX builds.
- Use TEST_TMPDIR for QNX integration-test storage paths instead of /tmp.
- Add a QNX-specific mtime workaround for token-object persistence tests.
- Move optional user Bazel configuration loading after repository defaults.
@OliverHeilwagen
OliverHeilwagen force-pushed the fix_qnx_build_and_test_issues branch from 825813b to bca00cd Compare August 27, 2026 12:04
@OliverHeilwagen
OliverHeilwagen deployed to workflow-approval August 27, 2026 12:04 — with GitHub Actions Active
@OliverHeilwagen
OliverHeilwagen deployed to workflow-approval August 27, 2026 12:04 — with GitHub Actions Active
@ShoroukRamzy

Copy link
Copy Markdown
Contributor

@ShoroukRamzy I noticed that the former fix was skipping elements, now cryptoki lib is build and tests are running under QNX. Can you please check if my changes are valid?

Thank you for the PR @OliverHeilwagen, I will give my feedback soon.

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.

2 participants