Closed Bug 936207 Opened 8 years ago Closed 8 years ago

browser-chrome chunks are failing to start on cedar

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jgriffin, Unassigned)

References

Details

Attachments

(1 file)

The browser-chrome chunks that were just enabled on cedar are failing to start with the error:

Required config file not set! (use --config-file option)

https://tbpl.mozilla.org/php/getParsedLog.php?id=30290279&tree=Cedar&full=1

I made a quick look at buildbot-configs and couldn't spot the reason for this.
Ah, this is only on Linux x64 ASAN, regular 32/64 looks ok.
(In reply to Jonathan Griffin (:jgriffin) from comment #0)
> The browser-chrome chunks that were just enabled on cedar are failing to
> start with the error:
> 
> Required config file not set! (use --config-file option)
> 
> https://tbpl.mozilla.org/php/getParsedLog.php?id=30290279&tree=Cedar&full=1
> 
> I made a quick look at buildbot-configs and couldn't spot the reason for
> this.

(In reply to Jonathan Griffin (:jgriffin) from comment #1)
> Ah, this is only on Linux x64 ASAN, regular 32/64 looks ok.

Found in triage - anything to do here, or is this expected and should be closed? Put another way, do you have what you need for fixing the chunked-up mochitest-browser-chrome in bug#819963 ?
Blocks: 819963
Flags: needinfo?(jgriffin)
This needs to be fixed and is not expected, but it doesn't completely block bug 819963; I can work on builds other than linux x64 ASAN for the time being.
Flags: needinfo?(jgriffin)
Attachment #829296 - Flags: review?(rail) → review+
Attachment #829296 - Flags: checked-in+
in production
This has been fixed.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.