1598253 - AssertionError when trying to run wpt tests

Status: NEW

(Testing :: web-platform-tests, defect, P3)

Description

[Simon Giesecke [:sg] [he/him]]

When trying to run ./mach wpt --headless testing/web-platform/tests/IndexedDB/idbcursor-continue.htm, I get the following AssertionError:

AssertionError

  File "/home/simon/work/mozilla-unified/testing/web-platform/mach_commands.py", line 309, in run_wpt
    return self.run_web_platform_tests(**params)
  File "/home/simon/work/mozilla-unified/testing/web-platform/mach_commands.py", line 301, in run_web_platform_tests
    return wpt_runner.run(logger, **params)
  File "/home/simon/work/mozilla-unified/testing/web-platform/mach_commands_base.py", line 29, in run
    self.update_manifest(logger)
  File "/home/simon/work/mozilla-unified/testing/web-platform/mach_commands_base.py", line 49, in update_manifest
    **kwargs)
  File "/home/simon/work/mozilla-unified/testing/web-platform/manifestupdate.py", line 121, in run
    cache_root=kwargs["cache_root"])
  File "/home/simon/work/mozilla-unified/testing/web-platform/manifestupdate.py", line 190, in load_and_update
    cache_root=this_cache_root)
  File "/home/simon/work/mozilla-unified/testing/web-platform/tests/tools/manifest/manifest.py", line 578, in load_and_update
    changed = manifest.update(tree)
  File "/home/simon/work/mozilla-unified/testing/web-platform/tests/tools/manifest/manifest.py", line 328, in update
    assert rel_path in path_hash

I don't know how to run wpt tests otherwise, so any workaround would be appreciated!

Comment 1

[James Graham [:jgraham]]

Ugh. It seems like you somehow got a corrupt manifest. It will be fixed by a clobber (or by deleting the <objdir>/_tests/web-platform/meta/MANIFEST.json file). Further investigation is needed to understand why this happens (maybe it's possible if we aren't writing the manifest atomically?) and if we could better recover from it.

Comment 2

[James Graham [:jgraham]]

I"m removing the mach-busted blocker since I suspect this is a system-specific problem rather than something that's generally broken.

Comment 3

[Simon Giesecke [:sg] [he/him]]

(In reply to James Graham [:jgraham] from comment #1)

Ugh. It seems like you somehow got a corrupt manifest. It will be fixed by a clobber (or by deleting the <objdir>/_tests/web-platform/meta/MANIFEST.json file).

Thanks, that did it for now!

Comment 4

[Simon Giesecke [:sg] [he/him]]

Interestingly, I still run into this repeatedly now, and I can't remember this ever happened before I reported this. Removing the MANIFEST.json fixes it every time.

Comment 5

[BugBot [:suhaib / :marco/ :calixte]]

The priority flag is not set for this bug.
:jgraham, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 6

[James Graham [:jgraham]]

I can re-prioritise if this becomes more common, but there's some chance we'll change the manifest format to eliminate this problem.