mochitest-a11y: intermittent "test_events_caretmove.html | Wrong caret offset for textbox - got 5, expected -1"

RESOLVED FIXED

Status

()

defect
RESOLVED FIXED
10 years ago
7 years ago

People

(Reporter: jrmuizel, Unassigned)

Tracking

(Blocks 1 bug, {intermittent-failure})

Trunk
x86
All
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [BK1])

Attachments

(3 attachments, 1 obsolete attachment)

Whiteboard: [orange]
Marco, Alex, any ideas what might have caused this? Any recent work in text box, and text area caret computation?  (Assuming this is a recent failure)
I don't think so. It sounds like timing issue. Rarely I get this on windows platform locally.
Just thinking aloud... I sometimes get errors when the test harness window isn't in the foreground. Could this happen on a tinderbox?
When running locally I get this bug in suite but not when run on its own.
Ditto for my fresh windows 7 build too.
OS: Mac OS X → All
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1252419853.1252427717.2284.gz
OS X 10.5.2 mozilla-central unit test on 2009/09/08 07:24:13

> 1232 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/a11y/accessible/test_events_caretmove.html | Wrong caret offset for textbox - got 5, expected -1
> 1233 ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/a11y/accessible/test_events_caretmove.html | Wrong caret offset for textarea - got 12, expected -1

Note that this failure happened after an "Error: Unable to restore focus, expect failures and timeouts." in test_unsafeBidiChars.xhtml, so it's possible that this failure was due to whatever went wrong there.  The error messages in test_events_caretmove.html exactly match those in comment 0's log, though, so I think this is the same problem.
Marco, I regularly get this bug locally on Mac. Until we can put time into our Mac a11y implementation I think we should mitigate the tbox tree noise. Thoughts?
Assignee: nobody → bolterbugz
Attachment #402166 - Flags: review?(marco.zehe)
Attachment #402166 - Flags: review?(marco.zehe) → review+
Comment on attachment 402166 [details] [diff] [review]
patch (disable fragile tests for mac)

Yep makes sense! r=me
Pushed to trunk: http://hg.mozilla.org/mozilla-central/rev/a1283b105a34

Leaving, bug open. Please report instances on other platforms.
Just happened on windows again. I think I'll disable these tests for all platforms.
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox-Unittest/1253718770.1253721521.16968.gz
Linux mozilla-central test everythingelse on 2009/09/23 08:12:50
Blocks: 438871
Summary: ERROR TEST-UNEXPECTED-FAIL | chrome://mochikit/content/a11y/accessible/test_events_caretmove.html | Wrong caret offset for textbox - got 5, expected -1 → mochitest-a11y: intermittent "test_events_caretmove.html | Wrong caret offset for textbox - got 5, expected -1"
Comment on attachment 402372 [details] [diff] [review]
cover all platforms

OK!
Attachment #402372 - Flags: review?(marco.zehe) → review+
Posted patch less random timing (obsolete) — Splinter Review
This should remove one aspect of timing randomness.
(Related to bug 474952 comment 3)
Thoughts?
Attachment #414772 - Flags: review?(surkov.alexander)
Attachment #414772 - Flags: review?(marco.zehe)
Comment on attachment 414772 [details] [diff] [review]
less random timing

r=me, might make a sense, let's check
Attachment #414772 - Flags: review?(surkov.alexander) → review+
Comment on attachment 414772 [details] [diff] [review]
less random timing

Yes, let's try this! Thanks!
Attachment #414772 - Flags: review?(marco.zehe) → review+
Tryserver ran with failures on Win and Linux but not Mac.
Attachment #414772 - Attachment is obsolete: true
Attachment #415127 - Flags: review?(marco.zehe)
Attachment #415127 - Flags: review?(marco.zehe) → review+
(In reply to comment #20)
> Created an attachment (id=415127) [details]
> removed non deterministic tests.

Why are they non deterministic and why should they be removed?
(In reply to comment #21)
> (In reply to comment #20)
> > Created an attachment (id=415127) [details] [details]
> > removed non deterministic tests.
> 
> Why are they non deterministic

Probably not truly non deterministic (what is?).

> and why should they be removed?

I'm not sure what we gain by testing for -1 offsets.
(In reply to comment #22)

> Probably not truly non deterministic (what is?).

Still not sure I fully understand deterministic epithet.

> I'm not sure what we gain by testing for -1 offsets.

bug 448744
I see, then it would appear we have bug (sometimes).
Hasn't popped up in over two years. Closing WFM.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange] → [orange][BK1]
(In reply to Marco Zehe (:MarcoZ) from comment #26)
> Hasn't popped up in over two years. Closing WFM.

absolutely and it wont' pop up until tests are enabled
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Assignee: dbolter → nobody
Whiteboard: [orange][BK1] → [orange][BK1][test disabled]
fixed by bug 725581
Status: REOPENED → RESOLVED
Closed: 8 years ago7 years ago
Resolution: --- → FIXED
Whiteboard: [orange][BK1][test disabled] → [orange][BK1]
Whiteboard: [orange][BK1] → [BK1]
You need to log in before you can comment on or make changes to this bug.