Closed
Bug 1179369
Opened 9 years ago
Closed 9 years ago
Using a tiny build, validate the correct behavior when FHR is turned off
Categories
(Cloud Services Graveyard :: Metrics: Pipeline, defect, P2)
Cloud Services Graveyard
Metrics: Pipeline
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: thuelbert, Assigned: thuelbert)
Details
(Whiteboard: [unifiedTelemetry])
Want to be sure before this hits the beta channel, hence the tiny build. As per BDS.
Assignee | ||
Comment 1•9 years ago
|
||
Thomas investigate
Assignee: nobody → thuelbert
Whiteboard: [b5] [unifiedTelemetry]
Assignee | ||
Updated•9 years ago
|
Flags: needinfo?(thuelbert)
Priority: -- → P2
Assignee | ||
Updated•9 years ago
|
Flags: needinfo?(thuelbert)
Whiteboard: [b5] [unifiedTelemetry] → [40b7] [unifiedTelemetry]
Assignee | ||
Updated•9 years ago
|
Iteration: --- → 42.3 - Aug 10
Whiteboard: [40b7] [unifiedTelemetry] → [unifiedTelemetry]
Assignee | ||
Comment 2•9 years ago
|
||
closing
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
Updated•6 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•