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

Issue 863310 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 828031
Owner: ----
Closed: Jul 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 1
Type: ----



Sign in to add a comment

browser_tests on Mac10.11: Crashing in Crashpad.

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Jul 13

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of mkwst@chromium.org

browser_tests failing on chromium.mac/Mac10.11 Tests

Builders failed on: 
- Mac10.11 Tests: 
  https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/Mac10.11%20Tests

Many browser tests failing with the same stack:

[ RUN      ] CrSettingsSearchTest.All
[0712/182722.113016:ERROR:mach_extensions.cc(68)] bootstrap_check_in org.chromium.crashpad.child_port_handshake.13615.151238.OFTMKRAANZZDAJCX: unknown error code (141)
[0712/182722.113178:FATAL:child_port_handshake.cc(111)] Check failed: server_port.is_valid().
0   crashpad_handler                    0x000000010d23e71c base::debug::StackTrace::StackTrace(unsigned long) + 28
1   crashpad_handler                    0x000000010d22ba81 logging::LogMessage::~LogMessage() + 225
2   crashpad_handler                    0x000000010d2483d4 crashpad::ChildPortHandshake::RunServerForFD(base::ScopedGeneric, crashpad::ChildPortHandshake::PortRightType) + 516
3   crashpad_handler                    0x000000010d21a946 crashpad::HandlerMain(int, char**, std::__1::vector >, std::__1::allocator > > > const*) + 4790
4   libdyld.dylib                       0x00007fff95b035ad start + 1
5   ???                                 0x0000000000000008 0x0 + 8
[0712/182722.114028:ERROR:file_io.cc(89)] ReadExactly: expected 4, observed 0
[0712/182722.114846:ERROR:mach_extensions.cc(68)] bootstrap_check_in org.chromium.crashpad.child_port_handshake.13613.151199.XPEJOHATOMXHSADU: unknown error code (141)
[0712/182722.114956:FATAL:child_port_handshake.cc(111)] Check failed: server_port.is_valid().
0   crashpad_handler                    0x000000010faec71c base::debug::StackTrace::StackTrace(unsigned long) + 28
1   crashpad_handler                    0x000000010fad9a81 logging::LogMessage::~LogMessage() + 225
2   crashpad_handler                    0x000000010faf63d4 crashpad::ChildPortHandshake::RunServerForFD(base::ScopedGeneric, crashpad::ChildPortHandshake::PortRightType) + 516
3   crashpad_handler                    0x000000010fac8946 crashpad::HandlerMain(int, char**, std::__1::vector >, std::__1::allocator > > > const*) + 4790
4   libdyld.dylib                       0x00007fff95b035ad start + 1
5   ???                                 0x0000000000000009 0x0 + 9
 
Components: Infra
Labels: Infra-Troopers OS-Mac
Summary: browser_tests on Mac10.11: Crashing in Crashpad. (was: browser_tests failing on chromium.mac/Mac10.11 Tests)
Skimming the code, it looks like Crashpad is having a hard time checking in with the bootstrap server, and is failing the subsequent CHECK.

Most recently, all the failures seemed to happen in one swarming task running on vm147-m1: https://chromium-swarm.appspot.com/task?id=3eaa0fdad5019810&refresh=10&show_raw=1

Adding `Infra-Troopers`, as this could possible be a bot issue?
The next run also failed only on one swarming task, but running on a different bot: vm143-m1 (https://chromium-swarm.appspot.com/task?id=3eab223a38a88010&refresh=10&show_raw=1).
Mergedinto: 828031
Status: Duplicate (was: Available)
this is a persistent issue -- something in browser_tests is flakily killing the window server, dropping the bot into an unusable state for subsequent tests.

Sign in to add a comment