Closed
Bug 1148182
Opened 10 years ago
Closed 10 years ago
Re-enable testSecNotification and make the expired tests work with the new domain
Categories
(Mozilla QA Graveyard :: Mozmill Tests, defect, P1)
Mozilla QA Graveyard
Mozmill Tests
Tracking
(firefox38 fixed, firefox39 fixed, firefox-esr31 fixed)
RESOLVED
FIXED
People
(Reporter: sydpolk, Assigned: sydpolk)
References
()
Details
(Keywords: regression, Whiteboard: [mozmill-test-failure])
Attachments
(2 files)
2.08 KB,
patch
|
chmanchester
:
review+
|
Details | Diff | Splinter Review |
931 bytes,
patch
|
Details | Diff | Splinter Review |
The expired certificate domain has been updated. This BZ is to change the test domain and re-enable these tests.
The domain has change from "summitbook.mozilla.org" to "ssl-expired.mozqa.com".
+++ This bug was initially created as a clone of Bug #1146314 +++
This test failure started to happen over the weekend and totally breaks our tests across Nightly, and Aurora so far. I haven't tested with beta and release yet.
ERROR | Test Failure | {
"fail": {
"message": "The error code is a SEC Expired certificate error - 'summitbook.mozilla.org uses an invalid security certificate.\n\nThe certificate is not trusted because the issuer certificate is unknown.\nThe server might not be sending the appropriate intermediate certificates.\nAn additional root certificate may need to be imported.\nThe certificate expired on 7/8/2011 5:41 AM. The current time is 3/22/2015 6:57 AM.\n\n(Error code: sec_error_unknown_issuer)\n' should contain 'sec_error_expired_certificate'",
"fileName": "file:///c:/jenkins/workspace/mozilla-central_remote/data/mozmill-tests/firefox/tests/remote/testSecurity/testSecurityNotification.js",
"name": "testSecNotification",
"lineNumber": 70
}
Assignee | ||
Comment 1•10 years ago
|
||
Change domain. Re-enable tests.
Attachment #8584129 -
Flags: review?(cmanchester)
Assignee | ||
Updated•10 years ago
|
status-firefox38:
--- → affected
status-firefox39:
--- → affected
Comment 2•10 years ago
|
||
Comment on attachment 8584129 [details] [diff] [review]
diff.out
Review of attachment 8584129 [details] [diff] [review]:
-----------------------------------------------------------------
::: firefox/tests/remote/testSecurity/testSecurityNotification.js
@@ +45,5 @@
> expect.waitFor(function () {
> return identityBox.getNode().className === "unknownIdentity";
> }, "Identity is unknown");
>
> + // Bug 1106077 - Broken root certificate for http://summitbook.mozilla.org
Nit: the comment on this line can be removed now.
Attachment #8584129 -
Flags: review?(cmanchester) → review+
Whiteboard: [mozmill-test-failure][blocked by bug 1106077] → [mozmill-test-failure]
Assignee | ||
Comment 3•10 years ago
|
||
Assignee | ||
Comment 4•10 years ago
|
||
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → spolk
Status: NEW → ASSIGNED
Assignee | ||
Comment 5•10 years ago
|
||
I will check the mozmill run tomorrow before marking this as fixed.
Comment 6•10 years ago
|
||
Syd, FYI we usually continue to work on the original filed bug. I have CC'ed you on that one and also mentioned it on IRC. So this would have been bug 1146314.
Comment 7•10 years ago
|
||
Comment on attachment 8584129 [details] [diff] [review]
diff.out
Review of attachment 8584129 [details] [diff] [review]:
-----------------------------------------------------------------
::: firefox/tests/remote/testSecurity/testSecurityNotification.js
@@ +45,5 @@
> expect.waitFor(function () {
> return identityBox.getNode().className === "unknownIdentity";
> }, "Identity is unknown");
>
> + // Bug 1106077 - Broken root certificate for http://summitbook.mozilla.org
FYI the comment has not been removed before landing the patch. But it's not important enough for any follow-up work.
Comment 8•10 years ago
|
||
The landed changes in comment 3 and comment 4 fixed the problem for 38 and 39. So we can mark this bug as fixed.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Comment 9•10 years ago
|
||
This was not fixed for the esr31 branch and caused massive failures for the last full testrun 2 days ago. For that branch we only have to exchange the domain. That's all. So I think no review is necessary.
Comment 10•10 years ago
|
||
status-firefox-esr31:
--- → fixed
Not sure why but this is not fixed on esr31 when the tests get run via Mozmill CI:
http://hg.mozilla.org/qa/mozmill-tests/file/14e66857901d16c351e554d77adf4e76bbf25fed/firefox/tests/remote/testSecurity/testSecurityNotification.js
The domain is still the old one. While latest esr31 shows the correct domain. I will investigate soon.
Please disregard my last comment. I landed the skip on May 6th while the last esr release tests were on May 5th. So all good here.
Updated•5 years ago
|
Product: Mozilla QA → Mozilla QA Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•