Closed
Bug 650553
Opened 14 years ago
Closed 11 years ago
[READY] test_webgl_conformance_test_suite.html needs to be explicit about its timeout requirements
Categories
(Core :: Graphics: CanvasWebGL, defect)
Tracking
()
RESOLVED
FIXED
mozilla32
People
(Reporter: ehsan.akhgari, Assigned: ehsan.akhgari)
References
Details
(Whiteboard: webgl-internal)
Attachments
(1 file)
|
1.10 KB,
patch
|
bjacob
:
review+
|
Details | Diff | Splinter Review |
No description provided.
|
Assignee | |
Comment 1•14 years ago
|
||
|
||
Comment 2•14 years ago
|
||
What does requestFlakyTimeout do?
|
|
Assignee | |
Comment 3•14 years ago
|
||
(In reply to comment #2)
> What does requestFlakyTimeout do?
See bug 649012. It enables the test to use setTimeout(f, t) where t>0 in exceptional cases (such as this one).
These types of timeouts in tests have always been a source of intermittent oranges for us, so I'm planning to disable using them in bug 649012.
|
|
||
Updated•14 years ago
|
Attachment #526520 -
Flags: review?(bjacob) → review+
|
|
Assignee | |
Updated•14 years ago
|
Summary: test_webgl_conformance_test_suite.html needs to be explicit about its timeout requirements → [READY] test_webgl_conformance_test_suite.html needs to be explicit about its timeout requirements
|
||
Comment 4•14 years ago
|
||
Ehsan, are you still planning to land this?
|
|
Assignee | |
Comment 5•14 years ago
|
||
Yes, but all of the dependencies of bug 649012 should get fixed first, and I don't have time to do that right now...
|
||
Updated•12 years ago
|
Whiteboard: webgl-internal
|
|
||
Comment 6•12 years ago
|
||
This probably has severe bitrot. Is this worth saving?
Flags: needinfo?(ehsan)
|
|
Assignee | |
Comment 7•12 years ago
|
||
Only if somebody starts to resurrect my work in bug 649012. This is one of the many dependencies there.
Flags: needinfo?(ehsan)
|
|
Assignee | |
Comment 8•11 years ago
|
||
|
|
||
Comment 9•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla32
You need to log in
before you can comment on or make changes to this bug.
Description
•