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

Jenkins TEST TARGETS SUMMARY parser got wrong result #4460

Closed
renfeiw opened this issue Mar 21, 2023 · 2 comments
Closed

Jenkins TEST TARGETS SUMMARY parser got wrong result #4460

renfeiw opened this issue Mar 21, 2023 · 2 comments

Comments

@renfeiw
Copy link
Contributor

renfeiw commented Mar 21, 2023

When there are multiple test targets summary (currently in CRIU testing), the current Jenkins summary parser only parses the first occurrence (due to the Jenkins manager.getLogMatcher behaviour). We need a solution to parse the only one summary output that user wants.

@renfeiw
Copy link
Contributor Author

renfeiw commented Apr 18, 2023

PR: #4511, adoptium/TKG#435

@renfeiw renfeiw closed this as completed Apr 18, 2023
@renfeiw
Copy link
Contributor Author

renfeiw commented Apr 18, 2023

To prevent summary from docker tests get parsed, we can export an env var to avoid parsing the unwanted summary.
For example, do the following in the docker test command:

export RESULT_COMMENT="IN DOCKER"

in playlist.xml test command. The result summary will look like:

22:50:09  (IN DOCKER) TEST TARGETS SUMMARY
22:50:09  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
22:50:09  PASSED test targets:
22:50:09  	cmdLineTester_criu_keepCheckpoint_0 
22:50:09  	cmdLineTester_criu_keepCheckpoint_1 
22:50:09  	cmdLineTester_criu_keepCheckpoint_2 
22:50:09  	cmdLineTester_criu_keepCheckpoint_3 
22:50:09  	cmdLineTester_criu_keepCheckpoint_4 
22:50:09  	cmdLineTester_criu_keepCheckpoint_5 
22:50:09  
22:50:09  (TOTAL: 6   EXECUTED: 6   PASSED: 6   FAILED: 0   DISABLED: 0   SKIPPED: 0)
22:50:09  ALL TESTS PASSED
22:50:09  ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

It then will not be picked up by the Jenkins parser.

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

No branches or pull requests

1 participant