I went through all the tests on https://build.chromium.org/p/chromium.mac/builders/Mac10.11%20Tests/builds/2180. I've filed bugs for all the failures, and marked them as blockers of this bug.

Didn’t run:
telemetry_gpu_unittests
telemetry_perf_unittests
telemetry_unittests
nacl_integration 

Passed tests:
accessibility_unittests
base_unittests
cacheinvalidation_unittests
capture_unittests
cast_unittests
cc_unittests
chrome_app_unittests
chromedriver_unittests
components_browsertests
components_unittests
content_unittests
crypto_unittests
device_unittests 
display_unittests
extensions_unittests
gcm_unit_tests
gn_unittests 
google_apis_unittests
gpu_ipc_service_unittests
ipc_tests
jingle_unittests
media_blink_unittests
media_unittests
message_center_unittests
midi_unittests
mojo_common_unittests
mojo_public_bindings_unittests
mojo_public_system_unittests
mojo_system_unittests
nacl_loader_unittests
ppapi_unittests
printing_unittests
remoting_unittests
skia_unittests
sql_unittests
sync_integration_tests
sync_unit_tests
ui_base_unittests
unit_tests
url_unittests
views_unittests

Note that all remaining open issues are not marked with ReleaseBlock.

Erik, can this bug be closed? It looks like we have a 10.12 bot on the waterfall now.