Closed Bug 1750251 Opened 2 years ago Closed 2 years ago

Perma Late-Beta macOS spi-nw TEST-UNEXPECTED-TIMEOUT | security/manager/ssl/tests/unit/test_cert_chains.js | Test timed out - when Gecko 98 merges to Beta on 2022-02-18

Categories

(Core :: Security: PSM, defect)

defect

Tracking

()

VERIFIED FIXED
98 Branch
Tracking Status
firefox-esr91 --- unaffected
firefox96 --- unaffected
firefox97 --- unaffected
firefox98 + verified

People

(Reporter: smolnar, Assigned: kershaw)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file, 1 obsolete file)

Central-as-late-beta simulation

How to run these simulations

Failure log

INFO -  TEST-PASS | security/manager/ssl/tests/unit/test_cert_chains.js |  - failedCertChain should be deserialized correctly - true == true
[task 2022-01-14T13:56:54.898Z] 13:56:54     INFO -  (xpcshell/head.js) | test run_next_test 7 pending (3)
[task 2022-01-14T13:56:54.898Z] 13:56:54     INFO -  (xpcshell/head.js) | test finished (3)
[task 2022-01-14T13:56:54.899Z] 13:56:54     INFO -  (xpcshell/head.js) | test run_next_test 6 finished (2)
[task 2022-01-14T13:56:54.899Z] 13:56:54     INFO -  security/manager/ssl/tests/unit/test_cert_chains.js | Starting
[task 2022-01-14T13:56:54.899Z] 13:56:54     INFO -  (xpcshell/head.js) | test pending (2)
[task 2022-01-14T13:56:54.899Z] 13:56:54     INFO -  (xpcshell/head.js) | test run_next_test 7 finished (2)
[task 2022-01-14T13:56:54.899Z] 13:56:54     INFO -  <<<<<<<
[task 2022-01-14T13:56:54.899Z] 13:56:54     INFO -  xpcshell return code: None
[task 2022-01-14T13:56:54.899Z] 13:56:54     INFO -  security/manager/ssl/tests/unit/test_cert_chains.js | Process still running after test!
[task 2022-01-14T13:56:55.093Z] 13:56:55  WARNING -  TEST-UNEXPECTED-FAIL | Received SIGINT (control-C), so stopped run. (Use --keep-going to keep running tests after killing one with SIGINT)
[task 2022-01-14T13:56:55.094Z] 13:56:55     INFO -  Retrying tests that failed when run in parallel.
[task 2022-01-14T13:56:55.102Z] 13:56:55     INFO -  TEST-START | browser/components/urlbar/tests/unit/test_providerPlaces.js
[task 2022-01-14T13:56:56.436Z] 13:56:56  WARNING -  TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/unit/test_providerPlaces.js | xpcshell return code: 0
[task 2022-01-14T13:56:56.436Z] 13:56:56     INFO -  TEST-INFO took 1334ms
Flags: needinfo?(dkeeler)

Is this related to bug 1748341? (Previous cenral-as-late-beta had been run on Tuesday). It's not from bug 1747320. The failure is only observed on macOS with the new socket process code.

Keywords: regression
Summary: Perma Late-Beta TEST-UNEXPECTED-TIMEOUT | security/manager/ssl/tests/unit/test_cert_chains.js | Test timed out - when Gecko 98 merges to Beta on 2022-02-07 → Perma Late-Beta macOS spi-nw TEST-UNEXPECTED-TIMEOUT | security/manager/ssl/tests/unit/test_cert_chains.js | Test timed out - when Gecko 98 merges to Beta on 2022-02-18

Bug 1741425 turned on the execution of xpcshell tests with socket process. Kershaw, could you take care of the tests which fail in central-as-late-beta simulations, very likely because network.process.enabled is false for late beta and release?

Has Regression Range: --- → yes
Flags: needinfo?(dkeeler) → needinfo?(kershaw)
Regressed by: 1741425

(In reply to Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout) from comment #2)

Bug 1741425 turned on the execution of xpcshell tests with socket process. Kershaw, could you take care of the tests which fail in central-as-late-beta simulations, very likely because network.process.enabled is false for late beta and release?

I think the reason is something else. network.process.enabled should be set to true when running socket process tests.
We can disable this test for now.

Flags: needinfo?(kershaw)
Assignee: nobody → kershaw
Status: NEW → ASSIGNED

Not sure why there are so many tests failed, but I think it's fine to not running these tests with socket process.
:ahal, do you know is there a way to not run socket process tests on late beta?
Thanks.

Flags: needinfo?(ahal)

In this case you could change the built-projects to ["trunk"] here:
https://searchfox.org/mozilla-central/source/taskcluster/ci/test/xpcshell.yml#48

Though this only affects xpcshell.

Once you have a patch you could run ./mach taskgraph target --diff -p taskcluster/test/params --target-kind test --fast to verify your changes do what you expect (or you could also submit to Phabricator and wait for reviewbot to comment with a diff of tasks).

Flags: needinfo?(ahal)
Attachment #9259312 - Attachment is obsolete: true

This would be nice to have on ESR too where we're running spi tests without any real need to.

(In reply to Ryan VanderMeulen [:RyanVM] from comment #9)

This would be nice to have on ESR too where we're running spi tests without any real need to.

Do you mean spi or spi-nw tests?
As far as I know, spi tests are about testing WebRTC code on socket process and WebRTC team is close to ship this feature. So, I think we should keep spi tests on ESR.

We're running spi-nw xpcshell on ESR91, also spi mochitest-media. Regardless, if it's not shipping yet, we're certainly not going to be backporting that to an already-existing ESR branch.

Pushed by kjang@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c02e7f75b9ec
Not run socket process tests on late beta, r=ahal
See Also: → 1751338
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 98 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: