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

Issue 702694 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 708324



Sign in to add a comment

A lot of errors in Swarming rerun for flaky tests

Project Member Reported by st...@chromium.org, Mar 17 2017

Issue description

There are 45 errors out of 100 analyses.

We should investigate the reason. If it is test timeout, then we'd get the test execution time T_SECONDS from the Swarming task of the flake report, then use min(max(T_SECONDS * NUM_OF_RERUN * 2, 60 * 60), 2*60*60) as the timeout for the Swarming rerun.

As a first step, record the currently running Swarming task, and show it on the page.
 
Status: Started (was: Assigned)
Project Member

Comment 4 by bugdroid1@chromium.org, Mar 24 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/infra/infra/+/8cde5c68789a11a07a1753acf70d1cb2232a7df8

commit 8cde5c68789a11a07a1753acf70d1cb2232a7df8
Author: Jeffrey Li <lijeffrey@chromium.org>
Date: Fri Mar 24 01:42:26 2017

[Findit] Flake Analyzer - Surface last attempted swarming task/try job

BUG= 702694 

Change-Id: I4aea2931211500ca5aca65e831bd8f1a7444c893
Reviewed-on: https://chromium-review.googlesource.com/457781
Reviewed-by: Shuotao Gao <stgao@chromium.org>
Reviewed-by: Chan Li <chanli@chromium.org>
Reviewed-by: Roberto Carrillo <robertocn@chromium.org>
Commit-Queue: Jeffrey Li <lijeffrey@chromium.org>

[modify] https://crrev.com/8cde5c68789a11a07a1753acf70d1cb2232a7df8/appengine/findit/waterfall/process_flake_swarming_task_result_pipeline.py
[modify] https://crrev.com/8cde5c68789a11a07a1753acf70d1cb2232a7df8/appengine/findit/waterfall/flake/recursive_flake_pipeline.py
[modify] https://crrev.com/8cde5c68789a11a07a1753acf70d1cb2232a7df8/appengine/findit/model/flake/master_flake_analysis.py
[modify] https://crrev.com/8cde5c68789a11a07a1753acf70d1cb2232a7df8/appengine/findit/waterfall/flake/test/recursive_flake_pipeline_test.py
[modify] https://crrev.com/8cde5c68789a11a07a1753acf70d1cb2232a7df8/appengine/findit/handlers/flake/check_flake.py
[modify] https://crrev.com/8cde5c68789a11a07a1753acf70d1cb2232a7df8/appengine/findit/waterfall/flake/recursive_flake_try_job_pipeline.py
[modify] https://crrev.com/8cde5c68789a11a07a1753acf70d1cb2232a7df8/appengine/findit/waterfall/test/process_flake_swarming_task_result_pipeline_test.py
[modify] https://crrev.com/8cde5c68789a11a07a1753acf70d1cb2232a7df8/appengine/findit/handlers/flake/test/check_flake_test.py
[modify] https://crrev.com/8cde5c68789a11a07a1753acf70d1cb2232a7df8/appengine/findit/waterfall/flake/test/recursive_flake_try_job_pipeline_test.py
[modify] https://crrev.com/8cde5c68789a11a07a1753acf70d1cb2232a7df8/appengine/findit/templates/flake/result.html

it seems even after reducing the # of iterations to 200 still a few analyses run into timeouts. Need to investigate further how the timeout is determined, i.e. is it per test or per task and how to adjust it
Blocking: 708324
Status: Fixed (was: Started)
Status: Verified (was: Fixed)

Sign in to add a comment