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

CI: test-ISLET-SDK-shim_test fails with error: package zeroize v1.8.0 cannot be built because it requires rustc 1.72 or newer #244

Closed
gapisback opened this issue Apr 25, 2024 · 2 comments · Fixed by #245
Assignees

Comments

@gapisback
Copy link
Collaborator

This issue was encoutered while stabilizing CI build-jobs on the ubuntu-latest version of Linux specified in build.yml.

Seems like on the newer CCC-enabled CI machines, we are running on : Ubuntu 22.04.4 LTS.

The failure can be seen in the CI-jobs for PR #243 , where this stabilization effort is being done.

  Downloaded linux-raw-sys v0.4.13
  Downloaded libc v0.2.153
error: package `zeroize v1.8.0` cannot be built because it requires rustc 1.72 or newer, while the currently active rustc version is 1.68.0-nightly
Either upgrade to rustc 1.72 or newer, or use
cargo update -p zeroize@1.8.0 --precise ver
where `ver` is the latest version of `zeroize` supporting rustc 1.68.0-nightly
 
test.sh: **** Error **** Failed command, ../../third_party/islet/setup.sh, at line 796 ./CI/scripts/test.sh while executing function test-ISLET-SDK-shim_test
Error: Process completed with exit code 101.

Stabilization in dev-branch: gapisback/Fix-make-test-build-and-install-sev-snp-simulator

As part of this stabilization, I added a new shell script, ./CI/scripts/osinfo.sh which is run at the beginning of CI.

You can see the output shows that we are running on these Linux VMs:

Run ./CI/scripts/osinfo.sh
Linux fv-az1242-222 6.5.0-1018-azure #19~22.04.2-Ubuntu SMP Thu Mar 21 16:45:46 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
 AuthenticAMD, 4 CPUs, 15 GB,  AMD EPYC 7763 64-Core Processor
PING fv-az1242-222.5v455grvumqehdtexsenyv1bfb.ex.internal.cloudapp.net (10.1.1.172) 56(84) bytes of data.
64 bytes from fv-az1242-222.5v455grvumqehdtexsenyv1bfb.ex.internal.cloudapp.net (10.1.1.172): icmp_seq=1 ttl=64 time=0.034 ms

No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.4 LTS
Release:	22.04
Codename:	jammy

I have been able to repro this on my Linux-VM also running on Ubuntu 22.04.4 LTS Linux.:

$ agurajada-Linux-Vm:[44] $ ./CI/scripts/test.sh test-ISLET-SDK-shim_test
[...]

  Downloaded num-bigint-dig v0.8.4
  Downloaded cbindgen v0.24.5
  Downloaded libm v0.2.8
  Downloaded 33 crates (1.3 MB) in 0.40s
error: package `zeroize v1.8.0` cannot be built because it requires rustc 1.72 or newer, while the currently active rustc version is 1.68.0-nightly
Either upgrade to rustc 1.72 or newer, or use
cargo update -p zeroize@1.8.0 --precise ver
where `ver` is the latest version of `zeroize` supporting rustc 1.68.0-nightly

test.sh: **** Error **** Failed command, ../../third_party/islet/setup.sh, at line 796 ./CI/scripts/test.sh while executing function test-ISLET-SDK-shim_test

The error is coming from this step in this script: third_party/islet/setup.sh:

 44 . "$HOME/.cargo/env"
 45 # Build ISLET SDK (simulated version for x86_64)
 46 cd "$ISLET_SDK" && cargo build                                <<<<<<<
@gapisback
Copy link
Collaborator Author

Hi, @bitboom [ cc: Jinbum, ] can you please look at this ISLET build stability we are seeing on these new CI build-jobs?

For now, I will comment out this test run from test.sh, so it won't fail. I need to get the other jobs running cleanly as I am doing some re-stabilization and clean-up of other pending items.

When you fix this issue, you can re-activate this part of the test.sh:

789 function test-ISLET-SDK-shim_test() {
790     echo "**********************************************************"
791     echo "* Download ISLET SDK, build the library and run shim_test"
792     echo "**********************************************************"
793     echo " "
794     echo "****** WARNING! Skipped due to open issue #242, Fails on Ubuntu 22.04.4"
795     echo " "
796     return
[...]

817 function test-run_example-simple_app_under_islet-using-shim() {
818     echo "***********************************************************************************"
819     echo "* Test: Execute script to compile, build and run simple_app_under_islet using shim"
820     echo "***********************************************************************************"
821     echo " "
822     echo "****** WARNING! Skipped due to open issue #242, Fails on Ubuntu 22.04.4"
823     echo " "
824     return

I am adding those warning messages and return in a commit which I will push thru CI, to see if the rest of the tests run cleanly.

gapisback added a commit that referenced this issue Apr 25, 2024
This commit attempts to keep the CI tests runing cleanly. Some tests
are failing due to different issues reported under issue #242
and #244. Those will need some minor corrections in build-steps.
For now, 5 test-cases from test.sh are commented out with a
Warning message.

- Skip few simulated-SEV related build-and-test cases.
- Skip ISLET-related build-and-test tests due to rustc version
  incompatibility.

Those will need to be re-enabled when above two issues are resolved,
if possible.

(If further investigation shows that we cannot support Ubunutu 22.04,
then some changes will need to be made in CI's build.yml to drop-down
to an older Ubuntu rev-level.)
@bitboom
Copy link
Collaborator

bitboom commented Apr 26, 2024

Thanks for reporting this issue :) I will check this next week.

gapisback added a commit that referenced this issue May 3, 2024
This commit attempts to keep the CI tests runing cleanly. Some tests
are failing due to different issues reported under issue #242
and #244. Those will need some minor corrections in build-steps.
For now, 5 test-cases from test.sh are commented out with a
Warning message.

- Skip few simulated-SEV related build-and-test cases.
- Skip ISLET-related build-and-test tests due to rustc version
  incompatibility.

Those will need to be re-enabled when above two issues are resolved,
if possible.

(If further investigation shows that we cannot support Ubunutu 22.04,
then some changes will need to be made in CI's build.yml to drop-down
to an older Ubuntu rev-level.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants