New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 765114 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

[Telemetry] [Tracking bug] testHeapProfilerForSmoke not working on some platforms

Project Member Reported by kraynov@chromium.org, Sep 14 2017

Issue description

Currently disabled on:
- Chrome OS
- Reference builds

Failing on Win7 Tests (dbg) bot with
self.assertEquals(dumps_detailed[0].value, dumps_heap_profiler[0].value) AssertionError: 1 != 0

Should be disabled on Windows while we investigate.
Close this bug when this test is enabled on all platform or good reason provided for exclusion.
 
Summary: [Telemetry] [Tracking bug] testHeapProfilerForSmoke not working on some platforms (was: [Telemetry] [Tracking bug] testHeapProfilerForSmoke not working on all platforms)
Project Member

Comment 2 by bugdroid1@chromium.org, Sep 14 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/cfa21bcfdd1a5052e2397d7a3ca58c8a936dbdc6

commit cfa21bcfdd1a5052e2397d7a3ca58c8a936dbdc6
Author: catapult-deps-roller@chromium.org <catapult-deps-roller@chromium.org>
Date: Thu Sep 14 11:58:16 2017

Roll src/third_party/catapult/ 743ca01bf..dd30f4f38 (1 commit)

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/743ca01bfe12..dd30f4f3837e

$ git log 743ca01bf..dd30f4f38 --date=short --no-merges --format='%ad %ae %s'
2017-09-14 kraynov Disable testHeapProfilerForSmoke on Windows.

Created with:
  roll-dep src/third_party/catapult
BUG=765114


Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

If the roll is causing failures, see:
http://www.chromium.org/developers/tree-sheriffs/sheriff-details-chromium#TOC-Failures-due-to-DEPS-rolls


CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.android:android_optional_gpu_tests_rel
TBR=sullivan@chromium.org

Change-Id: I70befd4bce6df479a4c6d9a9225f2c0f255443d8
Reviewed-on: https://chromium-review.googlesource.com/666049
Reviewed-by: <catapult-deps-roller@chromium.org>
Commit-Queue: <catapult-deps-roller@chromium.org>
Cr-Commit-Position: refs/heads/master@{#501924}
[modify] https://crrev.com/cfa21bcfdd1a5052e2397d7a3ca58c8a936dbdc6/DEPS

Cc: kraynov@chromium.org
Owner: perezju@chromium.org
perezju@ PTAL someday (not time critical) thanks!
Cc: hjd@chromium.org
Owner: primiano@chromium.org
This sounds like the same issue in:
https://github.com/catapult-project/catapult/issues/2610#issuecomment-285639223

where a similar test fails for Windows.

+Primiano, +Hector; any idea if these are expected to fail on Windows? Who could investigate these?

Comment 5 by hjd@chromium.org, Nov 14 2017

No idea sorry :(
Will the out-of-process heap profiler exercise this test?
If not, it doesn't seem worth fighting to enable it just in time for it to be deprecated.
If so, maybe the desktop memory folks can take a look since they are working on the heap profiler at the moment?


Components: Test>Telemetry
Components: -Speed>Telemetry

Sign in to add a comment