#207 - Adding log-junuit example for v1 #208
Draft
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
|
Note: Will need to update the tests as well. |
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.
Hi @Jean85 , I am adding this MR to provide some idea how I have solved the log-junit in paraunit.
This was one of the main features that i needed in the rewrite i mentioned to you via email.
I did not had a chance to go over the 2.x version knowing you made a huge refactor but I will get to it in my free time.
The basic idea is to send the log-junit command to each of the processes i.e either chunks or tests and generate files based on the filename provided -> --log-unit=test.xml and the output will be stored in the junit dir then merged into one file and the directory will be deleted something similar to what you are doing with the chunks currently.