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

Issue 678957 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

Catapult roll is blocked due to failure in telemetry_perf_unittest in android_n5x_swarming_rel

Project Member Reported by nedngu...@google.com, Jan 6 2017

Issue description

An example roll:

https://codereview.chromium.org/2617703005

Failure log:
https://chromium-swarm.appspot.com/task?id=338cb4158a241110&refresh=10&show_raw=1


Almost all of these failures are due to certain files or directory are missing. So I am suspecting this is infra failure. May this has something to do with the swarming bot's hard disk is full?


The failures are:
[213/317] core.benchmark_finders_unittest.TestGetBenchmarkNamesForFile.testListSimpleBenchmarksDefinedInOneFile failed unexpectedly 0.0002s:
Traceback (most recent call last):
File "/b/swarm_slave/w/irdEv_F6/tools/perf/core/benchmark_finders_unittest.py", line 23, in testListSimpleBenchmarksDefinedInOneFile
File "/b/swarm_slave/w/irdEv_F6/tools/perf/core/benchmark_finders.py", line 31, in GetBenchmarkNamesForFile
IOError: [Errno 2] No such file or directory



[221/317] core.trybot_command_unittest.TrybotCommandTest.testAttemptTryjobAllForCrRepo failed unexpectedly 0.0146s:
Traceback (most recent call last):
File "/b/swarm_slave/w/irdEv_F6/third_party/catapult/telemetry/third_party/mock/mock.py", line 1201, in patched
File "/b/swarm_slave/w/irdEv_F6/tools/perf/core/trybot_command_unittest.py", line 646, in testAttemptTryjobAllForCrRepo
File "/b/swarm_slave/w/irdEv_F6/tools/perf/core/trybot_command_unittest.py", line 86, in _MockTempFile
File "/usr/lib/python2.7/tempfile.py", line 308, in mkstemp
return _mkstemp_inner(dir, prefix, suffix, flags)
File "/usr/lib/python2.7/tempfile.py", line 239, in _mkstemp_inner
fd = _os.open(file, flags, 0600)
OSError: [Errno 2] No such file or directory: '/b/swarm_slave/w/itKvWjlN/clDMrlay.json'

[268/317] measurements.rasterize_and_record_micro_unittest.RasterizeAndRecordMicroUnitTest.testRasterizeAndRecordMicro failed unexpectedly 0.0003s:
Traceback (most recent call last):
File "/b/swarm_slave/w/irdEv_F6/tools/perf/measurements/rasterize_and_record_micro_unittest.py", line 30, in testRasterizeAndRecordMicro
File "/b/swarm_slave/w/irdEv_F6/third_party/catapult/telemetry/telemetry/testing/page_test_test_case.py", line 38, in CreateStorySetFromFileInUnittestDataDir
File "/b/swarm_slave/w/irdEv_F6/third_party/catapult/telemetry/telemetry/testing/page_test_test_case.py", line 45, in CreateEmptyPageSet
File "/b/swarm_slave/w/irdEv_F6/third_party/catapult/telemetry/telemetry/story/story_set.py", line 42, in __init__
ValueError: Invalid directory path of base_dir: /b/swarm_slave/w/irdEv_F6/third_party/catapult/telemetry/telemetry/internal/testing
 
Cc: haraken@chromium.org
Labels: -Pri-1 Pri-0
I confirm that this happens to not just catapult roll CL but also other CLs that trigger telemetry_perf_unittest. 
Example CL by haraken@: https://codereview.chromium.org/2615213002

This is P0 because it's blocking CQ
Cc: martiniss@chromium.org
Adding martiniss@ as we had an issue with deleted files on some swarming bots earlier this week.  He might have some insight into any infra issues.
Status: Available (was: Untriaged)
This is a different issue than what happened earlier this week. Doubt it's the same bug. 

This isn't failing on every CQ attempt which runs telemetry_perf_unittest, right? Should it be a P0? I'm not familiar with the problem, but I noticed that not every CQ run is failing on it. https://luci-milo.appspot.com/buildbot/tryserver.chromium.linux/linux_chromium_rel_ng/366166 is an example of run which ran telemetry_perf_unittests and was ok.
Labels: -Pri-0 Pri-1
Status: WontFix (was: Available)
This was failing consistently but no longer happens (https://catapult-roll.skia.org/). Will reopen if I see this happens again

Sign in to add a comment