If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Mark gfx/layers as FAIL_ON_WARNINGS

RESOLVED FIXED in mozilla29

Status

()

Core
Graphics
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: dholbert, Assigned: dholbert)

Tracking

Trunk
mozilla29
Points:
---
Dependency tree / graph
Bug Flags:
in-testsuite -

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [qa-])

Attachments

(1 attachment)

(Assignee)

Description

4 years ago
gfx/layers is nearly warning-free.

Filing this bug on marking it as such, once we fix the last few warnings there.
(Assignee)

Comment 1

4 years ago
Created attachment 8357391 [details] [diff] [review]
fix
Attachment #8357391 - Flags: review?(nical.bugzilla)
(Assignee)

Comment 2

4 years ago
Try run, layering on top of build-warning-fixes for bug 957499 and bug 957783:
 https://tbpl.mozilla.org/?tree=Try&rev=714be3eb7ea6
(Assignee)

Updated

4 years ago
Depends on: 957858
(Assignee)

Updated

4 years ago
Depends on: 957859
(Assignee)

Updated

4 years ago
Depends on: 957884
(Assignee)

Updated

4 years ago
Depends on: 957904
(Assignee)

Comment 3

4 years ago
New Try run with fixes for (windows-only) build warnings bug 957858, bug 957859, bug 957884, & bug 957904:
 https://tbpl.mozilla.org/?tree=Try&rev=3195a0616cee
Comment on attachment 8357391 [details] [diff] [review]
fix

Review of attachment 8357391 [details] [diff] [review]:
-----------------------------------------------------------------

Sweet :)
Attachment #8357391 - Flags: review?(nical.bugzilla) → review+
(Assignee)

Comment 5

4 years ago
https://hg.mozilla.org/integration/mozilla-inbound/rev/fdc991012039
Flags: in-testsuite-
(Assignee)

Updated

4 years ago
No longer blocks: 957499, 957783
Depends on: 957499, 957783
https://hg.mozilla.org/mozilla-central/rev/fdc991012039
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla29

Updated

4 years ago
Whiteboard: [qa-]
You need to log in before you can comment on or make changes to this bug.