Add more CHECKs to help investigate the Mojo bootstrap crash

Add more CHECKs to help investigate the Mojo bootstrap crash

The only plausible explanation I have is that the EDK is
being initialized with a null IO task runner. This should
confirm/deny that suspicion.

BUG=587807
TBR=jam@chromium.org

Committed: https://crrev.com/8fa2980459d0a4e8c52429321e26bf19cfcfd907
Cr-Commit-Position: refs/heads/master@{#376323}

[Ken Rockot(use gerrit already), 2016-02-18 23:17:54]

rockot@chromium.org changed reviewers:
+ amistry@chromium.org

[Ken Rockot(use gerrit already), 2016-02-18 23:18:04]

Description was changed from

==========
Add more CHECKs to help investigate the Mojo bootstrap crash

The only plausible explanation I have is that the EDK is
being initialized with a null IO task runner. This should
confirm/deny that suspicion.

BUG=587807
==========

to

==========
Add more CHECKs to help investigate the Mojo bootstrap crash

The only plausible explanation I have is that the EDK is
being initialized with a null IO task runner. This should
confirm/deny that suspicion.

BUG=587807
TBR=jam@chromium.org
==========

[Ken Rockot(use gerrit already), 2016-02-18 23:18:52]

The CQ bit was checked by rockot@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-02-18 23:19:55]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1714693002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1714693002/1

[Anand Mistry (off Chromium), 2016-02-18 23:39:18]

lgtm

[commit-bot: I haz the power, 2016-02-19 00:42:20]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-02-19 00:42:21]

Dry run: This issue passed the CQ dry run.

[Ken Rockot(use gerrit already), 2016-02-19 00:42:38]

The CQ bit was checked by rockot@chromium.org

[commit-bot: I haz the power, 2016-02-19 00:47:41]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1714693002/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1714693002/1

[commit-bot: I haz the power, 2016-02-19 00:58:05]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-02-19 00:59:10]

Description was changed from

==========
Add more CHECKs to help investigate the Mojo bootstrap crash

The only plausible explanation I have is that the EDK is
being initialized with a null IO task runner. This should
confirm/deny that suspicion.

BUG=587807
TBR=jam@chromium.org
==========

to

==========
Add more CHECKs to help investigate the Mojo bootstrap crash

The only plausible explanation I have is that the EDK is
being initialized with a null IO task runner. This should
confirm/deny that suspicion.

BUG=587807
TBR=jam@chromium.org

Committed: https://crrev.com/8fa2980459d0a4e8c52429321e26bf19cfcfd907
Cr-Commit-Position: refs/heads/master@{#376323}
==========

[commit-bot: I haz the power, 2016-02-19 00:59:12]

Patchset 1 (id:??) landed as
https://crrev.com/8fa2980459d0a4e8c52429321e26bf19cfcfd907
Cr-Commit-Position: refs/heads/master@{#376323}