Do you have an example failing test? I see instances of enterprise_RemoraRequisitionServer[1], but not enterprise_RemoraRequisition.

1: https://wmatrix.googleplex.com/unfiltered?hide_missing=True&releases=tot&tests=enterprise_RemoraRequisitionServer

enterprise_RemoraRequisitionServer triggers the enterprise_RemoraRequisition client test. It does not get reported separately on wmatrix.

You can navigate through the enterprise_RemoraRequisitionServer test logs for any of these test runs to see the logs for enterprise_RemoraRequisition.

Seems like the short links i posted in the original post expired. Here are the debugs logs from both a working test and failing testing:
Passing test: https://pantheon.corp.google.com/m/cloudstorage/b/chromeos-autotest-results/o/57255229-chromeos-test/chromeos1-row3-rack5-host2/enterprise_RemoraRequisitionServer/enterprise_RemoraRequisition/debug/enterprise_RemoraRequisition.DEBUG

Failing test: https://pantheon.corp.google.com/m/cloudstorage/b/chromeos-autotest-results/o/57474613-chromeos-test/chromeos1-row3-rack5-host2/enterprise_RemoraRequisitionServer/enterprise_RemoraRequisition/debug/enterprise_RemoraRequisition.DEBUG



The issue seems to be with evaluating the following JS expression:
"document.readyState == 'complete' && document.getElementById('Email') != null",

Looks like this state is never met (when I run this test on a local test device, I can visually see that during enrollment process it never gets pass the initial screen, never gets to the screen where you enter email). The test somehow does not wait for this screen to come up and continue to execute the remaining code and fails when it tries to verify if the app launched or not.

This looks like a renderer crash in devtools / Chrome while loading the login screen. See [1] for a full stack trace. The rest of the logs are at [2].

 0  chrome!gfx::FontList::FontList [ref_counted.h : 280 + 0x0]
 1  chrome + 0x198a681
 2  chrome + 0x44cb229
 3  chrome + 0x44bdbcf
 4  chrome + 0x4480a63
 5  chrome + 0x19a5204
 6  chrome + 0x19a5878
 7  chrome!content::DevToolsAgent::OnDispatchOnInspectorBackend [devtools_agent.cc : 231 + 0xc]
 8  chrome!content::DevToolsAgent::OnMessageReceived [tuple.h : 166 + 0xf]
 9  chrome!content::RenderFrameImpl::OnMessageReceived [render_frame_impl.cc : 1351 + 0xc]
10  chrome!content::ChildThreadImpl::OnMessageReceived [child_thread_impl.cc : 669 + 0xd]
11  chrome!IPC::ChannelProxy::Context::OnDispatchMessage [ipc_channel_proxy.cc : 293 + 0x9]
12  chrome!base::debug::TaskAnnotator::RunTask [callback.h : 397 + 0x8]
13  chrome!scheduler::TaskQueueManager::DoWork [task_queue_manager.cc : 288 + 0x13]

 Bug 599947  also has a devtools crash, not sure if they are related.

1: https://pantheon.corp.google.com/m/cloudstorage/b/chromeos-autotest-results/o/57474613-chromeos-test/chromeos1-row3-rack5-host2/enterprise_RemoraRequisitionServer/enterprise_RemoraRequisition/sysinfo/iteration.1/var/spool/crash/chrome.20160321.232458.21527.dmp.txt
2: https://pantheon.corp.google.com/storage/browser/chromeos-autotest-results/57474613-chromeos-test/chromeos1-row3-rack5-host2/enterprise_RemoraRequisitionServer/

Yes, it's related. There is no context with id equals zero in DevTools. If you'd like to run in default context then please omit contextId argument.
After recent CL runtime.evaluate with contextId = 0 is producing crash in DevTools. I've fixed it in https://codereview.chromium.org/1867903002/.