Closed Bug 1704191 Opened 3 years ago Closed 3 years ago

Running telemetry-tests-client not using mach telemetry-tests-client fails with "Not in PYTHON_UNITTEST_MANIFESTS?"

Categories

(Toolkit :: Telemetry, defect)

Product:
Toolkit
Component:
Telemetry
Type:
defect

Tracking

()

Status:
RESOLVED INVALID

People

(Reporter: chutten, Unassigned)

References

(Regression)

Details

(Keywords: regression)

Running ./mach python-test toolkit/components/telemetry/tests/marionette/tests/client/ fails with:

 0:01.01 TEST-UNEXPECTED-FAIL | No tests collected (Not in PYTHON_UNITTEST_MANIFESTS?)

It didn't used to do this. And I'm pretty sure it still shouldn't.

(( I might be wrong about this being regressed by bug 1638991, but it seemed likely. ))

Flags: needinfo?(rpierzina)
Flags: needinfo?(ahal)

For whatever reason this suite ended up being implemented as its own thing rather than as part of the regular python-test harness, so you're looking for:

./mach telemetry-tests-client

I don't recall why it's its own harness, with infinite time I'd probably make it use ./mach python-test.

Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(ahal)
Resolution: --- → INVALID
Flags: needinfo?(rpierzina)

I just tried to run the above command against e4517a8133cf1a96e15c1e1128009e7b44877e69 (the parent revision of the Python 3 commit stack) and I see the same error message. I have not tried running this before and always used ./mach telemetry-tests-client.

FWIW I don't know why this suite was originally set up this way, but we've decided to implement the pytest based telemetry integration tests using python-test in bug 1560185.

Has Regression Range: --- → yes
Keywords: regression
You need to log in before you can comment on or make changes to this bug.