Closed
Bug 1171065
Opened 11 years ago
Closed 4 years ago
test_async_transitions.js sometimes takes a very long time to run
Categories
(Toolkit :: Places, defect, P3)
Toolkit
Places
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: RyanVM, Unassigned)
References
Details
I observed a Win7 opt run today that took over 200 seconds to run. Windows slaves are physical hardware (not VMs in the cloud). I haven't done any more investigation of it, but mak asked me to file.
http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-win32/1433342620/mozilla-inbound_win7-ix_test-xpcshell-bm119-tests1-windows-build460.txt.gz
08:03:54 INFO - TEST-START | toolkit/components/places/tests/unit/test_async_transactions.js
08:07:15 INFO - TEST-PASS | toolkit/components/places/tests/unit/test_async_transactions.js | took 201537ms
Updated•11 years ago
|
Blocks: PlacesAsyncTransact
Updated•10 years ago
|
Priority: -- → P3
Comment 1•8 years ago
|
||
No reason to block the feature, I hope with the perf improvements it will become faster.
No longer blocks: PlacesAsyncTransact
Depends on: PlacesAsyncTransact
| Reporter | ||
Updated•4 years ago
|
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•