Closed Bug 1613998 Opened 8 months ago Closed 2 months ago

'SourceRepository' is missing from application.ini on fuzzing builds

Categories

(Firefox Build System :: General, defect, P3)

defect

Tracking

(firefox80 fixed)

RESOLVED FIXED
mozilla80
Tracking Status
firefox80 --- fixed

People

(Reporter: tsmith, Assigned: tsmith)

Details

(Keywords: in-triage)

Attachments

(1 file)

The SourceRepository entry in the App section of application.ini is used by Pernosco to help retrieve source information.

This needs to be fixed to allow us to use fuzzing debug builds with Pernosco.

Keywords: in-triage
Priority: -- → P3

That entry is only included when MOZ_INCLUDE_SOURCE_INFO is set, which is automatically set by other builds because they define MOZILLA_OFFICIAL=1:

https://searchfox.org/mozilla-central/rev/1db5ef59eba65d32d6a29a494e87b6078453e559/browser/config/mozconfigs/linux64/common-opt#14
https://searchfox.org/mozilla-central/rev/1db5ef59eba65d32d6a29a494e87b6078453e559/old-configure.in#2943
https://searchfox.org/mozilla-central/rev/1db5ef59eba65d32d6a29a494e87b6078453e559/build/variables.py#96

So, we could set MOZILLA_OFFICIAL=1 in the relevant mozconfigs that you're interested in to get the SourceRepository info. I'm not really sure if that will have other side-effects though, so we could export MOZ_INCLUDE_SOURCE_INFO=1 in the mozconfigs instead.

Alternatively, it may be worth exploring setting MOZ_INCLUDE_SOURCE_INFO=1 in all automation builds. I don't know of a use-case for skipping the repo info in automation, but https://bugzilla.mozilla.org/show_bug.cgi?id=1057600#c6 suggests it can be annoying for local users of git or tarballs (which could be fixed by having different query methods, IMO).

Assignee: nobody → twsmith
Status: NEW → ASSIGNED
Pushed by abutkovits@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4c10445d2e2c
Use MOZ_INCLUDE_SOURCE_INFO=1 in Linux ASan debug build. r=froydnj
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla80
You need to log in before you can comment on or make changes to this bug.