Closed Bug 1198611 Opened 10 years ago Closed 9 years ago

[10.2] TEST-UNEXPECTED-ERROR | test_ssl_status_after_restart.py TestSSLStatusAfterRestart.test_ssl_status_after_restart | TimeoutException: TimeoutException: Timed out after 5.0 seconds

Categories

(Testing :: Firefox UI Tests, defect)

43 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1272591

People

(Reporter: whimboo, Assigned: whimboo)

References

Details

(Keywords: intermittent-failure)

The timeout happens because the identitypopup does not open: Traceback (most recent call last): File "/Users/mozauto/jenkins/workspace/mozilla-central_functional/venv/lib/python2.7/site-packages/marionette/marionette_test.py", line 296, in run testMethod() File "/Users/mozauto/jenkins/workspace/mozilla-central_functional/venv/lib/python2.7/site-packages/firefox_ui_harness/decorators.py", line 15, in wrapper return target(self, *args, **kwargs) File "/Users/mozauto/jenkins/workspace/mozilla-central_functional/venv/lib/python2.7/site-packages/firefox_ui_harness/decorators.py", line 23, in wrapper return target(self, *args, **kwargs) File "/Users/mozauto/jenkins/workspace/mozilla-central_functional/venv/lib/python2.7/site-packages/firefox_ui_tests/functional/security/test_ssl_status_after_restart.py", line 66, in test_ssl_status_after_restart self.verify_certificate_status(item) File "/Users/mozauto/jenkins/workspace/mozilla-central_functional/venv/lib/python2.7/site-packages/firefox_ui_tests/functional/security/test_ssl_status_after_restart.py", line 79, in verify_certificate_status Wait(self.marionette).until(lambda _: self.identity_popup.is_open) File "/Users/mozauto/jenkins/workspace/mozilla-central_functional/venv/lib/python2.7/site-packages/marionette_driver/wait.py", line 143, in until cause=last_exc) TimeoutException: TimeoutException: Timed out after 5.1 seconds
So far only the machine mm-osx-1010-2 in the production system seems to be affected here. I will continue to watch and check its status now.
OS: All → Mac OS X
The problem here was that a Java update prompt was open and most likely killed out focus. Hi Neil, can you imagine what we could do to run our tests more stable in terms of those OS annoyances? Why does Firefox not correctly handle popups like the identity popup, if other applications seem to have a window stick to the top?
Flags: needinfo?(enndeakin)
If another application opened a window while the test was running, there isn't much that can be done. We should disable any auto-update dialogs though in general on the test machines. It might be worth building something into the test infrastructure that can detect these kinds of cases when a failure occurs though. For instance, when a test fails, it could perform some checks to ensure that firefox is still focused, and/or log what it instead.
Flags: needinfo?(enndeakin)
No, the Java upgrade dialog popped up on that OS X machine while no test was running. So starting tests afterward should have brought Firefox into focus by default. But even then we seem to fail to open the popup correctly. If it would help I could do some checks in how to reproduce it.
Do you have a screenshot of this? Is the update prompt some special type of popup/dialog that behaves differently?
We also had this failure for 40.0 release candidate builds today. It seems that it's really only this box which has issues with the focus. Some locales passed and others not. Also a retrigger of the german locale did not succeed. I was watching the run and the check for the popup was successful for the first two tabs, but for the third it doesn't open. Given that the Java update notification is not open anymore, it might have been a red herring, and it's really something else. Sorry Neil.
Thinking more about that issue it reminds me on bug 1087261. That's exactly the same machine just before it got re-imaged with OS X 10.10. And we always had issues with focus on it, which we never figured out. Looks like this problem is back now since a couple of days after it was working for a couple of months. :(
Depends on: 1201715
So the constant failures on mm-osx-10.10-2 are a side-effect and we will keep this machine offline for now. But as you can see by the previous comments the issue is also visible intermittently on other platforms.
OS: Mac OS X → All
Summary: "TimeoutException: Timed out after 5 seconds" in test_ssl_status_after_restart.py → TEST-UNEXPECTED-ERROR | test_ssl_status_after_restart.py TestSSLStatusAfterRestart.test_ssl_status_after_restart | TimeoutException: TimeoutException: Timed out after 5.0 seconds
I have seen that a Java update prompt was open on mm-osx-1010-2. This could have caused problems in the past too. I will re-enable this node and watch it the next days for its stability.
Product: Mozilla QA → Testing
We haven't seen this failure in the last 2 months. So I think we can blame this single machine for it and mark the bug as fixed.
Assignee: nobody → hskupin
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Whiteboard: [failure] → [failure][mm-osx-1010-2 only]
What? It didn't fail for 2 months and then when I close the bug as fixed it starts to happen again? This machine fools us... https://treeherder.mozilla.org/logviewer.html#?job_id=3032736&repo=mozilla-central
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Nothing specific was visible for this node. I rebooted it now. Lets see how long it will stay quiet.
Summary: TEST-UNEXPECTED-ERROR | test_ssl_status_after_restart.py TestSSLStatusAfterRestart.test_ssl_status_after_restart | TimeoutException: TimeoutException: Timed out after 5.0 seconds → [10.2] TEST-UNEXPECTED-ERROR | test_ssl_status_after_restart.py TestSSLStatusAfterRestart.test_ssl_status_after_restart | TimeoutException: TimeoutException: Timed out after 5.0 seconds
Latest beta showed the failure for multiple platforms.
Whiteboard: [failure][mm-osx-1010-2 only]
This didn't happen anymore for a couple of months. Closing as WFM.
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → WORKSFORME
Actually the signature has been changed. So this is bug 1272591.
Resolution: WORKSFORME → DUPLICATE
You need to log in before you can comment on or make changes to this bug.