Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

s390x artifact build jobs failing #568

Closed
fitzthum opened this issue Nov 8, 2024 · 1 comment · Fixed by #571
Closed

s390x artifact build jobs failing #568

fitzthum opened this issue Nov 8, 2024 · 1 comment · Fixed by #571

Comments

@fitzthum
Copy link
Member

fitzthum commented Nov 8, 2024

We're running into this error

#14 101.2 error: failed to run custom build command for `tss-esapi-sys v0.5.0`
#14 101.2 
#14 101.2 Caused by:
#14 101.2   process didn't exit successfully: `/usr/src/attestation-service/target/release/build/tss-esapi-sys-e17dce3a146ba30a/build-script-build` (exit status: 101)
#14 101.2   --- stderr
#14 101.2   thread 'main' panicked at /usr/local/cargo/registry/src/index.crates.io-d11c229612889eed/tss-esapi-sys-0.5.0/build.rs:35:17:
#14 101.2   Compilation target (architecture, OS) tuple (s390x, linux) is not part of the supported tuples. Please compile with the "generate-bindings" feature or add support for your platform :)
#14 101.2   note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
#14 101.2 warning: build failed, waiting for other jobs to finish...
#14 140.4 error: failed to compile `attestation-service v0.1.0 (/usr/src/attestation-service/attestation-service)`, intermediate artifacts can be found at `/usr/src/attestation-service/target`.
#14 140.4 To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.
#14 ERROR: process "/bin/sh -c cargo install --path attestation-service --bin grpc-as --features grpc-bin --locked" did not complete successfully: exit code: 101

Seems like it may have started on #565 but not sure if it's related yet

@Xynnn007
Copy link
Member

Xynnn007 commented Nov 11, 2024

Well I test locally and think they are related.

The default feature will enable all-verifiers by default even if looks like being disabled

BbolroC added a commit to BbolroC/trustee that referenced this issue Nov 15, 2024
Issue confidential-containers#568 highlights the need for an image build check for s390x,
similar to what we have for x86_64. This commit addresses the need by:
- Extracting the image build steps from the push-{kbs,as}-image-to-ghcr
  workflow into separate workflows
- Configuring these workflows to run on PR events or after merging a PR

Notable change:
- On merge, the workflow now pushes `ghcr.io/confidential-containers/staged-images/rhel-ubi`

Signed-off-by: Hyounggyu Choi <[email protected]>
BbolroC added a commit to BbolroC/trustee that referenced this issue Nov 15, 2024
Issue confidential-containers#568 highlights the need for an image build check for s390x,
similar to what we have for x86_64. This commit addresses the need by:
- Extracting the image build steps from the push-{kbs,as}-image-to-ghcr
  workflow into separate workflows
- Configuring these workflows to run on PR events or after merging a PR

Notable change:
- On merge, the workflow now pushes `ghcr.io/confidential-containers/staged-images/rhel-ubi`

Signed-off-by: Hyounggyu Choi <[email protected]>
BbolroC added a commit to BbolroC/trustee that referenced this issue Nov 15, 2024
Issue confidential-containers#568 highlights the need for an image build check for s390x,
similar to what we have for x86_64. This commit addresses the need by:
- Extracting the image build steps from the push-{kbs,as}-image-to-ghcr
  workflow into separate workflows
- Configuring these workflows to run on PR events or after merging a PR

Notable change:
- On merge, the workflow now pushes `ghcr.io/confidential-containers/staged-images/rhel-ubi`

Signed-off-by: Hyounggyu Choi <[email protected]>
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 a pull request may close this issue.

2 participants