Skip to content
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

Running a single test got harder #31964

Closed
DaveCTurner opened this issue Jul 11, 2018 · 2 comments · Fixed by #32015
Closed

Running a single test got harder #31964

DaveCTurner opened this issue Jul 11, 2018 · 2 comments · Fixed by #32015
Assignees
@rjernst
Labels
>bug :Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team

Comments

@DaveCTurner
Copy link
Contributor

The changes introduced in #30975 unfortunately mean that it's harder to run a single test from the command line, and in particular the command that REPRODUCE WITH says will reproduce a failure will not work if the failing test was from the :server:test task. For instance:

$ ./gradlew :server:test -Dtests.class=org.elasticsearch.common.rounding.TimeZoneRoundingTests -Dtests.method="testUTCTimeUnitRounding"
...
> Task :server:testScriptDocValuesMissingV6Behaviour FAILED
   [junit4] <JUnit4> says jolly good day! Master seed: AA38CDFBB89D3357
==> Test Summary: 0 suites, 0 tests
   [junit4] Tests summary: 0 suites, 0 tests

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':server:testScriptDocValuesMissingV6Behaviour'.
> There were no executed tests: 0 suites, 0 tests
...

As a workaround, one can add -x :server:testScriptDocValuesMissingV6Behaviour to the command line.
@DaveCTurner DaveCTurner added the :Delivery/Build Build or test infrastructure label Jul 11, 2018
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@rjernst
Copy link
Member

rjernst commented Jul 11, 2018

This has not worked out like I had hoped. I will create a PR to make check depend on this test task instead of test.

@rjernst rjernst added the >bug label Jul 11, 2018
@rjernst rjernst self-assigned this Jul 11, 2018
rjernst added a commit to rjernst/elasticsearch that referenced this issue Jul 12, 2018
@rjernst
Build: Make additional test deps of check
521f89e 
This commit moves additional unit test runners from being dependencies
of the test task to dependencies of check. Without this change,
reproduce lines are incorrect due to the additional test runner not
matching any of the reproduce class/method info.

closes elastic#31964
@rjernst rjernst mentioned this issue Jul 12, 2018
Merged
@cbuescher cbuescher mentioned this issue Jul 13, 2018
Closed
rjernst added a commit that referenced this issue Jul 17, 2018
@rjernst
Build: Make additional test deps of check (#32015)
6371d51 
This commit moves additional unit test runners from being dependencies
of the test task to dependencies of check. Without this change,
reproduce lines are incorrect due to the additional test runner not
matching any of the reproduce class/method info.

closes #31964
rjernst added a commit that referenced this issue Jul 17, 2018
@rjernst
Build: Make additional test deps of check (#32015)
34e7858 
This commit moves additional unit test runners from being dependencies
of the test task to dependencies of check. Without this change,
reproduce lines are incorrect due to the additional test runner not
matching any of the reproduce class/method info.

closes #31964
@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
>bug :Delivery/Build Build or test infrastructure Team:Delivery Meta label for Delivery team
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Build: Make additional test deps of check rjernst/elasticsearch
4 participants
@rjernst @mark-vieira @DaveCTurner @elasticmachine