[mojo-edk] Fix shutdown with old EDK.

[mojo-edk] Fix shutdown with old EDK.

The old EDK always initializes the new EDK as well, but it wasn't
shutting it down unless --use-new-edk was set. This was hitting
CHECKs to guard against double-initialization, because tests init
and shutdown the EDK multiple times in the same process.

This CL fixes that by always shutting the new EDK down as well.

Also we don't actually use g_io_thread_task_runner anymore so
I removed that.

TBRing since it's a pretty obvious fix IMHO and it's breaking
stuff on bots.

BUG=None
TBR=jam@chromium.org

Committed: https://crrev.com/3d0e9ea31ad19497d1328354ab75be25b9f9ad6a
Cr-Commit-Position: refs/heads/master@{#371748}

[Ken Rockot(use gerrit already), 2016-01-27 05:21:51]

Description was changed from

==========
[mojo-edk] Fix shutdown with old EDK.

The old EDK always initializes the new EDK as well, but it wasn't
shutting it down unless --use-new-edk was set. This was hitting
CHECKs to guard against double-initialization.

This CL fixes that by always shutting the new EDK down as well.

Also, we don't actually use g_io_thread_task_runner anymore so
I removed that.

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

to

==========
[mojo-edk] Fix shutdown with old EDK.

The old EDK always initializes the new EDK as well, but it wasn't
shutting it down unless --use-new-edk was set. This was hitting
CHECKs to guard against double-initialization, because tests init
and shutdown the EDK multiple times in the same process.

This CL fixes that by always shutting the new EDK down as well.

Also we don't actually use g_io_thread_task_runner anymore so
I removed that.

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

[Ken Rockot(use gerrit already), 2016-01-27 05:22:19]

Description was changed from

==========
[mojo-edk] Fix shutdown with old EDK.

The old EDK always initializes the new EDK as well, but it wasn't
shutting it down unless --use-new-edk was set. This was hitting
CHECKs to guard against double-initialization, because tests init
and shutdown the EDK multiple times in the same process.

This CL fixes that by always shutting the new EDK down as well.

Also we don't actually use g_io_thread_task_runner anymore so
I removed that.

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

to

==========
[mojo-edk] Fix shutdown with old EDK.

The old EDK always initializes the new EDK as well, but it wasn't
shutting it down unless --use-new-edk was set. This was hitting
CHECKs to guard against double-initialization, because tests init
and shutdown the EDK multiple times in the same process.

This CL fixes that by always shutting the new EDK down as well.

Also we don't actually use g_io_thread_task_runner anymore so
I removed that.

TBRing since it's a pretty obvious fix IMHO and it's breaking
stuff on bots.

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

[Ken Rockot(use gerrit already), 2016-01-27 05:23:02]

The CQ bit was checked by rockot@chromium.org

[commit-bot: I haz the power, 2016-01-27 05:23:49]

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

[commit-bot: I haz the power, 2016-01-27 06:23:20]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-01-27 06:25:28]

Description was changed from

==========
[mojo-edk] Fix shutdown with old EDK.

The old EDK always initializes the new EDK as well, but it wasn't
shutting it down unless --use-new-edk was set. This was hitting
CHECKs to guard against double-initialization, because tests init
and shutdown the EDK multiple times in the same process.

This CL fixes that by always shutting the new EDK down as well.

Also we don't actually use g_io_thread_task_runner anymore so
I removed that.

TBRing since it's a pretty obvious fix IMHO and it's breaking
stuff on bots.

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

to

==========
[mojo-edk] Fix shutdown with old EDK.

The old EDK always initializes the new EDK as well, but it wasn't
shutting it down unless --use-new-edk was set. This was hitting
CHECKs to guard against double-initialization, because tests init
and shutdown the EDK multiple times in the same process.

This CL fixes that by always shutting the new EDK down as well.

Also we don't actually use g_io_thread_task_runner anymore so
I removed that.

TBRing since it's a pretty obvious fix IMHO and it's breaking
stuff on bots.

BUG=None
TBR=jam@chromium.org

Committed: https://crrev.com/3d0e9ea31ad19497d1328354ab75be25b9f9ad6a
Cr-Commit-Position: refs/heads/master@{#371748}
==========

[commit-bot: I haz the power, 2016-01-27 06:25:29]

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