Report could not find hits as test case error #1650
Merged
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.
Currently,
"could not find hits in <data_stream> data stream"error is not reported as part of the xUnit report.For instance, in this build https://buildkite.com/elastic/integrations/builds/8409#018d4368-0d0c-4ddd-a1b9-1f6c3d4b6753 , no hits were found and
elastic-packagereturned an error without completing the test run. Moreover, there is no jUnit report (XML file)because of that failure:
https://buildkite.com/elastic/integrations/builds/8409#018d4368-0d0c-4ddd-a1b9-1f6c3d4b6753/6-10235
This PR adds this specific error as a
ErrTestCaseFailedso it gets added into the system xUnit report. As a side-effect,elastic-packagenow allows to run the other tests even if for one data stream there are no hits found.Report example for
mysqlpackage:How to test locally