question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Docs on Blink layout tests seems outdated

See original GitHub issue

https://v8.dev/docs/blink-layout-tests

I’m having troubles with the third point (rebaselining the tests in Chromium), if you try to commit [ NeedsRebaseline ] it will fail during presubmit checks (as you can see here).

Another document exists with a manual way to do it (which is known to work): https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_tests.md#Rebaselining-Web-Tests.

Status: I’m currently following it and I can report the result here.

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Comments:9 (9 by maintainers)

github_iconTop GitHub Comments

2reactions
MayaLekovacommented, Feb 6, 2019

@xtuc Please check whether my last commit reflects the experience that you had. Once your CL in Chromium lands, I’d be happy to also link it in the docs as an example, that’s a great idea!

Re:

  • I would expect the tools/run_web_tests.py --reset-results flag to update the TestExpectations file, however it doesn’t.

AFAIK, the automatic updating of the TestExpectations file will work only when you make changes in Chromium itself, not in V8, because we can’t synchronize rolling V8 into Chromium with this update. That’s why we fall back to the manual process and you need to do the whole skip-unskip dance with the TestExpectations file.

1reaction
mathiasbynenscommented, Feb 4, 2019

https://bugs.chromium.org/p/chromium/issues/detail?id=735176 seems relevant:

Pretty soon, NeedsRebaseline will be removed (bug 692811).

Now there’s NeedsManualRebaseline and Rebaseline. In practice, what these actually mean is:

  • NeedsManualRebaseline means “run the test but ignore the results”
  • Rebaseline means “select this test when webkit-patch rebaseline-expectations is run”
Read more comments on GitHub >

github_iconTop Results From Across the Web

New layout test guidelines - Google Groups
Dear blink-dev, I recently landed an almost-complete rewrite of the document that has best practices for writing layout tests.
Read more >
24182 - Slow layout tests that pass - Monorail
This is a general container bug for bugs that take a long time to run, but pass. We list them in test_expectations so...
Read more >
Testing in Chromium - Writing Web Tests
Text Tests output pure text which represents the DOM tree, the DOM inner text, internal data structure of Blink like layout tree or...
Read more >
Blink Scheduler - Google Docs
This document describes the Blink Scheduler, which is designed to overcome ... Some new tasks may make old tasks redundant, i.e. layout->load font->layout, ......
Read more >
Blink web tests (a.k.a. layout tests) · V8
V8's infrastructure continuously runs Blink's web tests to prevent integration problems with Chromium. This document describes what to do in case such a ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found