Closed Bug 1523684 Opened 7 years ago Closed 7 years ago

L10n jobs are missing the setup stub - nightlies end up in exception

Categories

(Release Engineering :: Release Automation, defect)

defect
Not set
normal

Tracking

(firefox67 fixed)

RESOLVED FIXED
Tracking Status
firefox67 --- fixed

People

(Reporter: CosminS, Unassigned)

References

Details

Attachments

(2 files)

My current theory is Bug 1522354 - nalexander asked me to n-i him to get it in a queue -- I have a try push of a backout to test the theory: https://treeherder.mozilla.org/#/jobs?repo=try&revision=58aa8a88b7ab388bab1b1c59a0ca1c1e81cb3416

Flags: needinfo?(nalexander)

(In reply to Justin Wood (:Callek) from comment #1)

My current theory is Bug 1522354 - nalexander asked me to n-i him to get it in a queue -- I have a try push of a backout to test the theory: https://treeherder.mozilla.org/#/jobs?repo=try&revision=58aa8a88b7ab388bab1b1c59a0ca1c1e81cb3416

I don't understand why this line is present, but it smells bad:

if test "$OS_ARCH" = "WINNT"; then
  if ! test "$HAVE_64BIT_BUILD"; then
    if test "$MOZ_UPDATE_CHANNEL" = "nightly" -o \
            "$MOZ_UPDATE_CHANNEL" = "nightly-try" -o \
            "$MOZ_UPDATE_CHANNEL" = "aurora" -o \
            "$MOZ_UPDATE_CHANNEL" = "beta" -o \
            "$MOZ_UPDATE_CHANNEL" = "release"; then
      if ! test "$MOZ_DEBUG"; then
        if ! test "$USE_STUB_INSTALLER"; then
          # Expect USE_STUB_INSTALLER from taskcluster for downstream task consistency
          echo "ERROR: STUB installer expected to be enabled but"
          echo "ERROR: USE_STUB_INSTALLER is not specified in the environment"
          exit 1
        fi
        MOZ_STUB_INSTALLER=1
      fi
    fi
  fi
fi

It's ancient -- one wonders what's actually supposed to happen here now? Callek, can you try dropping it?

Flags: needinfo?(nalexander) → needinfo?(bugspam.Callek)

In Bug 1522354, the default for --host was changed to detect running on a 64bit host.
Since --target defaults to --host, this changed the default for --target
as well. This didn't affect builds, as they explictly set the --target in
build/win32/mozconfig.vs2017. Set it explicitly in L10n builds as well.

Pushed by mozilla@hocat.ca: https://hg.mozilla.org/mozilla-central/rev/58b77413fd91 Set `--target` to be a 32 bit target for L10n builds on win32; r=nalexander,Callek a=tomprince
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED

This was 1522354 for sure, my try push proved that -- Thanks Tom for writing the patch.

I'm leaving my n-i open so I can fix the devedition mozconfig tomorrow though (otherwise we'll hit this on next staging build/uplift)

Depends on: 1522354

In Bug 1522354, the default for --host was changed to detect running on a 64bit host. Since --target
defaults to --host, this changed the default for --target as well. This didn't affect builds, as they
explictly set the --target in build/win32/mozconfig.vs2017. Set it explicitly in L10n builds as well.

This patch also fixes devedition

Flags: needinfo?(bugspam.Callek)

Reopen for devedition

Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Pushed by jwood@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0d7772590ee4 Set `--target` to be a 32 bit target for L10n builds on win32; r=nalexander
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → FIXED
Component: Release Automation: L10N → Release Automation
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: