Closed Bug 633944 Opened 13 years ago Closed 13 years ago

Test failure in testStartStopPBMode.js | could not find element ID: community

Categories

(Mozilla QA Graveyard :: Mozmill Tests, defect)

x86
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: aaronmt, Assigned: aaronmt)

References

()

Details

(Keywords: regression, Whiteboard: [mozmill-test-failure])

Attachments

(2 files)

Do you already know why that happens? Has there anything being changed for PB mode a couple of days ago?
Unable to reproduce locally, I'll take a look on the QA machines.
This probably requires the same fix as bug 633959.
Indeed!
Attachment #512479 - Flags: review?(hskupin)
Comment on attachment 512479 [details] [diff] [review]
Patch v1 - (default)

Looks good in general. But could you add a comment to both tests? I completely forgot about it yesterday. We have to know here why a waitForElement call is necessary.
Attachment #512479 - Flags: review?(hskupin) → review-
I'll put the followup patch in the other module in the other bug.
Attachment #512480 - Flags: review?(hskupin)
Attachment #512480 - Flags: review?(hskupin) → review+
Attachment #512480 - Attachment description: Patch v1 - (default) → Patch v1 - (default) [checked-in]
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: