jetpack-w764 build fails tests with the error "w764 is not a valid platform."

RESOLVED FIXED

Status

Release Engineering
General
RESOLVED FIXED
7 years ago
4 years ago

People

(Reporter: myk, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

7 years ago
The jetpack-w764 build fails tests with the error "w764 is not a valid platform."

http://tinderbox.mozilla.org/showlog.cgi?log=Jetpack/1300863118.1300863159.12680.gz&fulltext=1

This looks like a bug on line 18 of run-jetpack.sh, which needs to be changed to accept w764 just as it accepts win764 as an identifier for the Windows 7 64bit platform:

http://mxr.mozilla.org/build/source/tools/buildfarm/utils/run_jetpack.sh#18

Or possibly the name of the build needs to be changed to jetpack-win764, or some other property that contains the value "w764" needs to be changed to "win764", if that's the standard designator for Windows 7 64bit builds.

Comment 1

7 years ago
Created attachment 523642 [details] [diff] [review]
Like so
Attachment #523642 - Flags: review?(lsblakk)
Created attachment 523643 [details] [diff] [review]
treat win764 like w764 for now as workaround

from irc with myk and ctalbert:

We're not sure if the real fix is to change "win764" to "w764" in the condition, or rename the builder from "w764" to "win764". However, the workaround in this patch should get things running until next week when lsblakk is back and can investigate properly.
Attachment #523643 - Flags: review?(aki)

Updated

7 years ago
Attachment #523643 - Flags: review?(aki) → review+

Updated

7 years ago
Attachment #523642 - Flags: review?(lsblakk)

Comment 3

7 years ago
Comment on attachment 523643 [details] [diff] [review]
treat win764 like w764 for now as workaround

http://hg.mozilla.org/build/tools/rev/60beab45b2b1
Attachment #523643 - Flags: checked-in+

Updated

7 years ago
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → FIXED
(Assignee)

Updated

4 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.