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 a script to shrink test-wpt output to only unexpected results #10129

Closed
nox opened this issue Mar 22, 2016 · 12 comments
Closed

Add a script to shrink test-wpt output to only unexpected results #10129

nox opened this issue Mar 22, 2016 · 12 comments

Comments

@nox
Copy link
Member

@nox nox commented Mar 22, 2016

No idea if this issue should live in saltfs, wpt itself or here.

Cc @metajack.

@nox nox changed the title Add a script to shrink test-wpt output to only failures Add a script to shrink test-wpt output to only unexpected results Mar 22, 2016
@Ms2ger
Copy link
Contributor

@Ms2ger Ms2ger commented Mar 23, 2016

I imagine we'd want a separate kind of logger; cc @jgraham

@jgraham
Copy link
Contributor

@jgraham jgraham commented Mar 23, 2016

Yeah, you would want to implement a mozlog formatter.

Not having an easy way to tell if a test ran at all, or see log output, seems rather problematic though. My suspicion is that whatever the use case here is, you're trying to solve the wrong problem.

@jgraham
Copy link
Contributor

@jgraham jgraham commented Mar 23, 2016

So it seems like you might just want --log-errorsummary=<file>. That produces a line-by-line json view of only the test failures and critical/error level log messages. It's not ideal for humans but is the right thing to use if you're implementing a bot (it's what treeherder uses for autoclassification, for example)

@nox
Copy link
Member Author

@nox nox commented Mar 23, 2016

Is that usable to update expectations too?

@jgraham
Copy link
Contributor

@jgraham jgraham commented Mar 23, 2016

No, you still need the raw log for that. Although conceivably someone could perhaps implement log updating based on the error summary in the future.

@nox
Copy link
Member Author

@nox nox commented Mar 23, 2016

And does it include unexpected PASS?

@jgraham
Copy link
Contributor

@jgraham jgraham commented Mar 23, 2016

Yes (this conversation would maybe be shorter on irc, or by pointing you at https://dxr.mozilla.org/mozilla-central/source/testing/mozbase/mozlog/mozlog/formatters/errorsummary.py )

@jgraham
Copy link
Contributor

@jgraham jgraham commented Mar 23, 2016

(sorry "test failures" was very lax language. I meant "unexpected test results")

@nox
Copy link
Member Author

@nox nox commented Oct 1, 2017

Cc @mateon1 who is doing a lot of fuzzing and shrinking.

@nox
Copy link
Member Author

@nox nox commented Oct 1, 2017

Never mind, I can't read.

@nox
Copy link
Member Author

@nox nox commented Oct 1, 2017

This was more or less done, with @jdm's intermittent stuff. Closing.

@nox nox closed this Oct 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.