[Telemetry] Re-enable ActionRunnerMeasureMemoryTest in reference builds

[Telemetry] Re-enable ActionRunnerMeasureMemoryTest in reference builds

Reference builds have been updated as required.

TBR=nednguyen@google.com
BUG=catapult:#2610

[perezju, 2017-03-10 09:56:47]

Description was changed from

==========
[Telemetry] Re-enable ActionRunnerMeasureMemoryTest in reference builds

Reference builds have been updated as required.

BUG=catapult:#2610
==========

to

==========
[Telemetry] Re-enable ActionRunnerMeasureMemoryTest in reference builds

Reference builds have been updated as required.

TBR=nednguyen@google.com
BUG=catapult:#2610
==========

[perezju, 2017-03-10 09:56:47]

perezju@chromium.org changed reviewers:
+ nednguyen@google.com

[perezju, 2017-03-10 09:56:56]

The CQ bit was checked by perezju@chromium.org

[commit-bot: I haz the power, 2017-03-10 09:57:10]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-10 10:27:15]

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

[commit-bot: I haz the power, 2017-03-10 10:27:16]

Try jobs failed on following builders:
  Catapult Windows Tryserver on master.tryserver.client.catapult (JOB_FAILED,
https://build.chromium.org/p/tryserver.client.catapult/builders/Catapult%20Wi...)

[perezju, 2017-06-05 09:22:41]

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

[commit-bot: I haz the power, 2017-06-05 09:22:49]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-06-05 09:55:58]

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

[commit-bot: I haz the power, 2017-06-05 09:55:59]

Dry run: Try jobs failed on following builders:
  Catapult Windows Tryserver on master.tryserver.client.catapult (JOB_FAILED,
https://build.chromium.org/p/tryserver.client.catapult/builders/Catapult%20Wi...)

[perezju, 2017-09-06 14:08:39]

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

[commit-bot: I haz the power, 2017-09-06 14:08:48]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-09-06 14:36:57]

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

[commit-bot: I haz the power, 2017-09-06 14:36:58]

Dry run: Try jobs failed on following builders:
  Catapult Windows Tryserver on master.tryserver.client.catapult (JOB_FAILED,
https://build.chromium.org/p/tryserver.client.catapult/builders/Catapult%20Wi...)

[perezju, 2017-09-06 14:39:32]

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

[commit-bot: I haz the power, 2017-09-06 14:39:37]

Dry run: CQ is trying da patch.

Follow status at:
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[perezju, 2017-09-06 15:21:27]

perezju@chromium.org changed reviewers:
+ primiano@chromium.org

[perezju, 2017-09-06 15:21:28]

+primiano

Is there any reason why we would expect these tests to still fail on reference
builds?

They just request a memory dump and check whether the dump is found on the
trace.

They fail when running on Windows stable, now on 60.0.3112.101 according to [1],
with: 'Unable to obtain memory dump'.

[1]:
https://github.com/catapult-project/catapult/blob/master/common/py_utils/py_u...

[commit-bot: I haz the power, 2017-09-06 15:42:47]

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

[commit-bot: I haz the power, 2017-09-06 15:42:48]

Dry run: Try jobs failed on following builders:
  Catapult Windows Tryserver on master.tryserver.client.catapult (JOB_FAILED,
https://build.chromium.org/p/tryserver.client.catapult/builders/Catapult%20Wi...)