Build: Fix ability to ignore when no tests are run #28930
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit fixes the test progress logging to not produce an NPE when there are no tests run. The onQuit method is always called, but onStart would not be called if no tests match the test patterns.
Running any randomized testing task within Elasticsearch currently fails if a project has zero tests. This was supposed to be overrideable, but it was always set to 'fail', and the system property to override was passed down to the test runner, but never read there. This commit changes the value of the ifNoTests setting to randomized runner to be read from system properties and continue to default to 'fail'.
rjernst
added
>test
|
Note this PR is based off #28929 and awaits that to be merged. |
|
/cc @elastic/es-core-infra |
rjernst
added a commit
that referenced
this pull request
Mar 8, 2018
Running any randomized testing task within Elasticsearch currently fails if a project has zero tests. This was supposed to be overrideable, but it was always set to 'fail', and the system property to override was passed down to the test runner, but never read there. This commit changes the value of the ifNoTests setting to randomized runner to be read from system properties and continue to default to 'fail'.
sebasjm
pushed a commit
to sebasjm/elasticsearch
that referenced
this pull request
Mar 10, 2018
Running any randomized testing task within Elasticsearch currently fails if a project has zero tests. This was supposed to be overrideable, but it was always set to 'fail', and the system property to override was passed down to the test runner, but never read there. This commit changes the value of the ifNoTests setting to randomized runner to be read from system properties and continue to default to 'fail'.
jasontedor
added a commit
to jasontedor/elasticsearch
that referenced
this pull request
Mar 12, 2018
* master: (28 commits) Maybe die before failing engine (elastic#28973) Remove special handling for _all in nodes info Remove Booleans use from XContent and ToXContent (elastic#28768) Update Gradle Testing Docs (elastic#28970) Make primary-replica resync failures less lenient (elastic#28534) Remove temporary file 10_basic.yml~ Use different pipeline id in test. (pipelines do not get removed between tests extending from ESIntegTestCase) Use fixture to test the repository-gcs plugin (elastic#28788) Use String.join() to describe a list of tasks (elastic#28941) Fixed incorrect test try-catch statement Plugins: Consolidate plugin and module loading code (elastic#28815) percolator: Take `matchAllDocs` and `verified` of the sub result into account when analyzing a function_score query. Build: Remove rest tests on archive distribution projects (elastic#28952) Remove FastStringReader in favor of vanilla StringReader (elastic#28944) Remove FastCharArrayReader and FastCharArrayWriter (elastic#28951) Continue registering pipelines after one pipeline parse failure. (elastic#28752) Build: Fix ability to ignore when no tests are run (elastic#28930) [rest-api-spec] update doc link for /_rank_eval Switch XContentBuilder from BytesStreamOutput to ByteArrayOutputStream (elastic#28945) Factor UnknownNamedObjectException into its own class (elastic#28931) ...
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Running any randomized testing task within Elasticsearch currently fails
if a project has zero tests. This was supposed to be overrideable, but
it was always set to 'fail', and the system property to override was
passed down to the test runner, but never read there. This commit
changes the value of the ifNoTests setting to randomized runner to be
read from system properties and continue to default to 'fail'.