Closed Bug 1425968 Opened 7 years ago Closed 7 years ago

browser_hsts-priming_allow_active.js is going to permafail when the Gecko version number is bumped to 60

Categories

(Core :: DOM: Security, enhancement, P2)

Product:
Core
Component:
DOM: Security
Type:
enhancement

Tracking

()

Status:
VERIFIED FIXED
Milestone:
mozilla59
Tracking Flags:
Tracking Status
firefox-esr52 --- unaffected
firefox57 --- unaffected
firefox58 --- unaffected
firefox59 + verified

People

(Reporter: RyanVM, Assigned: RyanVM)

References

Details

(Whiteboard: [domsecurity-active])

[Tracking Requested - why for this release]: Permafailing tests when the Gecko version number is bumped to 60. Looks like the test depends on the MIXED_CONTENT_HSTS_PRIMING_RESULT probe, which is set to expire in Gecko 60. How should we proceed here, Kate?
Flags: needinfo?(kmckinley)
This will be removed when bug 1424917 lands.
Depends on: 1424917
Flags: needinfo?(kmckinley)
Yeah, this becomes INVALID once Bug 1424917 has landed. We just have to make sure it happens before FF60. Kate, since we are triaging bugs at the moment I am assigning this one to you in the meantime
Assignee: nobody → kmckinley
Status: NEW → ASSIGNED
Priority: -- → P2
Whiteboard: [domsecurity-active]
Would you object to disabling this test in the mean time then? It would at least get rid of the noise from my Try pushes and it doesn't sound like it's giving us much value anyway.
The early/first merge will be Jan. 11th. Tracking so we can make sure to check back in early January. Disabling the test for now sounds reasonable.
tracking-firefox59: ? → +
Kate confirmed on IRC that she's fine with me disabling the test for now, so taking.
Assignee: kmckinley → nobody
Status: ASSIGNED → NEW
Pushed by ryanvm@gmail.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/4b384e880e28 Skip HSTS browser-chrome tests because the feature is being removed and they depend on an expiring Telemetry probe. r=kmckinley
https://hg.mozilla.org/mozilla-central/rev/4b384e880e28
Status: NEW → RESOLVED
Closed: 7 years ago
status-firefox59: affected → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla59
Status: RESOLVED → VERIFIED
status-firefox59: fixed → verified
Assignee: nobody → ryanvm
You need to log in before you can comment on or make changes to this bug.