-
Notifications
You must be signed in to change notification settings - Fork 15
Testsuite fails on in a chroot on qemu/kvm VM #43
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
Comments
The test cases a simple script (test.pm) that use the openssl command line utility to perform pairwise-consistency tests: 1. Enc/Dec a tmp file configured to use the ibmca openssl-engine (which in turn uses s390x crypto hw via libica). 2. Dec/Enc the result using openssl (w/o engine configuration), 3. compare results. At the moment, the testcases operate on the same temporary input/output files, so they cant be run concurrently. Regrading the test case failures:
is an openssl error ( https://www.openssl.org/docs/faq.html#USER2 ). Regarding the skipped test cases: A test is only skipped, if the engine could not be configured. This is checked by parsing the output of
output must contain "ibmca", srcdir is from the autotools test framwork |
thank you for details. I shall check what exactly why those things are failing here. |
Is this one still relevant? |
I think this was resolved some time ago:
As seen in build log of https://launchpad.net/ubuntu/+source/openssl-ibmca/2.4.1-0ubuntu1/+build/27674210 at https://launchpadlibrarian.net/710728827/buildlog_ubuntu-noble-s390x.openssl-ibmca_2.4.1-0ubuntu1_BUILDING.txt.gz which is the current build of openssl-ibmca since Noble onwards. |
This is on Ubuntu Cosmic (to become 18.10) as built in launchpad PPA. Note anybody can use PPAs on launchpad and activate builds for s390x.
When doing a similar build, but in chroot on a z/VM, things are slightly better:
So no tests are actually run, and everything is skipped.
Regular user build (non-chrooted) on z/VM goes fine and results in full test suite pass:
The text was updated successfully, but these errors were encountered: