Closed Bug 1091410 Opened 10 years ago Closed 3 years ago

Intermittent testLinkContextMenu | Exception caught - junit.framework.AssertionFailedError: Click can not be completed!

Categories

(Firefox for Android Graveyard :: General, defect, P3)

Product:
Firefox for Android Graveyard
Component:
General
Platform:
x86_64
Linux
Type:
defect

Tracking

(firefox34 affected, firefox35 affected, firefox36 affected, firefox-esr31 unaffected)

Status:
RESOLVED INCOMPLETE
Tracking Flags:
Tracking Status
firefox34 --- affected
firefox35 --- affected
firefox36 --- affected
firefox-esr31 --- unaffected

People

(Reporter: nigelb, Assigned: mfinkle)

References

(
URL
)

Details

(Keywords: intermittent-failure)

Attachments

(1 file)

wait-for-urlbar v0.1
1.89 KB, patch
bnicholson
: review+
Details | Diff | Splinter Review 
https://treeherder.mozilla.org/ui/logviewer.html#?job_id=3421662&repo=mozilla-inbound

builder 	Android 4.2 x86 Emulator mozilla-inbound opt test androidx86-set-4
buildid 	20141029194317
builduid 	c244ee7a27fb4a7c8225999c7d50479e
results 	warnings (1)
revision 	de7878c31f76
slave 	talos-linux64-ix-056
starttime 	Thu Oct 30 2014 08:32:17 GMT+0530 (IST)

20:39:11 INFO - runtests.py | Server pid: 3312
20:39:11 INFO - runtests.py | Websocket server pid: 3314
20:39:11 INFO - runtests.py | SSL tunnel pid: 3316
20:39:11 INFO - runtests.py | Running tests: start.
20:39:11 INFO -
20:39:11 INFO - Robocop process name: org.mozilla.fennec
20:39:11 INFO - INFO | automation.py | Application pid: 0
20:39:11 INFO - SimpleTest START
20:39:11 INFO - TEST-START | testLinkContextMenu
20:39:11 INFO - TEST-PASS | testLinkContextMenu | Robocop tests need the test device screen to be powered on. -
20:39:11 INFO - EventExpecter: no longer listening for Gecko:Ready
20:39:11 INFO - 0 ERROR Exception caught during test! - junit.framework.AssertionFailedError: Click can not be completed!
20:39:11 WARNING - TEST-UNEXPECTED-FAIL | testLinkContextMenu | Exception caught - junit.framework.AssertionFailedError: Click can not be completed!
20:39:11 INFO - INFO | automation.py | Application ran for: 0:00:29.598850
20:39:11 INFO - INFO | zombiecheck | Reading PID log: /tmp/tmplFShNTpidlog
20:39:11 INFO - Contents of /data/anr/traces.txt:
20:39:11 INFO -
20:39:11 INFO -
20:39:11 INFO - /data/tombstones does not exist; tombstone check skipped
20:39:11 INFO - Stopping web server
20:39:11 INFO - Stopping web socket server
20:39:11 INFO - Stopping ssltunnel
20:39:11 INFO - WARNING | leakcheck | refcount logging is off, so leaks can't be detected!
20:39:11 INFO - runtests.py | Running tests: end.
20:39:11 WARNING - PROCESS-CRASH | Automation Error: Missing end of test marker (process crashed?)
Keywords: intermittent-failure
It might have nothign to do with it, but for some reason I see a group of "ExchangeService" failures occurring around the time of the test failure.

Can we see about turning the Exchange Service off on these Android 4.2 x86 Emulator devices?
Flags: needinfo?(gbrown)
I found this Robotium discussion:
https://code.google.com/p/robotium/issues/detail?id=448

"The way in which Robotium works is that it sends a pointer sync and in that
way emulates a real user clicking somewhere. It asks a view where it is
located and then sends a pointer sync that location. When you are using
your app with non-window the view will give incorrect values back as its
not really shown in any window."
(In reply to Mark Finkle (:mfinkle) from comment #3)
> It might have nothign to do with it, but for some reason I see a group of
> "ExchangeService" failures occurring around the time of the test failure.
> 
> Can we see about turning the Exchange Service off on these Android 4.2 x86
> Emulator devices?

I think those messages are harmless, but filed bug 1092192 anyway.
Flags: needinfo?(gbrown)
(In reply to Mark Finkle (:mfinkle) from comment #7)
> I found this Robotium discussion:
> https://code.google.com/p/robotium/issues/detail?id=448
> 
> "The way in which Robotium works is that it sends a pointer sync and in that
> way emulates a real user clicking somewhere. It asks a view where it is
> located and then sends a pointer sync that location. When you are using
> your app with non-window the view will give incorrect values back as its
> not really shown in any window."

That issue seems to be blaming use of the -no-window option when starting the emulator. We do not pass -no-window:

Trying to start the emulator with this command: emulator -avd test-1 -debug init,console,gles,memcheck,adbserver,adbclient,adb,avd_config,socket -port 5554 -qemu -m 1024 -enable-kvm
Just playing a hunch. I saw someone suggest waiting for the view before trying to click it.
Attachment #8515030 - Flags: review?(bnicholson)
(In reply to Mark Finkle (:mfinkle) from comment #10)
> Created attachment 8515030 [details] [diff] [review]
> wait-for-urlbar v0.1
> 
> Just playing a hunch. I saw someone suggest waiting for the view before
> trying to click it.

This has 4 green S4 runs so far:
https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=bb958fddd3a7

I retriggered more
(In reply to Mark Finkle (:mfinkle) from comment #11)
> (In reply to Mark Finkle (:mfinkle) from comment #10)
> > Created attachment 8515030 [details] [diff] [review]
> > wait-for-urlbar v0.1
> > 
> > Just playing a hunch. I saw someone suggest waiting for the view before
> > trying to click it.
> 
> This has 4 green S4 runs so far:
> https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=bb958fddd3a7
> 
> I retriggered more

Three more green runs
Attachment #8515030 - Flags: review?(bnicholson) → review+
https://hg.mozilla.org/mozilla-central/rev/e9fc0e0b2cbf
Assignee: nobody → mark.finkle
Status: NEW → RESOLVED
Closed: 10 years ago
status-firefox34: --- → affected
status-firefox35: --- → affected
status-firefox36: --- → fixed
status-firefox-esr31: --- → unaffected
Resolution: --- → FIXED
Target Milestone: --- → Firefox 36
Mark, this seems to happen again https://treeherder.mozilla.org/ui/logviewer.html#?job_id=3612609&repo=mozilla-inbound , could you take a look, thanks!
Status: RESOLVED → REOPENED
Flags: needinfo?(mark.finkle)
Resolution: FIXED → ---
Won't have time to look until I get really frustrated again...
Flags: needinfo?(mark.finkle)
Bulk assigning P3 to all open intermittent bugs without a priority set in Firefox components per bug 1298978.
Priority: -- → P3
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 3 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: