Closed Bug 932153 Opened 12 years ago Closed 12 years ago

A11Y_LOG will cause the build to burn when Gecko 27 moves from mozilla-aurora to mozilla-beta

Categories

(Core :: Disability Access APIs, defect)

defect
Not set
critical

Tracking

()

VERIFIED FIXED
mozilla28
Tracking Status
firefox25 --- unaffected
firefox26 --- unaffected
firefox27 + verified
firefox28 --- verified

People

(Reporter: philor, Assigned: glandium)

References

Details

Attachments

(1 file)

This is rather surprising, but https://tbpl.mozilla.org/?tree=Try&rev=f8ad0256dcf3 is the current tip of aurora, just after Gecko 27 merged to it, pushed to try as though it were beta, with among other things the update channel set to 'beta', and according to the burning builds that causes us to do what looks like correctly seeing that it's beta in accessible/src/shared.mozbuild and not building Logging.cpp as a result, but not seeing it's beta in accessible/src/Makefile.in and thus defining A11Y_LOG and expecting that Logging.cpp will have been compiled. This only failing now (Gecko 26, the thing that's actually on beta now, is fine) seems rather weird, since neither the makefile nor the moz.build file appear to have been touched in a way likely to change that.
Oh my... Makefiles under accessible/src/* are relying on A11Y_LOG being exported from accessible/src/Makefile.in. Which is not the case when doing derecursed build nowadays. It's also not the case when doing make -C objdir/accessible/src/foo, so it was wrong to do that in the first place. Backing out the removal of 'test -n "$DEVELOPER_OPTIONS"' from bug 926126 could be something we can land on aurora safely (no need to backout the MOZ_PSEUDO_DERECURSE value change). Alternatively, A11Y_LOG could be moved to accessible/src/defs.mk, in which case it will be inherited by all submakefiles.
Blocks: 926126
Assignee: nobody → mh+mozilla
Status: NEW → ASSIGNED
Comment on attachment 823761 [details] [diff] [review] Move A11Y_LOG to accessible/src/defs.mk Philor, can you test this? It should be good enough to land on m-c and aurora.
Attachment #823761 - Flags: feedback?(philringnalda)
Comment on attachment 823761 [details] [diff] [review] Move A11Y_LOG to accessible/src/defs.mk Looks like this worked.
Attachment #823761 - Flags: feedback?(philringnalda) → review?(gps)
(This is keeping aurora closed currently)
Comment on attachment 823761 [details] [diff] [review] Move A11Y_LOG to accessible/src/defs.mk This looks good to me. Reviewing for gps since it's causing sheriff pain.
Attachment #823761 - Flags: review?(gps) → review+
Sorry for not seeing this. I woke up with 14 new reviews in my queue. I'm about half in and I still have unread bugmail. IRC pings would have helped. Next time.
RyanVM: (autoresponse) content-free ping detected. Please consider providing some additional context so I can address your questions more efficiently.
(In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #10) > RyanVM: (autoresponse) content-free ping detected. Please consider providing > some additional context so I can address your questions more efficiently. I don't see a ping earlier than 13:18 my time. Whatevs. We got review.
An hour in and the nightlies are still going. I think we're in good shape here :)
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla28
(In reply to Ryan VanderMeulen [:RyanVM UTC-5] from comment #13) > An hour in and the nightlies are still going. I think we're in good shape > here :) Does this mean, once 27 goes to Beta, those builds won't go up in flames?
It does, I've pushed aurora-as-beta and trunk-as-aurora-with-aurora's-channel to try a couple of times since this landed.
Status: RESOLVED → VERIFIED
Excellent, thank you, philor!
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: