1893912 - Intermittent /IndexedDB/idbobjectstore_delete.any.worker.html | single tracking bug

Status: RESOLVED INCOMPLETE

(Core :: Storage: IndexedDB, defect, P5)

Description

[Treeherder Bug Filer]

Filed by: sstanca [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer?job_id=456200908&repo=mozilla-central
Full log: https://firefox-ci-tc.services.mozilla.com/api/queue/v1/task/Itn-E_5GSw-iBwkwp4ibSQ/runs/0/artifacts/public/logs/live_backing.log

---

[task 2024-04-29T00:24:15.506Z] 00:24:15     INFO - TEST-PASS | /IndexedDB/idbobjectstore_delete.any.worker.html | If the transaction this IDBObjectStore belongs to has its mode set to readonly, throw ReadOnlyError 
[task 2024-04-29T00:24:15.507Z] 00:24:15     INFO - TEST-UNEXPECTED-TIMEOUT | /IndexedDB/idbobjectstore_delete.any.worker.html | If the object store has been deleted, the implementation must throw a DOMException of type InvalidStateError - Test timed out
[task 2024-04-29T00:24:15.507Z] 00:24:15     INFO - TEST-UNEXPECTED-TIMEOUT | /IndexedDB/idbobjectstore_delete.any.worker.html | expected OK
[task 2024-04-29T00:24:15.507Z] 00:24:15     INFO - TEST-INFO took 10244ms
[task 2024-04-29T00:24:15.510Z] 00:24:15     INFO - PID 1568 | 1714350255506	Marionette	INFO	Stopped listening on port 49879
[task 2024-04-29T00:24:19.474Z] 00:24:19     INFO - Browser exited with return code 0
[task 2024-04-29T00:24:19.476Z] 00:24:19     INFO - Closing logging queue
[task 2024-04-29T00:24:19.477Z] 00:24:19     INFO - queue closed
[task 2024-04-29T00:24:19.780Z] 00:24:19     INFO - Application command: D:\task_171434811997954\build\application\firefox\firefox.exe -marionette about:blank --wait-for-browser -profile C:\Users\task_171434811997954\AppData\Local\Temp\tmptkcu6ghr
[task 2024-04-29T00:24:19.790Z] 00:24:19     INFO - PID 3536 | 1714350088501	Marionette	INFO	Marionette enabled
[task 2024-04-29T00:24:19.790Z] 00:24:19     INFO - PID 3536 | 1714350088588	Marionette	INFO	Listening on port 49880
[task 2024-04-29T00:24:19.791Z] 00:24:19     INFO - PID 3536 | [ERROR error_support::handling] suggest-unexpected: Error from Remote Settings: Error parsing URL: relative URL with a cannot-be-a-base base
[task 2024-04-29T00:24:19.792Z] 00:24:19     INFO - PID 3536 | console.error: URLBar - QuickSuggest.SuggestBackendRust: "Ingest error: Error from Remote Settings: Error parsing URL: relative URL with a cannot-be-a-base base"
[task 2024-04-29T00:24:19.793Z] 00:24:19     INFO - Starting runner
[task 2024-04-29T00:24:21.540Z] 00:24:21     INFO - TEST-START | /IndexedDB/idbobjectstore_deleteIndex.any.html
[task 2024-04-29T00:24:21.555Z] 00:24:21     INFO - Setting pref extensions.blocklist.enabled to false
[task 2024-04-29T00:24:25.119Z] 00:24:25     INFO - .
[task 2024-04-29T00:24:25.119Z] 00:24:25     INFO - TEST-OK | /IndexedDB/idbobjectstore_deleteIndex.any.html | took 3580ms

Comment 1

[Intermittent Failures Robot]

1 failures in 4336 pushes (0.0 failures/push) were associated with this bug in the last 7 days.

Repository breakdown:

• mozilla-central: 1

Platform and build breakdown:

• windows11-64-2009-shippable-qr: 1
  • opt: 1

For more details, see:
https://treeherder.mozilla.org/intermittent-failures/bugdetails?bug=1893912&startday=2024-04-22&endday=2024-04-28&tree=all

Comment 2

[Jens Stutte [:jstutte]]

Looking at the profile from the test run it seems that many tests are taking quite some time in this run. And the CPU usage while idbobjectstore_delete.any.worker.html is running seems not different from the before running tests, so I assume there is no hang or such.

There might be a point in trying to reduce the runtime of quite some IndexedDB tests, like:

test — /IndexedDB/idbindex_getAllKeys.any.sharedworker.html
test — /IndexedDB/idbindex_getAllKeys.any.worker.html
test — /IndexedDB/idbindex_getAllKeys.any.serviceworker.html
test — /IndexedDB/idbobjectstore_delete.any.sharedworker.html
test — /IndexedDB/idbobjectstore_delete.any.html
test — /IndexedDB/idbobjectstore_delete.any.serviceworker.html
test — /IndexedDB/idbobjectstore_delete.any.worker.html
test — /IndexedDB/idbobjectstore_deleteIndex.any.html
test — /IndexedDB/idbobjectstore_deleteIndex.any.serviceworker.html
test — /IndexedDB/idbobjectstore_deleteIndex.any.worker.html
test — /IndexedDB/idbobjectstore_deleteIndex.any.sharedworker.html
test — /IndexedDB/idbobjectstore_get.any.worker.html
test — /IndexedDB/idbobjectstore_get5.any.worker.html
test — /IndexedDB/idbobjectstore_get5.any.html
test — /IndexedDB/idbobjectstore_get6.any.worker.html
test — /IndexedDB/idbobjectstore_get6.any.html
test — /IndexedDB/idbobjectstore_getAll.any.html
test — /IndexedDB/idbobjectstore_getAll.any.worker.html
test — /IndexedDB/idbobjectstore_getAllKeys.any.html
test — /IndexedDB/idbobjectstore_getAllKeys.any.worker.html
test — /IndexedDB/idbobjectstore_getKey.any.worker.html
test — /IndexedDB/idbobjectstore_getKey.any.html
test — /IndexedDB/idbobjectstore_put.any.serviceworker.html
test — /IndexedDB/idbobjectstore_put.any.html
test — /IndexedDB/interleaved-cursors-large.html
test — /IndexedDB/interleaved-cursors-small.html

Comment 3

[Jens Stutte [:jstutte]]

IIUC these are WPT tests, are they part of the official ones? There might also be a point in just raising the timeouts, of course.

Comment 4

[Jan Varga [:janv]]

Is there something like requestLongerTimeout for WPT ?

Comment 5

[Jens Stutte [:jstutte]]

Attachment: NormalRuntime.png

Taken from this profile found on this run from the same push.

Comment 6

[Jens Stutte [:jstutte]]

Attachment: SlowRuntime.png

Taken from the timed out profile.

Comment 7

[Jens Stutte [:jstutte]]

It looks like several tests running immediately before and after that test on that run were running significantly slower than normal. This seems to be a temporary condition of that machine, as tests run before and later seem to execute with comparable times.

From CPU load and IO track there seem to be no evident differences. So the only thing that might explain such a behavior could be a temporary CPU throttling, but I might misread the "CPU use" lane.

Comment 8

[Jari Jalkanen]

The resource usage for normal and slower runs also looks very similar.

The normal one was running on region westus2, the slow one on westus. Not sure if this is a systematic difference. Maybe there's a difference in how much other load there is on these two regions?

Comment 9

[BugBot [:suhaib / :marco/ :calixte]]

https://wiki.mozilla.org/Bug_Triage#Intermittent_Test_Failure_Cleanup
For more information, please visit BugBot documentation.