Open Bug 1715293 Opened 3 years ago Updated 3 years ago

Generating private key for OTR fails in some test conditions

Categories

(Chat Core :: Security: OTR, defect)

defect

Tracking

(Not tracked)

People

(Reporter: freaktechnik, Unassigned)

References

Details

FAIL A promise chain failed to handle a rejection: Generating OTR private key failed: otrl_privkey_generate_start (536903715) - stack: reportKeyGenFailure@resource:///modules/OTRUI.jsm:213:11
Rejection date: Tue Jun 08 2021 16:42:24 GMT+0200 (Mitteleuropäische Sommerzeit) - false == true - JS frame :: resource://testing-common/PromiseTestUtils.jsm :: assertNoUncaughtRejections :: line 285
Stack trace:
resource://testing-common/PromiseTestUtils.jsm:assertNoUncaughtRejections:285
chrome://mochikit/content/browser-test.js:nextTest:628
chrome://mochikit/content/browser-test.js:testScope/test_finish/<:1553
chrome://mochikit/content/browser-test.js:run:1468

This is the error you'd get with some tests (this one is from browser_accountTelemetry, but similar ones happen with the chat browser tests) in --verify mode. Due to this OTR is disabled in most browser tests that touch chat stuff currently (chat.otr.enable=false in browser.ini).

This is likely a race where the test destroys the account while OTR is generating the key and then fails, or a generation from a previous test account is still running when a new account for the next test is created.

See Also: → 1714761
Summary: Generating private key fails in some test conditions → Generating private key for OTR fails in some test conditions
You need to log in before you can comment on or make changes to this bug.