1387586 - AWFY - home page no longer shows chrome results

Status: RESOLVED FIXED

(Testing Graveyard :: AWFY, defect)

Description

[Bob Clary [:bc] (inactive)]

1. https://arewefastyet.com/

2. Unselect everything but Chrome tests and see that the last results reported were tested around July 15.

Either these tests are not running or are not being reported or are not being reported on the home page.

* Compare OS
  https://arewefastyet.com/#machine=31

kraken 1.1 Chrome (Windows 10, 64bit) stopped running around July 12. OSX is currently running however.

* Mac OSX 10.10 32bit Mac Pro shell
  https://arewefastyet.com/#machine=28

Chrome v8 stopped around July 15

Chrome Turbofan, ignition; Turbofan only, Ignition have been stopped for some time.

* Mac OSX 10.10 64bit Mac Pro shell
  https://arewefastyet.com/#machine=29

Chrome v8 stopped around July 15

Chrome Turbofan, ignition; Turbofan only, Ignition have been stopped for some time.

* Quantum Reference (Windows, browser, x64)
  https://arewefastyet.com/#machine=36

Chrome v8 is currently running.
Chrome (Windows 10, 64bit) is not running since July 3.

* Quantum Reference (Windows, browser, x86)
  https://arewefastyet.com/#machine=37

Chrome v8 is running but only once per day.

* Win 8 32bit browser
  https://arewefastyet.com/#machine=17

Chrome v8 is currently running.

* Win 8 64bit browser
  https://arewefastyet.com/#machine=35

Chrome v8 is running.

Comment 1

[Benjamin Bouvier [:bbouvier] (inactive)]

If you zoom in on the charts, you can see that Chrome stopped around July 30th.

The logs show the following error:

Traceback (most recent call last):
  File "/awfy-new/repos/v8-64/v8/build/mac/find_sdk.py", line 89, in <module>
    print main()
  File "/awfy-new/repos/v8-64/v8/build/mac/find_sdk.py", line 62, in main
    raise Exception('No %s+ SDK found' % min_sdk_version)
Exception: No 10.12+ SDK found

From first investigation, looking at this script, it seems that the machine only has MacOSX10.11.sdk, which is less than 10.12 as requested. Upgrading Xcode and open it to accept its license term should do the trick.

Comment 2

[Bob Clary [:bc] (inactive)]

The appleid and credentials we have do not work with this machine and we are unable to update it from the app store.

Comment 3

[Bob Clary [:bc] (inactive)]

Updating OSX and XCode now.

Comment 4

[Bob Clary [:bc] (inactive)]

The machine has been updated to macOS 10.12.6 with Xcode 8.3.3. Macports has been migrated and the task restarted. The first job run after the restart is: <https://arewefastyet.com/task_info.php?id=100871>. This is still running so the output isn't available on the web site yet, but I see python exceptions and can't guarantee we are getting good results.

Comment 5

[Bob Clary [:bc] (inactive)]

This doesn't appear to be running correctly. There appear to be failures building d8, failure processing the output and failures running the proxy server though no missing SDK. None of these errors are new as they also appeared before the macOS/Xcode upgrade. I'll keep investigating but it would be helpful if someone who knew this system could take a look.

Comment 6

[Bob Clary [:bc] (inactive)]

The d8 build does fail with:

FAILED: mksnapshot 
TOOL_VERSION=1480419879 ../../build/toolchain/mac/linker_driver.py ../../third_party/llvm-build/Release+Asserts/bin/clang++  -stdlib=libc++ -arch i386 -Werror -isysroot ../../../../../../../../Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk -mmacosx-version-min=10.9.0 -Wl,-ObjC -Wl,-pie -Wl,-dead_strip -o "./mksnapshot" -Wl,-filelist,"./mksnapshot.rsp"  
ld: unexpected token: !tapi-tbd-v2 file '../../../../../../../../Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk/usr/lib/libSystem.tbd' for architecture i386
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Traceback (most recent call last):
  File "../../build/toolchain/mac/linker_driver.py", line 229, in <module>
    Main(sys.argv)
  File "../../build/toolchain/mac/linker_driver.py", line 79, in Main
    subprocess.check_call(compiler_driver_args)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/subprocess.py", line 540, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['../../third_party/llvm-build/Release+Asserts/bin/clang++', '-stdlib=libc++', '-arch', 'i386', '-Werror', '-isysroot', '../../../../../../../../Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.12.sdk', '-mmacosx-version-min=10.9.0', '-Wl,-ObjC', '-Wl,-pie', '-Wl,-dead_strip', '-o', './mksnapshot', '-Wl,-filelist,./mksnapshot.rsp']' returned non-zero exit status 1
ninja: build stopped: subcommand failed.

We don't check that the build succeed before attempting to run execute.py, but that is an issue for another day.

We hard code the version of clang we use to 3.8.0 which was released in 2016-03-08 which might be the problem. We have much newer versions we could use: http://releases.llvm.org/.

Comment 7

[Bob Clary [:bc] (inactive)]

From what I can tell, we are using the clang shipped as part of v8/third_party/llvm-build/Release+Asserts/ and this is not affected by the environment variables CC, CXX or LINK.

Comment 8

[Benjamin Bouvier [:bbouvier] (inactive)]

Looking into it.

Comment 9

[Benjamin Bouvier [:bbouvier] (inactive)]

I found https://bugs.chromium.org/p/v8/issues/detail?id=5994 where our very own bzbarsky asks for the same issue: I did what's recommended in the comment 9, i.e. sudo port install ld64 +ld64_xcode. This fixes the v8 build. I've restarted the task to see if it completes correctly.

Comment 10

[Bob Clary [:bc] (inactive)]

Ben, should we do the same updates/upgrades on awfy-cmp-osx?

Comment 11

[Bob Clary [:bc] (inactive)]

Ben already started by upgrading to 10.12.6. I completed the upgrades by updating the remaining packages, removing and install Xcode again and migrating mac ports to the new Xcode. I also did what Ben did in comment 9 and restarted the task. Marking this fixed as it ever will be.