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.

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

Add step in Wildfly tests to copy junit report xml to host machine for jenkins reporting #575

Closed
Mesbah-Alam opened this issue Sep 19, 2018 · 3 comments
Assignees
Labels

Comments

@Mesbah-Alam
Copy link
Contributor

Currently failures in Wildfly tests do not show up in the list of failures in the external test build https://ci.adoptopenjdk.net/view/Test_external/job/openjdk8_hs_externaltest_x86-64_linux/179/testReport/

We need to add a step in Wildfly tests to copy junit report xml to host machine for jenkins reporting.

Details:

We should make the same change for Wildfly tests as was made in the Jenkins test -- which is adding a docker cp step in the command line to copy the junit xml reports out of the docker container & into the host machine's workspace. This allows the Jenkins reporting plugin to generate test reports at the end of the test build.

Here's the PR for the Jenkins test change that can be taken as example: https://github.com/AdoptOpenJDK/openjdk-tests/pull/537/files.

So, we need to run Wildfly tests in a local machine, find out where it generates the xml junit reports and use that path in the docker cp command in playlist.xml.

@Mesbah-Alam
Copy link
Contributor Author

@suman-mitra - since you added the Kafka tests originally, I'm assigning this issue to you. Please let me know if you have any question.

@suman-mitra
Copy link
Contributor

The results seems to be available under the below directories. All the .xml files under the below dir's have the junit results

./kafka/clients/build/test-results/test/
./kafka/core/build/test-results/test/
./kafka/streams/streams-scala/build/test-results/test

We can also find them by using find *.xml

@smlambert
Copy link
Contributor

Closing this in favour of #976

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants