OpenSSL error while attempting to trigger an integration test
In a MRB development environment with:
v08_14_00-87-g9163b82, updated to use LArSoft
set up with
mrbsetenv (and compiled), running from
trigger --build-delay 0 --revisions 'larsim@feature/gp_PhotonVisTransformations'
I get a "Triggering CI build" message and no integration test starts (I don't get any e-mail).
A modified, more verbose
curl: (58) could not load PEM client certificate, OpenSSL error error:02001002:system library:fopen:No such file or directory, (no key found, wrong pass phrase, or wrong file format?)
10 times before giving up announcing "trigger of CI build failed".
lar_ci version is the current one (
#1 Updated by Vito Di Benedetto 2 months ago
- Target version set to v1_9_0_RC
- Assignee set to Vito Di Benedetto
- Status changed from New to Assigned
Since couple of mounts ago jobsub_client included a curl as dependency:
$ ups depend jobsub_client jobsub_client v1_2_10 -f NULL -z /cvmfs/fermilab.opensciencegrid.org/products/common/db -g current |__cigetcert v1_18_1 -f Linux64bit+2.6-2.12 -z /cvmfs/fermilab.opensciencegrid.org/products/common/db -g current | |__cigetcertlibs v1_1 -f Linux64bit+2.6-2.12 -z /cvmfs/fermilab.opensciencegrid.org/products/common/db |__curl v7_64_1 -f Linux64bit+2.6 -z /cvmfs/fermilab.opensciencegrid.org/products/common/db -g current
it looks like this curl version is not compatible with the CI.
I'll work on this to ensure the CI can use this curl version.
#3 Updated by Vito Di Benedetto 2 months ago
- % Done changed from 0 to 100
- Status changed from Work in progress to Resolved
This issue has been fixed.
trigger command now should be able to use
curl from the system and from CVMFS as well.
The fix is available in the develop branch on
generic_ci product and it will be available in the new CI release that will be deployed on early July.