Run mojo_apptests on debug Linux as well.

Run mojo_apptests on debug Linux as well.

Any test which runs on the main waterfall should run on debug and release. Otherwise a dcheck could be hit which wouldn't show up on the main waterfall, but would fail on the trybots which use release-with-asserts.

BUG=478244
Committed: https://crrev.com/a7cef43c8ed1c379bd2d6bb5fffd3a7ff2a38fb0
Cr-Commit-Position: refs/heads/master@{#376028}

[jam, 2016-02-17 19:01:00]

jam@chromium.org changed reviewers:
+ msw@chromium.org

[msw, 2016-02-17 19:07:39]

Nice, lgtm. maybe these were GYP bots when I originally added the step to the
other bots. (the FYI bot seems to flakily crash in resource provider apptests, I
wonder why that isn't happening on main/cq)

[msw, 2016-02-17 19:08:54]

Also, you can use BUG=478244

[jam, 2016-02-17 19:09:48]

On 2016/02/17 19:07:39, msw wrote:
> Nice, lgtm. maybe these were GYP bots when I originally added the step to the
> other bots. (the FYI bot seems to flakily crash in resource provider apptests,
I
> wonder why that isn't happening on main/cq)

the linux 32 is still gyp, so i've removed it from there and just added it to 64
bit linux debug.

not sure about differences with FYI. but if we see any failing on the main
waterfall flakily we should just disable them.

[jam, 2016-02-17 19:13:31]

Description was changed from

==========
Run mojo_apptests on debug Linux as well.

Any test which runs on the main waterfall should run on debug and release.
Otherwise a dcheck could be hit which wouldn't show up on the main waterfall,
but would fail on the trybots which use release-with-asserts.
==========

to

==========
Run mojo_apptests on debug Linux as well.

Any test which runs on the main waterfall should run on debug and release.
Otherwise a dcheck could be hit which wouldn't show up on the main waterfall,
but would fail on the trybots which use release-with-asserts.

BUG=478244
==========

[jam, 2016-02-17 21:24:57]

The CQ bit was checked by jam@chromium.org

[jam, 2016-02-17 21:24:58]

The patchset sent to the CQ was uploaded after l-g-t-m from msw@chromium.org
Link to the patchset: https://codereview.chromium.org/1705883002/#ps40001
(title: "build media mojo code for component builds")

[commit-bot: I haz the power, 2016-02-17 21:25:26]

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

[commit-bot: I haz the power, 2016-02-17 22:42:46]

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

[commit-bot: I haz the power, 2016-02-17 22:42:47]

Try jobs failed on following builders:
  linux_chromium_rel_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[jam, 2016-02-17 22:53:53]

The CQ bit was checked by jam@chromium.org

[commit-bot: I haz the power, 2016-02-17 22:55:22]

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

[commit-bot: I haz the power, 2016-02-17 23:27:50]

Description was changed from

==========
Run mojo_apptests on debug Linux as well.

Any test which runs on the main waterfall should run on debug and release.
Otherwise a dcheck could be hit which wouldn't show up on the main waterfall,
but would fail on the trybots which use release-with-asserts.

BUG=478244
==========

to

==========
Run mojo_apptests on debug Linux as well.

Any test which runs on the main waterfall should run on debug and release.
Otherwise a dcheck could be hit which wouldn't show up on the main waterfall,
but would fail on the trybots which use release-with-asserts.

BUG=478244
==========

[commit-bot: I haz the power, 2016-02-17 23:27:50]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2016-02-17 23:28:54]

Description was changed from

==========
Run mojo_apptests on debug Linux as well.

Any test which runs on the main waterfall should run on debug and release.
Otherwise a dcheck could be hit which wouldn't show up on the main waterfall,
but would fail on the trybots which use release-with-asserts.

BUG=478244
==========

to

==========
Run mojo_apptests on debug Linux as well.

Any test which runs on the main waterfall should run on debug and release.
Otherwise a dcheck could be hit which wouldn't show up on the main waterfall,
but would fail on the trybots which use release-with-asserts.

BUG=478244

Committed: https://crrev.com/a7cef43c8ed1c379bd2d6bb5fffd3a7ff2a38fb0
Cr-Commit-Position: refs/heads/master@{#376028}
==========

[commit-bot: I haz the power, 2016-02-17 23:28:54]

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