aqa-tests: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 16 (16 by maintainers)

Most upvoted comments

sw.os.zos.1_13 (where dotted version numbers represented by _ )

OK so I’ll look at implementing sw.tool.glibc.2_12 for us initially as a direct replacement for the current rhel6 and centos6 labels 😃

the name of the parameter is LABEL_ADDITION (which behaves to append && its value to the LABEL parameter, so our approach has been to use !someValue when it makes more sense to, as in this case)

Yep - ADDITIONAL_TEST_LABEL is the equivalent parameter in the json of the platform-specific pipelines which should get passed down to LABEL_ADDITION in the test jobs. e.g. at https://github.com/adoptium/ci-jenkins-pipelines/blob/782ebb0ffc5fbf9947dfb6c9065648e47bab2c7f/pipelines/jobs/configurations/jdk21u_pipeline_config.groovy#L30

Have I captured this correctly as per your understanding?

Pretty much, as per the original discussion and per how some of the real-world labels look like, dotted version numbers look like:

  • sw.os.zos.1_13 (where dotted version numbers represented by _ )
  • the name of the parameter is LABEL_ADDITION (which behaves to append && its value to the LABEL parameter, so our approach has been to use !someValue when it makes more sense to, as in this case)

One of the reasons we chose to use ‘long name labels’ is to help categorize the types of labels and give guidance to anyone who wanted to extend the schema.

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 😃