56.0b1 update tests fail: MAR_CHANNEL_MISMATCH_ERROR

RESOLVED FIXED

Status

Release Engineering
Release Automation: Other
RESOLVED FIXED
11 months ago
11 months ago

People

(Reporter: jlorenzo, Assigned: jlorenzo)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

MozReview Requests

Submitter Diff Changes Open Issues Last Updated
Loading...
Error loading review requests:

Attachments

(2 attachments)

Comment hidden (mozreview-request)
Attachment #8894841 - Flags: review?(mtabara) → review+
Landed on default at https://hg.mozilla.org/build/tools/rev/abe1efa0f593718b497b3aa5adefb0e031ec1964
Status: NEW → RESOLVED
Last Resolved: 11 months ago
Resolution: --- → FIXED
See Also: → bug 1388357
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Blocks: 1388357
See Also: bug 1388357
Comment hidden (mozreview-request)

Comment 4

11 months ago
mozreview-review
Comment on attachment 8895012 [details]
Bug 1388312 - fix the mar tools location in beta.

https://reviewboard.mozilla.org/r/166144/#review171340

::: lib/python/kickoff/__init__.py:180
(Diff revision 1)
> +                elif branch == "mozilla-release":
> +                    # if we don't get releasetasks in-tree by the time 56 get
> +                    # to release, we need to add here the last working release,
> +                    # either that's 55.0 or 55.0.X mar/mbsdiff build on BB mac
> +                    # native hardware - see bug 1388460 for more details
> +                    pass

I'd raise an exception here, since if we get this far without ripping this code out, we are then going to fail 56.x release :-) -- And an exception will help releaseduty easily notice whats wrong.
Attachment #8895012 - Flags: review?(bugspam.Callek) → review+
Comment on attachment 8895012 [details]
Bug 1388312 - fix the mar tools location in beta.

https://hg.mozilla.org/build/tools/rev/9657b6ff2fbe
Landed on default and pulled to bm85.
Attachment #8895012 - Flags: checked-in+

Comment 7

11 months ago
154 failures in 182 pushes (0.846 failures/push) were associated with this bug yesterday.   

Repository breakdown:
* mozilla-beta: 154

Platform breakdown:
* osx-10-10: 106
* windows8-64: 24
* windows8-32: 24

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1388312&startday=2017-08-08&endday=2017-08-08&tree=all
Patches from this bug solved the problem, last 56.0b1-build5 went out smoothly.
I think we can close this.
Status: REOPENED → RESOLVED
Last Resolved: 11 months ago11 months ago
Resolution: --- → FIXED

Comment 9

11 months ago
153 failures in 901 pushes (0.17 failures/push) were associated with this bug in the last 7 days. 

This is the #4 most frequent failure this week. 

** This failure happened more than 75 times this week! Resolving this bug is a very high priority. **

** Try to resolve this bug as soon as possible. If unresolved for 1 week, the affected test(s) may be disabled. **  

Repository breakdown:
* mozilla-beta: 153

Platform breakdown:
* osx-10-10: 106
* windows8-64: 24
* windows8-32: 23

For more details, see:
https://brasstacks.mozilla.com/orangefactor/?display=Bug&bugid=1388312&startday=2017-08-07&endday=2017-08-13&tree=all
You need to log in before you can comment on or make changes to this bug.