simple tool based on current tree to find which test job a given test will run in
Categories
(Testing :: General, task, P3)
Tracking
(Not tracked)
People
(Reporter: jmaher, Unassigned)
Details
(Whiteboard: dev-prod-2020)
in chatting with :padenot, there is a usecase that would be helpful:
./mach find-job --platform windows-10-debug dom/media/webaudio/test/test_audioContextSuspendResumeClose.html or something, it it would answer "mda-2"
we have solved what looks like this problem in many ways in the past, I think making this use case might already exist or would be very low effort. Possibly the work we do to generate the test-info artifact could be part of a ./mach command that is filtered based on the input path and platform?
![]() |
||
Comment 1•5 years ago
|
||
Related, but different, 'mach test-info tests --show-tasks' reports where a test has run in the recent past:
$ ./mach test-info tests --show-tasks test_audioContextSuspendResumeClose.html
===== test_audioContextSuspendResumeClose.html =====
Found dom/media/webaudio/test/test_audioContextSuspendResumeClose.html in source control.
dom/media/webaudio/test/test_audioContextSuspendResumeClose.html found in manifest dom/media/webaudio/test/mochitest.ini
flavor: mochitest
skip-if: (os == "win" && processor == "aarch64")
Querying ActiveData...
Found records matching 'dom/media/webaudio/test/test_audioContextSuspendResumeClose.html' in ActiveData.
Test tasks for dom/media/webaudio/test/test_audioContextSuspendResumeClose.html on mozilla-central,autoland between 2020-02-05 and 2020-02-12
android-hw-p2-8-0-android-aarch64/debug-e10s: test-android-hw-p2-8-0-android-aarch64/debug-geckoview-mochitest-media-e10s-1 in 32 runs
android-hw-p2-8-0-android-aarch64/pgo-e10s: test-android-hw-p2-8-0-android-aarch64/pgo-geckoview-mochitest-media-e10s-1 in 32 runs
linux1804-64-asan/opt-asan-e10s-spi: test-linux1804-64-asan/opt-mochitest-media-spi-e10s-1 in 34 runs
linux1804-64-asan/opt-asan-e10s: test-linux1804-64-asan/opt-mochitest-media-e10s-1 in 23 runs
linux1804-64-qr/debug-e10s-qr-spi: test-linux1804-64-qr/debug-mochitest-media-spi-e10s-1 in 25 runs
linux1804-64-qr/debug-e10s-qr: test-linux1804-64-qr/debug-mochitest-media-e10s-1 in 29 runs
linux1804-64-qr/debug-qr-fis: test-linux1804-64-qr/debug-mochitest-media-fis-e10s-1 in 31 runs
linux1804-64-qr/opt-e10s-qr-spi: test-linux1804-64-qr/opt-mochitest-media-spi-e10s-1 in 4 runs
linux1804-64-qr/opt-e10s-qr: test-linux1804-64-qr/opt-mochitest-media-e10s-1 in 2 runs
linux1804-64-qr/opt-qr-fis: test-linux1804-64-qr/opt-mochitest-media-fis-e10s-1 in 6 runs
linux1804-64-shippable-qr/opt-e10s-qr-spi: test-linux1804-64-shippable-qr/opt-mochitest-media-spi-e10s-1 in 20 runs
linux1804-64-shippable-qr/opt-e10s-qr: test-linux1804-64-shippable-qr/opt-mochitest-media-e10s-1 in 25 runs
linux1804-64-shippable/opt-e10s-spi: test-linux1804-64-shippable/opt-mochitest-media-spi-e10s-1 in 23 runs
linux1804-64-shippable/opt-e10s: test-linux1804-64-shippable/opt-mochitest-media-e10s-1 in 24 runs
linux1804-64/debug-e10s-service-worker: test-linux1804-64/debug-mochitest-media-sw-e10s-1 in 4 runs
linux1804-64/debug-e10s-spi: test-linux1804-64/debug-mochitest-media-spi-e10s-1 in 24 runs
linux1804-64/debug-e10s: test-linux1804-64/debug-mochitest-media-e10s-1 in 28 runs
linux1804-64/debug-fis: test-linux1804-64/debug-mochitest-media-fis-e10s-1 in 4 runs
linux1804-64/opt-ccov-e10s-spi: test-linux1804-64-ccov/opt-mochitest-media-spi-e10s-1 in 6 runs
linux1804-64/opt-ccov-e10s: test-linux1804-64-ccov/opt-mochitest-media-e10s-1 in 4 runs
linux1804-64/opt-e10s-spi: test-linux1804-64/opt-mochitest-media-spi-e10s-1 in 4 runs
linux1804-64/opt-e10s: test-linux1804-64/opt-mochitest-media-e10s-1 in 5 runs
linux1804-64/opt-fis: test-linux1804-64/opt-mochitest-media-fis-e10s-1 in 6 runs
macosx1014-64-shippable/opt-e10s-spi: test-macosx1014-64-shippable/opt-mochitest-media-spi-e10s-1 in 32 runs
macosx1014-64-shippable/opt-e10s: test-macosx1014-64-shippable/opt-mochitest-media-e10s-1 in 25 runs
macosx1014-64/debug-e10s-spi: test-macosx1014-64/debug-mochitest-media-spi-e10s-1 in 119 runs
macosx1014-64/debug-e10s: test-macosx1014-64/debug-mochitest-media-e10s-1 in 17 runs
windows10-64-qr/debug-e10s-qr-spi: test-windows10-64-qr/debug-mochitest-media-spi-e10s in 30 runs
windows10-64-qr/debug-e10s-qr: test-windows10-64-qr/debug-mochitest-media-e10s in 24 runs
windows10-64-qr/opt-e10s-qr-spi: test-windows10-64-qr/opt-mochitest-media-spi-e10s in 3 runs
windows10-64-qr/opt-e10s-qr: test-windows10-64-qr/opt-mochitest-media-e10s in 2 runs
windows10-64-qr/opt-qr-fis: test-windows10-64-qr/opt-mochitest-media-fis-e10s in 3 runs
windows10-64-shippable-qr/opt-e10s-qr-spi: test-windows10-64-shippable-qr/opt-mochitest-media-spi-e10s in 20 runs
windows10-64-shippable-qr/opt-e10s-qr: test-windows10-64-shippable-qr/opt-mochitest-media-e10s in 40 runs
windows10-64-shippable/opt-e10s-spi: test-windows10-64-shippable/opt-mochitest-media-spi-e10s in 22 runs
windows10-64-shippable/opt-e10s: test-windows10-64-shippable/opt-mochitest-media-e10s in 26 runs
windows10-64/debug-e10s-spi: test-windows10-64/debug-mochitest-media-spi-e10s in 28 runs
windows10-64/debug-e10s: test-windows10-64/debug-mochitest-media-e10s in 23 runs
windows10-64/opt-asan-e10s-spi: test-windows10-64-asan/opt-mochitest-media-spi-e10s in 33 runs
windows10-64/opt-asan-e10s: test-windows10-64-asan/opt-mochitest-media-e10s in 26 runs
windows10-64/opt-ccov-e10s-spi: test-windows10-64-ccov/opt-mochitest-media-spi-e10s in 3 runs
windows10-64/opt-ccov-e10s: test-windows10-64-ccov/opt-mochitest-media-e10s in 2 runs
windows10-64/opt-e10s-spi: test-windows10-64/opt-mochitest-media-spi-e10s in 4 runs
windows10-64/opt-e10s: test-windows10-64/opt-mochitest-media-e10s in 5 runs
windows10-64/opt-fis: test-windows10-64/opt-mochitest-media-fis-e10s in 4 runs
windows10-aarch64/opt-e10s-spi: test-windows10-aarch64/opt-mochitest-media-spi-e10s in 5 runs
windows10-aarch64/opt-e10s: test-windows10-aarch64/opt-mochitest-media-e10s in 8 runs
windows7-32-shippable/opt-e10s-spi: test-windows7-32-shippable/opt-mochitest-media-spi-e10s-1 in 23 runs
windows7-32-shippable/opt-e10s: test-windows7-32-shippable/opt-mochitest-media-e10s-1 in 21 runs
windows7-32/debug-e10s-spi: test-windows7-32/debug-mochitest-media-spi-e10s-1 in 27 runs
windows7-32/debug-e10s: test-windows7-32/debug-mochitest-media-e10s-1 in 25 runs
windows7-32/opt-e10s-spi: test-windows7-32/opt-mochitest-media-spi-e10s-1 in 1 runs
windows7-32/opt-e10s: test-windows7-32/opt-mochitest-media-e10s-1 in 4 runs
![]() |
||
Updated•5 years ago
|
Reporter | ||
Updated•5 years ago
|
Reporter | ||
Comment 2•5 years ago
|
||
:padenot, in comment 1 above, there is a list of jobs that ran on various platforms with the correct chunk number. This is using historical data vs data from your current tip of changed code. I would imagine most of the time this would work, with some edge cases. Will this work for you? Do you have other needs or tweaks that we could implement?
Comment 3•5 years ago
|
||
This gives the right info, but the hard part here is to drive adoption to reduce wasted machine-hours and developer frustration, and this will only happen if people know about this.
Updated•3 years ago
|
Description
•