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

Flaky reftests in Taskcluster stability jobs are not possible to debug #14566

Open
foolip opened this issue Dec 17, 2018 · 6 comments
Open

Flaky reftests in Taskcluster stability jobs are not possible to debug #14566

foolip opened this issue Dec 17, 2018 · 6 comments

Comments

@foolip
Copy link
Member

foolip commented Dec 17, 2018

When reftests are found to be flaky in Taskcluster's stability jobs, the only information one can get from the logs is the number of passes and failures. If the problem doesn't reproduce locally there are no clues about how to proceed.

This affected #14469 and #14551 and. See also #14564.

@foolip
Copy link
Member Author

foolip commented Dec 17, 2018

@jgraham how do you think we should fix this? Even with TBPL logs, is reftest analyzer be able to extract multiple screenshots for the same test and show them?

@jgraham
Copy link
Contributor

jgraham commented Dec 17, 2018

The reftest analyzer is not very clever, so probably? If we can get the data into the logs and it doesn't work I can modify it so it does.

@foolip
Copy link
Member Author

foolip commented Dec 19, 2018

@jgraham, the command is already something like ./wpt run --channel=nightly --verify --affected HEAD^ --log-tbpl-level=info --log-tbpl=- -y --no-pause --no-restart-on-unexpected --install-fonts --no-headless --install-browser firefox, with --log-tbpl=- coming from taskcluster-run.py, but it doesn't seem to have any effect. I guess that --verify overrides the output format?

@foolip
Copy link
Member Author

foolip commented Dec 19, 2018

@Hexcles OK if I assign this to you for the proximity to getting screenshots out of regular runs?

@foolip
Copy link
Member Author

foolip commented Jan 23, 2019

For bookkeeping, #14469 was merged while possibly still having a flaky reftest in Firefox.

@foolip
Copy link
Member Author

foolip commented Jun 10, 2019

@Hexcles is it still appropriate that this is assigned to you? FWIW, I haven't seen it come up again since I filed this issue, so it's not on fire :)

@Hexcles Hexcles removed their assignment Dec 2, 2019
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

4 participants