-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
Verify the set of machines that have docker installed and update labels #1044
Comments
Bear in mind several godaddy ones currently have it installed but it doesn't quite work as per #721 |
Yes, still have the error with godaddy ones 'The command '/bin/sh -c apt-get update && apt-get -y install ant apt-transport-https ca-certificates curl git make unzip vim' returned a non-zero code: 100' https://ci.adoptopenjdk.net/view/work%20in%20progress/job/Grinder_Sandbox/1047/console |
Been through the set of https://ci.adoptopenjdk.net/label/hw.arch.ppc64le/ test machines, 5/11 have docker installed (ubuntu based ones), label is present. Going through s390x now, looks like docker present on test-marist-ubuntu1604-s390x-4 so label added, will confirm others and add labels to remaining machines shortly. |
I thought I'd help the effort. I used Ansible to just query all non-windows test machines with
|
Bumping this for two reasons:
|
The current list of linux/x64 test machines which do not have the ability to run docker containers are the ten machines at https://ci.adoptopenjdk.net/label/ci.role.test&&hw.arch.x86&&sw.os.linux&&!sw.tool.docker/ Of these, eight are "static docker" containers already so not suitable for running containers and must therefore not be tagged. I've added the tag to the ibmcloud-rhel7 one, but realistically it is preferable to run the docker jobs on the larger equinix machines that we have, which also have multiple executors which could be used. Those systems do not currently have the test tags, but (as I think we discussed elsewhere) I'd be keen to add the support for running containerised testing on them if we can define a suitable set of tags that only allows the dockerised tests to run on them. On that basis, I'll leave this open for a bit longer :-) |
We currently have 5 machines labelled with docker for use by test: https://ci.adoptopenjdk.net/label/ci.role.test&&hw.arch.x86&&sw.os.linux&&sw.tool.docker/
Given that docker is in the ansible playbooks, I think there are actually more machines with docker installed than are labelled with sw.tool.docker. We should go through the set of machines and try to run the external (docker-based tests from the openjdk-tests repo) to verify which additional test machines can be used for external tests.
The text was updated successfully, but these errors were encountered: