Skip to content

Linux OS id [arch-null] is not present in the Docker exclude list? #50393

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

Closed
nik9000 opened this issue Dec 19, 2019 · 4 comments · Fixed by #50664
Closed

Linux OS id [arch-null] is not present in the Docker exclude list? #50393

nik9000 opened this issue Dec 19, 2019 · 4 comments · Fixed by #50664
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team

Comments

@nik9000
Copy link
Member

nik9000 commented Dec 19, 2019

Elasticsearch version (bin/elasticsearch --version): master

Plugins installed: none

JVM version (java -version): jdk-13

OS version (uname -a if on a Unix-like system): Linux/arch

Description of the problem including expected versus actual behavior:

./gradlew :run logs

Linux OS id [arch-null] is not present in the Docker exclude list

This seems like a message that we log for CI, but it was an odd greeting while compiling the project for the first time in a year.

@nik9000 nik9000 added the :Delivery/Build Build or test infrastructure label Dec 19, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (:Core/Infra/Build)

@mark-vieira
Copy link
Contributor

@pugnascotia I'm inclined to short-circuit this stuff when not in a CI environment. Our exclusion list is based on our own custom images. There's nothing to say that a developer using Debian 8 can't run Docker-based tests. Thoughts?

@pugnascotia
Copy link
Contributor

@mark-vieira Yeah, I think that's fair. Do you happen to know what is the best way of detecting CI for us?

@mark-vieira
Copy link
Contributor

You can use BuildParams.isCi().

pugnascotia added a commit that referenced this issue Jan 7, 2020
Closes #50393. When generating the packaging test tasks, skip the Linux OS
checks unless we're running in CI.
SivagurunathanV pushed a commit to SivagurunathanV/elasticsearch that referenced this issue Jan 23, 2020
Closes elastic#50393. When generating the packaging test tasks, skip the Linux OS
checks unless we're running in CI.
@mark-vieira mark-vieira added the Team:Delivery Meta label for Delivery team label Nov 11, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants