Open
Bug 1690174
Opened 4 years ago
Updated 3 years ago
Gtest custom tasks are busted
Categories
(Testing :: General, defect, P3)
Tracking
(Not tracked)
NEW
People
(Reporter: glandium, Unassigned)
References
Details
They currently use mach in a standalone manner, which recent development in mach has completely broken. The test archives are missing a bunch of modules. Once we're past that, mach tries to load build/moz.configure/init.configure, which also needs a bunch more files. And once you're past that, they fail with:
[task 2021-01-29T11:58:38.954Z]
[task 2021-01-29T11:58:38.954Z] TypeError: 'NoneType' object is not callable
[task 2021-01-29T11:58:38.954Z]
[task 2021-01-29T11:58:38.954Z] File "/builds/worker/workspace/build/tests/gtest/mach_test_package_commands.py", line 131, in gtest
[task 2021-01-29T11:58:38.954Z] self._mach_context.activate_mozharness_venv()
Comment 1•4 years ago
|
||
I don't have enough knowledge on what's happening here:
- What is "mach in a standalone manner"? Is that "out-of-tree" mach?
- What's a GTest "custom task"? The (non-custom?) tasks in mozilla-central are happy.
- How do you create/run a GTest custom task to reproduce this issue?
- Can you link the task that failed whose output you've copied here?
Flags: needinfo?(mh+mozilla)
Comment 2•3 years ago
|
||
Clearing stale needinfos (please re-request if still needed)
Flags: needinfo?(mh+mozilla)
Updated•3 years ago
|
Severity: -- → S3
Priority: -- → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•