New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 810468 link

Starred by 1 user

Issue metadata

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

Blocked on:
issue 810524



Sign in to add a comment

Mac Experimental Retina Release bot failing since 4542

Project Member Reported by danakj@chromium.org, Feb 8 2018

Issue description

The 4541 build had an exception due to sharding resources, but 4540 was at the same angle position, so I don't think 4541 is problematic.

4542 had webgl2_conformance_tests and screenshot_sync_tests fail.
Then webgl2_conformance_tests has failed every build since.
Some other tests were flaky in the later builds as well such as tab_capture_end2end_tests, context_lost_tests, info_collection_tests and webgl_conformance_tests

The 4541-4542 angle changes were
https://chromium.googlesource.com/angle/angle/+/00155d58e8b034ecbc179186da8996451fb6de5c
  Vulkan: Implement scissor test and add a simple test for it
https://chromium.googlesource.com/angle/angle/+/b9d1daa06d3519752139d5714210bb43b3d4bec7
  Add Vulkan mock_icd to the build

These don't seem likely. So maybe a chrome-side change. There's 66 CLs in the one blame range :\

https://ci.chromium.org/buildbot/chromium.gpu.fyi/Mac%20Experimental%20Retina%20Release%20%28AMD%29/4542

https://chromium.googlesource.com/chromium/src/+/88a9ae6d5ab5d0da90cd9b82998ceee86a801b7b
  Bump Chrome-GPU experimental bots to 10.13.4

Was one of them. Nothing else is standing out for me. What do you think Ken?

 
Labels: OS-Mac
Cc: cwallez@chromium.org
Looking at the bot, it is always build210-m1 that's failing with either timeouts and weird errors in the log:

https://chromium-swarm.appspot.com/task?id=3b8fa64b799a7210&refresh=10&show_raw=1
TimeoutException: 
********************************************************************************
(/b/s/w/ir/third_party/catapult/telemetry/telemetry/internal/backends/chrome_inspector/inspector_backend.py:487 _ConvertExceptionFromInspectorWebsocket) The app is probably crashed:

Another early failure had network issues:

https://chromium-swarm.appspot.com/task?id=3b8b4d1e50223010&refresh=10&show_raw=1

I'm not sure what we should do with this machine, just restart it?
Ohh I see what you mean, with the sharding. That's an amazing observation.
Blockedon: 810524
Owner: ----
Status: Available (was: Assigned)

Comment 7 by kbr@chromium.org, Feb 8 2018

Components: Internals>GPU>Testing
Thanks for filing and triaging. Please use Internals>GPU>Testing for general bugs with the GPU bots.

Status: Fixed (was: Available)
Machine is looking better now

Sign in to add a comment