New issue
Advanced search Search tips

Issue 727089 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: May 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Runhooks step failing on new Mac Tester machines

Project Member Reported by kjellander@chromium.org, May 28 2017

Issue description

As part of bug 687467, our two Mac Tester machines in chromium.webrtc and chromium.webrtc.fyi were upgraded to 10.12. This caused runhooks starting to fail, most likely because it made them start using a clean checkout that didn't previously have anything downloaded.

Example failures:
https://build.chromium.org/p/chromium.webrtc.fyi/builders/Mac%20Tester/builds/39880
https://build.chromium.org/p/chromium.webrtc/builders/Mac%20Tester/builds/68237

It's either Mercurial and/or the AppRTC build that fails:
________ running '/usr/bin/python webrtc.DEPS/build_mercurial_local.py' in '/b/c/b/Mac_Tester'
python setup.py  \
	  build_py -c -d . \
	  build_ext  -i \
	  build_hgexe  -i \
	  build_mo
running build_py
running build_ext
running build_hgexe
running build_mo
warning: hgbuildmo: could not find msgfmt executable, no translations will be built

env HGRCPATH= python hg version
Mercurial Distributed SCM (version 3.2.2)
(see http://mercurial.selenic.com for more information)

Copyright (C) 2005-2014 Matt Mackall and others
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

________ running '/usr/bin/python webrtc.DEPS/build_apprtc_collider.py' in '/b/c/b/Mac_Tester'
failed MSpanList_Insert 0x74c178 0x468e4396214 0x0
fatal error: MSpanList_Insert

Since we've recently done work in moving this to the WebRTC repo, we should replace these runhooks steps with a separate buildbot step calling the download and setup scripts in https://chromium.googlesource.com/external/webrtc/+/master/webrtc/tools/testing
(living in src/third_party/webrtc/tools/testing of a Chromium checkout).

This bug tracks that work. Mirko: let's work together on this on Monday.
CCing upcoming WebRTC-in-Chrome sheriffs.
 
Labels: -Pri-1 Pri-2
Notice this doesn't fail every time, it's just failing flakily. That also tells me it might be possible to avoid the whole build step if there's a previous build already detected. 

My suggested first thing to try is to upgrade the Go runtime version from 1.3.1 to something newer. In WebRTC we now have 1.8.1 instead. Maybe that contains a fix for this bug that hits macOS Sierra (10.12).
Status: Started (was: Assigned)
Status: Fixed (was: Started)
Yay! Go was updated to 1.8.1 for Mac in https://codereview.chromium.org/2913583002 (bugdroid doesn't work for that repo, which explains why there's no post in here) and we have several green builds in a row. I consider this fixed but Mirko will update the other platforms in a separate CL.

Sign in to add a comment