Closed Bug 2065815 Opened 20 days ago Closed 17 days ago

155.0b3: toolkit/components/remote/nsXRemoteServer.cpp did not catch up with Success -> X11Success redefinition

Categories

(Toolkit :: Startup and Profile System, defect)

Firefox 155
defect

Tracking

()

RESOLVED FIXED
156 Branch
Tracking Status
firefox-esr140 --- unaffected
firefox-esr153 --- unaffected
firefox154 --- wontfix
firefox155 --- fixed
firefox156 --- fixed

People

(Reporter: balducci, Assigned: csmantle)

References

(Regression)

Details

(Keywords: regression)

Attachments

(2 files)

During mach build I got:

59:09.68 E /home/balducci/tmp/install-us-d/firefox-155.0b3/firefox-155.0b3/toolkit/components/remote/nsXRemoteServer.cpp:114:19: error: use of undeclared identifier 'Success'
59:09.68 E   114 |     if (result != Success || bytes_after != 0) {
59:09.68 E       |                   ^~~~~~~
59:10.11 E 1 error generated.

Reason is:

Commit 27def1ef41e52d649470661dd2e1f35631a2c53e redefined Success to X11Success in gfx/src/X11UndefineNone.h.
However, toolkit/components/remote/nsXRemoteServer.cpp did not catch up with the change and still uses Success

Severity: -- → S4
Component: General → Startup and Profile System
Keywords: regression
Product: Firefox → Toolkit
Regressed by: 2065007

Hmm, since Bug 2065007 is a macro renaming task, I was really worried about anything leaking past. This seems to be such a case. Unfortunately, even Try auto pushes didn't catch it.

Besides fixing this, I'd be happy to know what we could do to further ensure nothing more gets left behind.

The build failure here is for a non-default build config (--disable-dbus) so really the only way to catch it would be to add a build check with this config. It's not completely clear to me how important this is though.

Assignee: nobody → webmaster
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Attachment #9630448 - Attachment description: Bug 2065815 - Rename usage of macro Success to X11Success. r=mossop! → Bug 2065815 - Rename usage of macro Success to X11Success in nsXRemoteServer.cpp. r=mossop!

Set release status flags based on info from the regressing bug 2065007

Status: ASSIGNED → RESOLVED
Closed: 17 days ago
Resolution: --- → FIXED
Target Milestone: --- → 156 Branch

The patch landed in nightly and beta is affected.
:csmantle, is this bug important enough to require an uplift?

For more information, please visit BugBot documentation.

Flags: needinfo?(webmaster)

I'm not really sure if this is significant enough for an uplift. Dave and Ryan, what do you think?

Flags: needinfo?(webmaster)
Flags: needinfo?(ryanvm)
Flags: needinfo?(dtownsend)

(In reply to Rong Bao [:csmantle] from comment #8)

I'm not really sure if this is significant enough for an uplift. Dave and Ryan, what do you think?

It only really impacts downstream linux distros who might build with dbus disabled, I don't know if anyone does that. That said that also makes is zero risk to uplift it.

Flags: needinfo?(dtownsend)

What Mossop said. I'd be open to taking it as a ride-along if I'm uplifting other fixes anyway but wouldn't go out of my way to take it.

Flags: needinfo?(ryanvm)

Thanks. I'll submit an uplift request, but please feel free to review it at your convenience and accept or reject it at your discretion.

firefox-beta Uplift Approval Request

  • User impact if declined/Reason for urgency: Downstream distros with D-Bus disabled would fail to build; However, the existence of such distros is uncertain.
  • Code covered by automated testing?: no
  • Fix verified in Nightly?: yes
  • Needs manual QE testing?: no
  • Steps to reproduce for manual QE testing: N/A.
  • Risk associated with taking this patch: low
  • Explanation of risk level: This is a change in non-default config, and will be caught early in compilation if anything goes wrong.
  • String changes made/needed?: None.
  • Is Android affected?: no
Attachment #9631075 - Flags: approval-mozilla-beta?
Attachment #9631075 - Flags: approval-mozilla-beta? → approval-mozilla-beta+
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: