Closed
Bug 1888394
Opened 6 months ago
Closed 6 months ago
Update tests within accessible/ to work with https-first enabled
Categories
(Core :: DOM: Security, task, P3)
Core
DOM: Security
Tracking
()
RESOLVED
FIXED
127 Branch
Tracking | Status | |
---|---|---|
firefox127 | --- | fixed |
People
(Reporter: ckerschb, Assigned: ckerschb)
References
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file, 1 obsolete file)
Eventually we want to enable https-first
in Nightly. Currently we have a variety of tests failing on TRY. We update one folder of test at a time to eventually receive a full green TRY run.
Assignee | ||
Updated•6 months ago
|
Assignee: nobody → ckerschb
Blocks: 1719271
Status: NEW → ASSIGNED
Priority: -- → P3
Whiteboard: [domsecurity-active]
Assignee | ||
Comment 1•6 months ago
|
||
Pushed by mozilla@christophkerschbaumer.com:
https://hg.mozilla.org/integration/autoland/rev/1e349279000c
Update tests within accessible/ to work with https-first enabled, r=Jamie
Comment 3•6 months ago
|
||
Backed out for causing mochitests failures.
- Backout link
- Push with failures
- Failure Log
- Failure line: The 'prefs' key must be set in the DEFAULT section of a manifest. Fix the following manifests: accessible/tests/browser/e10s/browser.toml
Flags: needinfo?(ckerschb)
Assignee | ||
Comment 5•6 months ago
|
||
Updated•6 months ago
|
Attachment #9393754 -
Attachment is obsolete: true
Pushed by mozilla@christophkerschbaumer.com:
https://hg.mozilla.org/integration/autoland/rev/6600b3b35d95
Update tests within accessible/ to work with https-first enabled, r=Jamie
Comment 7•6 months ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 6 months ago
status-firefox127:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 127 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•