Skip to content

[CI] JdbcSqlSpecIT and JdbcCsvSpecIT initializationError #45866

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.

Sign up for GitHub

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

Jump to bottom
Closed
henningandersen opened this issue Aug 22, 2019 · 1 comment · Fixed by #45884
Closed

[CI] JdbcSqlSpecIT and JdbcCsvSpecIT initializationError #45866

henningandersen opened this issue Aug 22, 2019 · 1 comment · Fixed by #45884
Assignees
@rjernst
Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI

Comments

@henningandersen
Copy link
Contributor

My PR build failed with initializationError in above tests due to a missing directory. This seems to have happened once before on August 14th. I can reproduce this locally too.

The error is:

org.elasticsearch.xpack.sql.qa.security.JdbcCsvSpecIT > initializationError FAILED
--
java.nio.file.NoSuchFileException: /var/lib/jenkins/workspace/elastic+elasticsearch+pull-request-2/x-pack/plugin/sql/qa/security/without-ssl/build/classes/java/test

I can reproduct this locally by doing:

./gradlew :x-pack:plugin:sql:qa:security:without-ssl:clean

and then

./gradlew :x-pack:plugin:sql:qa:security:without-ssl:integTestRunner

fails. The test directory referenced above does not exist.

If I instead invoke the check task, it works OK and the directory is created.
@henningandersen henningandersen added :Delivery/Build Build or test infrastructure >test-failure Triaged test failures from CI labels Aug 22, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@henningandersen henningandersen mentioned this issue Aug 22, 2019
Merged
rjernst added a commit to rjernst/elasticsearch that referenced this issue Aug 22, 2019
@rjernst
Make reuse of sql test code explicit
3ecf401 
The sql project uses a common set of security tests, which are run in
subprojects. Currently these are shared through a shared directory, but
this is not setup correctly to ensure it is built before tests run. This
commit changes the test classes to be an artifact of the sql/qa/security
project and makes the test runner use the built artifact (a directory of
classes) for tests.

closes elastic#45866
@rjernst rjernst mentioned this issue Aug 22, 2019
Merged
rjernst added a commit that referenced this issue Sep 11, 2019
@rjernst
Make reuse of sql test code explicit (#45884)
e2977dc 
The sql project uses a common set of security tests, which are run in
subprojects. Currently these are shared through a shared directory, but
this is not setup correctly to ensure it is built before tests run. This
commit changes the test classes to be an artifact of the sql/qa/security
project and makes the test runner use the built artifact (a directory of
classes) for tests.

closes #45866
rjernst added a commit that referenced this issue Sep 11, 2019
@rjernst
Make reuse of sql test code explicit (#45884)
86290cb 
The sql project uses a common set of security tests, which are run in
subprojects. Currently these are shared through a shared directory, but
this is not setup correctly to ensure it is built before tests run. This
commit changes the test classes to be an artifact of the sql/qa/security
project and makes the test runner use the built artifact (a directory of
classes) for tests.

closes #45866
rjernst added a commit that referenced this issue Sep 30, 2019
@rjernst
Make reuse of sql test code explicit (#45884)
9b1ae8b 
The sql project uses a common set of security tests, which are run in
subprojects. Currently these are shared through a shared directory, but
this is not setup correctly to ensure it is built before tests run. This
commit changes the test classes to be an artifact of the sql/qa/security
project and makes the test runner use the built artifact (a directory of
classes) for tests.

closes #45866
@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
Assignees

@rjernst rjernst

Labels
:Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team >test-failure Triaged test failures from CI
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Make reuse of sql test code explicit rjernst/elasticsearch
4 participants
@rjernst @mark-vieira @elasticmachine @henningandersen