media/gfx push required a clobber

RESOLVED FIXED

Status

()

Core
Build Config
--
blocker
RESOLVED FIXED
5 years ago
4 years ago

People

(Reporter: philor, Assigned: glandium)

Tracking

(Blocks: 1 bug)

Trunk
x86_64
Linux
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
Much as I would have liked it if the last blocker about having to clobber every few pushes would have solved all our problems, it didn't.

https://hg.mozilla.org/integration/mozilla-inbound/rev/f26d6c5a2d93 failed in opt and debug Linux64 mochitest-1 and reftests in https://tbpl.mozilla.org/?tree=Mozilla-Inbound&rev=f26d6c5a2d93 and debug Linux64 in https://tbpl.mozilla.org/?tree=Mozilla-Inbound&rev=b8893f7f80c5 before starting to pass. I retriggered the builds on its landing push after clobbering, but I already know what the results will be, the clobber will have "fixed" it.
(Reporter)

Updated

5 years ago
Blocks: 767480
Blocks: 781529
This should be fixed by the backout of bug 781529.

When building nsCanvasRenderingContext2D.cpp with -MMD, the .deps/nsCanvasRenderingContext2D.o.pp file doesn't contain a reference to ImageContainer.h. With -MD it does. AFAICT, ImageContainer.h is never declared as a system header, so this likely is a GCC bug.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
Assignee: nobody → mh+mozilla
https://hg.mozilla.org/mozilla-central/rev/60a42d321090

Updated

4 years ago
Blocks: 941904
You need to log in before you can comment on or make changes to this bug.