Closed Bug 1586035 Opened 5 years ago Closed 5 years ago

'mach test-info' does not show platform variants like -sw

Categories

(Testing :: General, defect, P1)

Version 3
defect

Tracking

(firefox71 fixed)

RESOLVED FIXED
mozilla71
Tracking Status
firefox71 --- fixed

People

(Reporter: gbrown, Assigned: gbrown)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

'mach test-info <test>' (changing to 'mach test-info tests <test>') reports test runs per-platform, but some platform variants, like -sw (service-workers), are not evident.

./mach test-info test_simple.js
...
Test results for netwerk/test/unit/test_simple.js on mozilla-central,mozilla-inbound,autoland between 2019-09-26 and 2019-10-03
android-em-7-0-x86_64/debug-e10s:             0 failures (     0 skipped) in    153 runs
android-em-7-0-x86_64/opt-e10s:               0 failures (     0 skipped) in    154 runs
linux32/debug:                                0 failures (     0 skipped) in     21 runs
linux32/opt:                                  0 failures (     0 skipped) in     26 runs
linux64-qr/debug-e10s:                        0 failures (     0 skipped) in    161 runs
linux64-qr/opt-e10s:                          0 failures (     0 skipped) in     20 runs
linux64-shippable-qr/opt-e10s:                0 failures (     0 skipped) in    155 runs
linux64/asan-opt-e10s:                        0 failures (     0 skipped) in    177 runs
linux64/ccov-debug-e10s:                      0 failures (     0 skipped) in     20 runs
linux64/debug-e10s:                           0 failures (     0 skipped) in    158 runs
linux64/debug-e10s:                           0 failures (     0 skipped) in     20 runs
linux64/debug:                                0 failures (     0 skipped) in     27 runs
linux64/opt-e10s:                             0 failures (     0 skipped) in    174 runs
linux64/opt:                                  0 failures (     0 skipped) in     38 runs
linux64/opt:                                  0 failures (     0 skipped) in     24 runs
macosx1014-64-shippable/opt-e10s:             0 failures (     0 skipped) in    151 runs
macosx1014-64-shippable/opt:                  0 failures (     0 skipped) in     37 runs
macosx1014-64/debug-e10s:                     0 failures (     0 skipped) in    165 runs
macosx1014-64/debug:                          0 failures (     0 skipped) in     23 runs
windows10-64-shippable/opt-e10s:              0 failures (     0 skipped) in    154 runs
windows10-64-shippable/opt:                   0 failures (     0 skipped) in     24 runs
windows10-64/ccov-debug-e10s:                 0 failures (     0 skipped) in     20 runs
windows10-64/debug-e10s:                      0 failures (     0 skipped) in    156 runs
windows10-64/debug:                           0 failures (     0 skipped) in     23 runs
windows10-64/opt-e10s:                        0 failures (     0 skipped) in     16 runs
windows10-64/opt:                             0 failures (     0 skipped) in     24 runs
windows10-aarch64/opt-e10s:                   0 failures (     0 skipped) in      5 runs
windows7-32-shippable/opt-e10s:               0 failures (     0 skipped) in    165 runs
windows7-32-shippable/opt:                    0 failures (     0 skipped) in     23 runs
windows7-32/debug-e10s:                       0 failures (     0 skipped) in    154 runs
windows7-32/debug:                            0 failures (     0 skipped) in     19 runs
windows7-32/opt-e10s:                         0 failures (     0 skipped) in     19 runs
windows7-32/opt:                              0 failures (     0 skipped) in     22 runs

The data is there, but parts of the platform label are suppressed.

This contributes to the problem of duplicate platforms seen in bug 1566017; however, there are also other factors affecting bug 1566017.

The run.type info returned by ActiveData can be a simple string or a list.

'chunked' is returned for many platforms, but is not of interest: It is currently suppressed, and that seems appropriate.

Fission tests have both 'e10s' and 'fission' run.type labels: Currently these are combined as 'fission', and that seems appropriate.

Other run.type labels are silently discarded, and that seems inappropriate.

If all run.type labels except 'chunked' and combining e10s/fission, the results are better:

$ ./mach test-info test_simple.js
...
Test results for netwerk/test/unit/test_simple.js on mozilla-central,mozilla-inbound,autoland between 2019-09-26 and 2019-10-03
android-em-7-0-x86_64/debug-e10s:             0 failures (     0 skipped) in    153 runs
android-em-7-0-x86_64/opt-e10s:               0 failures (     0 skipped) in    154 runs
linux32/debug:                                0 failures (     0 skipped) in     21 runs
linux32/opt:                                  0 failures (     0 skipped) in     26 runs
linux64-qr/debug-e10s-qr:                     0 failures (     0 skipped) in    161 runs
linux64-qr/opt-e10s-qr:                       0 failures (     0 skipped) in     20 runs
linux64-shippable-qr/opt-e10s-qr:             0 failures (     0 skipped) in    155 runs
linux64/asan-opt-e10s:                        0 failures (     0 skipped) in    177 runs
linux64/ccov-debug-e10s:                      0 failures (     0 skipped) in     20 runs
linux64/debug-e10s-service-worker:            0 failures (     0 skipped) in     20 runs
linux64/debug-e10s:                           0 failures (     0 skipped) in    158 runs
linux64/debug:                                0 failures (     0 skipped) in     27 runs
linux64/opt-e10s:                             0 failures (     0 skipped) in    174 runs
linux64/opt:                                  0 failures (     0 skipped) in     38 runs
linux64/opt:                                  0 failures (     0 skipped) in     24 runs
macosx1014-64-shippable/opt-e10s:             0 failures (     0 skipped) in    151 runs
macosx1014-64-shippable/opt:                  0 failures (     0 skipped) in     37 runs
macosx1014-64/debug-e10s:                     0 failures (     0 skipped) in    165 runs
macosx1014-64/debug:                          0 failures (     0 skipped) in     23 runs
windows10-64-shippable/opt-e10s:              0 failures (     0 skipped) in    154 runs
windows10-64-shippable/opt:                   0 failures (     0 skipped) in     24 runs
windows10-64/ccov-debug-e10s:                 0 failures (     0 skipped) in     20 runs
windows10-64/debug-e10s:                      0 failures (     0 skipped) in    156 runs
windows10-64/debug:                           0 failures (     0 skipped) in     23 runs
windows10-64/opt-e10s:                        0 failures (     0 skipped) in     16 runs
windows10-64/opt:                             0 failures (     0 skipped) in     24 runs
windows10-aarch64/opt-e10s:                   0 failures (     0 skipped) in      5 runs
windows7-32-shippable/opt-e10s:               0 failures (     0 skipped) in    165 runs
windows7-32-shippable/opt:                    0 failures (     0 skipped) in     23 runs
windows7-32/debug-e10s:                       0 failures (     0 skipped) in    154 runs
windows7-32/debug:                            0 failures (     0 skipped) in     19 runs
windows7-32/opt-e10s:                         0 failures (     0 skipped) in     19 runs
windows7-32/opt:                              0 failures (     0 skipped) in     22 runs

Note especially "linux64/debug-e10s-service-worker" instead of a second "linux64/debug-e10s".

Fission still looks good:

$ ./mach test-info test_sanitySimpletest.html
...
Test results for testing/mochitest/tests/Harness_sanity/test_sanitySimpletest.html on mozilla-central,mozilla-inbound,autoland between 2019-09-26 and 2019-10-03
android-em-7-0-x86_64/debug-e10s:             0 failures (     0 skipped) in    599 runs
android-em-7-0-x86_64/opt-e10s:               0 failures (     0 skipped) in    155 runs
linux64-qr/debug-e10s-qr:                     0 failures (     0 skipped) in    157 runs
linux64-qr/debug-fis-qr:                      0 failures (     0 skipped) in    104 runs
linux64-qr/opt-e10s-qr:                       0 failures (     0 skipped) in     19 runs
linux64-qr/opt-fis-qr:                        0 failures (     0 skipped) in     71 runs
linux64-shippable-qr/opt-e10s-qr:             0 failures (     0 skipped) in    158 runs
linux64/asan-opt-e10s:                        0 failures (     0 skipped) in    156 runs
linux64/ccov-debug-e10s:                      0 failures (     0 skipped) in     21 runs
linux64/ccov-debug-fis:                       0 failures (     0 skipped) in      1 runs
linux64/debug-e10s-service-worker:            0 failures (     0 skipped) in     18 runs
linux64/debug-e10s:                           0 failures (     0 skipped) in    154 runs
linux64/debug-fis:                            0 failures (     0 skipped) in     97 runs
linux64/opt-e10s:                             0 failures (     0 skipped) in    214 runs
linux64/opt-fis:                              0 failures (     0 skipped) in     46 runs
macosx1014-64-shippable/opt-e10s:             0 failures (     0 skipped) in    476 runs
macosx1014-64/debug-e10s:                     0 failures (     0 skipped) in    574 runs
windows10-64-qr/debug-e10s-qr:                0 failures (     0 skipped) in    148 runs
windows10-64-qr/opt-e10s-qr:                  0 failures (     0 skipped) in     20 runs
windows10-64-qr/opt-fis-qr:                   0 failures (     0 skipped) in     23 runs
windows10-64-shippable-qr/opt-e10s-qr:        0 failures (     0 skipped) in    163 runs
windows10-64-shippable/opt-e10s:              0 failures (     0 skipped) in    156 runs
windows10-64/asan-opt-e10s:                   0 failures (     0 skipped) in    159 runs
windows10-64/ccov-debug-e10s:                 0 failures (     0 skipped) in     21 runs
windows10-64/debug-e10s:                      0 failures (     0 skipped) in    156 runs
windows10-64/opt-e10s:                        0 failures (     0 skipped) in     21 runs
windows10-64/opt-fis:                         0 failures (     0 skipped) in     23 runs
windows10-aarch64/opt-e10s:                   0 failures (     0 skipped) in     17 runs
windows7-32-shippable/opt-e10s:               0 failures (     0 skipped) in    151 runs
windows7-32/debug-e10s:                       0 failures (     0 skipped) in    155 runs
windows7-32/opt-e10s:                         0 failures (     0 skipped) in     20 runs

Instead of choosing specific run.types of interest, like 'e10s', concatenate
all returned strings, eliminating known exceptions, like 'chunked'. Notably
this correctly displays "linux64/debug-e10s-service-worker".

Pushed by gbrown@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/1c345279dea6 Improve platform naming in 'mach test-info'; r=bc
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
Blocks: 1577302
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: