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

somehow indicate which JUnit file a test failure came from #210

Closed
ixdy opened this issue Jun 23, 2016 · 2 comments
Closed

somehow indicate which JUnit file a test failure came from #210

ixdy opened this issue Jun 23, 2016 · 2 comments
Assignees
Labels
area/gubernator Issues or PRs related to code in /gubernator

Comments

@ixdy
Copy link
Member

ixdy commented Jun 23, 2016

Motivating example: unit/integration test runs like https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/pr-logs/pull/27600/kubernetes-pull-test-unit-integration/32233 have multiple JUnit files, with associated "verbose output" text files that can help debug test failures.

Rather than searching through each file, it'd be nice to know which one to go to for the verbose output. (Maybe even link directly to that file if it exists? May be getting too specific though.)

@ixdy ixdy added the area/gubernator Issues or PRs related to code in /gubernator label Jun 23, 2016
@fejta
Copy link
Contributor

fejta commented Sep 20, 2016

Thoughts on this?

@rmmh
Copy link
Contributor

rmmh commented Sep 20, 2016

This is done, Gubernator now links to the XML file for each failure

@rmmh rmmh closed this as completed Sep 20, 2016
simonswine pushed a commit to simonswine/test-infra that referenced this issue Jul 17, 2018
mborsz pushed a commit to mborsz/test-infra that referenced this issue Dec 14, 2018
…le_tests

ClusterLoader - Allowing multiple tests
grantr pushed a commit to grantr/test-infra that referenced this issue Feb 21, 2020
MushuEE pushed a commit to MushuEE/test-infra that referenced this issue Mar 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/gubernator Issues or PRs related to code in /gubernator
Projects
None yet
Development

No branches or pull requests

3 participants