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

TAP plugin fails with parse error when tests fail #36

Closed
sophia-guo opened this issue May 19, 2017 · 3 comments
Closed

TAP plugin fails with parse error when tests fail #36

sophia-guo opened this issue May 19, 2017 · 3 comments
Assignees

Comments

@sophia-guo
Copy link
Contributor

some tests fail will cause TAP plugin fails with parse error
https://ci.adoptopenjdk.net/view/OpenJDK%20tests/job/openjdk_test_x86-64_linux/13/
01:24:31 Error: Some tests failed or other problems occurred.
01:24:31 ]: special characters are not allowed
01:24:31 at org.tap4j.parser.Tap13Parser.parseDiagnostics(Tap13Parser.java:435)
01:24:31 at org.tap4j.parser.Tap13Parser.parseLine(Tap13Parser.java:262)
01:24:31 at org.tap4j.parser.Tap13Parser.parseTapStream(Tap13Parser.java:224)
01:24:31 ... 15 more
01:24:31 Caused by: unacceptable character '�' (0x7) special characters are not allowed
01:24:31 in "'string'", position 447721
01:24:31 at org.yaml.snakeyaml.reader.StreamReader.checkPrintable(StreamReader.java:67)
01:24:31 at org.yaml.snakeyaml.reader.StreamReader.(StreamReader.java:47)
01:24:31 at org.yaml.snakeyaml.Yaml.load(Yaml.java:369)
01:24:31 at org.tap4j.parser.Tap13Parser.parseDiagnostics(Tap13Parser.java:430)
01:24:31 ... 17 more
01:24:31 TAP parse errors found in the build. Marking build as UNSTABLE
01:24:31 TAP Reports Processing: FINISH

@smlambert
Copy link
Contributor

You may want to temporarily comment out that part of the deploy stage until this can be fixed (I suspect some jtreg output is not to tap4j's liking).

sophia-guo added a commit to sophia-guo/openjdk-tests that referenced this issue May 19, 2017
… to avoid

tap parse error.


Signed-off-by: Sophia Guo <sophiag@ca.ibm.com>
@sophia-guo
Copy link
Contributor Author

sophia-guo commented May 19, 2017

Right, it only works for testng, junit output. As we create the tap result by perl I can first try to avoid this parse error first. If not works will comment out the deploy stage, however, that means no taps tests result :_(. Or we could temporarily comment out the failure output( still have the tap results, change back to no failure output details )?

@karianna karianna added the bug label May 22, 2017
sophia-guo added a commit to sophia-guo/openjdk-tests that referenced this issue May 23, 2017
Jtreg output will be archived to txtfile TestTargetResult

Signed-off-by: Sophia Guo <sophiag@ca.ibm.com>
@smlambert
Copy link
Contributor

As we have moved towards using other plugins to represent the test output, I think we can close this issue altogether.

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

No branches or pull requests

3 participants