1907609 - Perma TEST-UNEXPECTED-TIMEOUT | browser/components/backup/tests/xpcshell/test_BackupService_archive.js | Test timed out when Gecko 130 merges to Beta on 2024-08-05

Status: RESOLVED DUPLICATE of bug 1906912

(Firefox :: Profile Backup, defect)

Description

[Sandor Molnar[:smolnar]]

Central as Beta Simulation

How to run these simulations

Failure log

TEST-START | browser/components/backup/tests/xpcshell/test_BackupService_archive.js
[task 2024-07-12T15:07:22.644Z] 15:07:22  WARNING -  TEST-UNEXPECTED-TIMEOUT | browser/components/backup/tests/xpcshell/test_BackupService_archive.js | Test timed out
[task 2024-07-12T15:07:22.644Z] 15:07:22     INFO -  TEST-INFO took 300184ms
[task 2024-07-12T15:07:22.644Z] 15:07:22     INFO -  >>>>>>>
[task 2024-07-12T15:07:22.644Z] 15:07:22     INFO -  (xpcshell/head.js) | test MAIN run_test pending (1)
[task 2024-07-12T15:07:22.644Z] 15:07:22     INFO -  (xpcshell/head.js) | test run_next_test 0 pending (2)
[task 2024-07-12T15:07:22.645Z] 15:07:22     INFO -  (xpcshell/head.js) | test MAIN run_test finished (2)
[task 2024-07-12T15:07:22.645Z] 15:07:22     INFO -  running event loop
[task 2024-07-12T15:07:22.645Z] 15:07:22     INFO -  browser/components/backup/tests/xpcshell/test_BackupService_archive.js | Starting setup
[task 2024-07-12T15:07:22.645Z] 15:07:22     INFO -  (xpcshell/head.js) | test pending (2)
[task 2024-07-12T15:07:22.645Z] 15:07:22     INFO -  (xpcshell/head.js) | test run_next_test 0 finished (2)
[task 2024-07-12T15:07:22.646Z] 15:07:22     INFO -  (xpcshell/head.js) | test run_next_test 1 pending (2)
[task 2024-07-12T15:07:22.646Z] 15:07:22     INFO -  (xpcshell/head.js) | test finished (2)
[task 2024-07-12T15:07:22.646Z] 15:07:22     INFO -  browser/components/backup/tests/xpcshell/test_BackupService_archive.js | Starting test_createArchive_unencrypted
[task 2024-07-12T15:07:22.646Z] 15:07:22     INFO -  (xpcshell/head.js) | test test_createArchive_unencrypted pending (2)
[task 2024-07-12T15:07:22.646Z] 15:07:22     INFO -  PID 5943 | console.debug: BackupService: "Instantiated"
[task 2024-07-12T15:07:22.646Z] 15:07:22     INFO -  (xpcshell/head.js) | test run_next_test 1 finished (2)
[task 2024-07-12T15:07:22.647Z] 15:07:22     INFO -  PID 5943 | JavaScript error: resource:///modules/backup/BackupService.sys.mjs, line 1863: NS_BINDING_ABORTED: Got JSON block. Aborting further reads.
[task 2024-07-12T15:07:22.647Z] 15:07:22     INFO -  "CONSOLE_MESSAGE: (error) [JavaScript Error: "NS_BINDING_ABORTED: Got JSON block. Aborting further reads." {file: "resource:///modules/backup/BackupService.sys.mjs" line: 1863}]
[task 2024-07-12T15:07:22.647Z] 15:07:22     INFO -  onStopRequest@resource:///modules/backup/BackupService.sys.mjs:1863:30
[task 2024-07-12T15:07:22.647Z] 15:07:22     INFO -  _do_main@/opt/worker/tasks/task_172079552098256/build/tests/xpcshell/head.js:245:6
[task 2024-07-12T15:07:22.648Z] 15:07:22     INFO -  _execute_test@/opt/worker/tasks/task_172079552098256/build/tests/xpcshell/head.js:596:5
[task 2024-07-12T15:07:22.648Z] 15:07:22     INFO -  @-e:1:1
[task 2024-07-12T15:07:22.648Z] 15:07:22     INFO -  "
[task 2024-07-12T15:07:22.648Z] 15:07:22     INFO -  PID 5943 | console.debug: BackupService: "Read out archive JSON: " ({version:1, encConfig:null, meta:{date:"2024-06-07T00:00:00+00:00", appName:"firefox", appVersion:"128.0", buildID:"20240604133346", profileName:"profile-default", machineName:"A super cool machine", osName:"Windows_NT", osVersion:"10.0", legacyClientID:"decafbad-0cd1-0cd2-0cd3-decafbad1000", accountID:"", accountEmail:""}})
[task 2024-07-12T15:07:22.649Z] 15:07:22     INFO -  TEST-PASS | browser/components/backup/tests/xpcshell/test_BackupService_archive.js

Comment 1

[Stephen Thompson [:sthompson]]

Test is hanging after ArchiveEncryptionState.initialize and before BackupService.#extractJSONFromArchive completes, but there's a fair amount of code in between. I will try to reproduce this.

Comment 2

[Stephen Thompson [:sthompson]]

Looks like the same as https://bugzilla.mozilla.org/show_bug.cgi?id=1906912 Would you prefer to track the issue there?