877101 - mozmill fails to reopen Firefox after a restart on Linux

Status: RESOLVED WORKSFORME

(Testing Graveyard :: Mozmill, defect)

Description

[Andrei Eftimie]

In mozmill 2.0 restarting Firefox has _sometimes_ the effect of not being able to reopen it, and failing with:
> Disconnect Error: Application unexpectedly closed
> ...
> Exception: Cannot connect to jsbridge extension, port 50140

This only seems to happen on Linux: Ubuntu 13.04, Ubuntu 12.10 and Ubuntu 12.04

I'm attaching a testcase.

Comment 1

[Andrei Eftimie]

Attachment: testcase 1

Run this with mozmill 2.0 under linux.
It might not crash on the first run, but it should in at least 3 runs.

Comment 2

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Please add a full log so we can get an impression what's going on. This is most likely not blocking 2.0 given that this affects restart tests.

Comment 3

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Sounds like a dupe of bug 865690 but for now I will mark it as dependency.

Comment 4

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Is this fixed with my fix on bug 893026?

Comment 5

[Andrei Eftimie]

Attachment: testcase 2

It still fails for me.
Ran with the updated testcase attached (for the updated restartApplication method)

Fails once in 4-6 runs with the following:

> Timeout: bridge.set("3f54fd42-ed32-11e2-9ae1-080027fa7a0c", Components.utils.import("resource://mozmill/modules/frame.js"))
> 
> Timeout: bridge.set("638c77e4-ed32-11e2-9ae1-080027fa7a0c", Components.utils.import("resource://mozmill/modules/frame.js"))
> 
> TEST-UNEXPECTED-FAIL | Disconnect Error: Application unexpectedly closed
> RESULTS | Passed: 6
> RESULTS | Failed: 2
> RESULTS | Skipped: 0
> Traceback (most recent call last):
>   File "/home/andrei/work/mozmill/src/mozmill/mozmill/__init__.py", line 778, in run
>     mozmill.run(tests, self.options.restart)
>   File "/home/andrei/work/mozmill/src/mozmill/mozmill/__init__.py", line 424, in run
>     self.stop_runner()
>   File "/home/andrei/work/mozmill/src/mozmill/mozmill/__init__.py", line 516, in stop_runner
>     raise Exception('client process shutdown unsuccessful')
> Exception: client process shutdown unsuccessful

Comment 6

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Comment 2 still stands. I need a full log with --debug jsbridge output to continue here. I did a couple of testruns but it never failed for me.

Comment 7

[Andreea Matei [:AndreeaMatei]]

I don't see this anymore with the latest changes in Mozmill and the testcase. Tried on 2 Linux machines, 12.04, 32 and 64 bit where I reproduced often before.
I even finished a update testrun and a functional one passed the restart tests already.

Comment 8

[Henrik Skupin [:whimboo][⌚️UTC+1]]

Thanks Andreea. So I will close this bug as WFM. Andrei, feel free to reopen the bug if you still encounter this issue. Make sure to deliver the requested information at the same time.

Comment 9

[Andrei Eftimie]

Attachment: log.txt

Here's a --debug log as requested.
I'm attaching this for reference purposes.

I see this issue fixed after bug 895657
I can reproduce it prior to that often.
No single occurrence after.
Marking fixed