aqa-tests: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found
/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34’ not found on https://ci.adoptium.net/computer/test-docker-ubuntu2004-x64-4/
https://ci.adoptium.net/view/Test_grinder/job/Grinder_Simple/391/ Same job no issues on https://ci.adoptium.net/computer/test-docker-ubuntu2204-x64-6/ https://ci.adoptium.net/view/Test_grinder/job/Grinder_Simple/392/
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 16 (16 by maintainers)
OK so I’ll look at implementing
sw.tool.glibc.2_12for us initially as a direct replacement for the current rhel6 and centos6 labels 😃Yep -
ADDITIONAL_TEST_LABELis the equivalent parameter in the json of the platform-specific pipelines which should get passed down toLABEL_ADDITIONin the test jobs. e.g. at https://github.com/adoptium/ci-jenkins-pipelines/blob/782ebb0ffc5fbf9947dfb6c9065648e47bab2c7f/pipelines/jobs/configurations/jdk21u_pipeline_config.groovy#L30Pretty much, as per the original discussion and per how some of the real-world labels look like, dotted version numbers look like:
&&its value to the LABEL parameter, so our approach has been to use !someValue when it makes more sense to, as in this case)Yeah absolutely - I have no issues with that, but I think we need to carefully thinkg about how many different ones we want to have for this particular use case. Maybe a topic for Tuesday’s call 😃