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

Rethink “navigation-timing-2” test to avoid recurrent “latest-is-not-previous” errors #205

Open
tripu opened this issue Jul 9, 2015 · 0 comments
Assignees

Comments

@tripu
Copy link
Member

tripu commented Jul 9, 2015

Every time there's a new version of the navigation timing 2 spec we have to manually update the metadata for the navigation-timing-2 test to avoid an error in the test suite (headers.dl.latest-is-not-previous) that breaks the builds — sometimes for days.

See #206, where I'm suggesting we disable that test until it's fixed.

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

2 participants