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

Issue 883321 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Sep 26
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 906166



Sign in to add a comment

Implement a set of "reapply patch" steps for the chromium CQ

Project Member Reported by erikc...@chromium.org, Sep 12

Issue description

This series of steps will run after the "deapply patch" steps. It will roll tip of tree, reapply the patch, and then run the failing tests. If the same tests fail as the original, then the build is marked as a failure. Otherwise, the build is marked as a success. 

See design doc for more details: https://docs.google.com/document/d/1YF3SAd7f9ekiwV-6CxYsf7f0FthY6ClAw9znS7N8xU0/edit#
 
Due to a typo in the CL description, this CL failed to get posted to the bug when committed:
https://chromium-review.googlesource.com/c/chromium/tools/build/+/1222326

"""
Add comments to chromium_tests trybot methods.

This CL has no functional change.

This CL adds detailed comments for the _trybot_steps_internal and
run_tests_on_tryserver in preparation for future refactors.
"""
Cc: liaoyuke@chromium.org st...@chromium.org
Labels: -Pri-3 Pri-1
+liaoyuke, stgao: FYI
Project Member

Comment 4 by bugdroid1@chromium.org, Sep 13

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/5965d3363f9745a40c54d9cbda7302470ec0ebab

commit 5965d3363f9745a40c54d9cbda7302470ec0ebab
Author: erikchen <erikchen@chromium.org>
Date: Thu Sep 13 20:04:02 2018

Remove the method test_utils.determine_new_failures.

This CL is a refactor with no intended behavior change.

The method determine_new_failures is used in exactly two places -- the
chromium_tests recipe module and the blink_downstream recipe.

There are three problems with determine_new_failures.
  * The method takes a closure that references global state. Running this
    closure has significant side effects. This makes it difficult to follow the
    control flow.
  * The retry logic for chromium_tests will be changing in the future. It will
    be difficult to modify determine_new_failures to take on the new behavior,
    partly due to the closure mentioned above.
  * The retry logic for chromium_tests will be diverging from that of
    blink_downstream.

This CL removes the method. The logic was copied into blink_downstream with no
changes. The functionality in chromium_tests is identical to before, but the new
logic is significantly simpler.

This CL removes some debugging logic added in
https://chromium-review.googlesource.com/c/chromium/tools/build/+/1115874 that
is no longer necessary.

Bug:  883321 , 850653
Change-Id: Ie575ddcff824007a7543c344b327e1d7d86bb449
Reviewed-on: https://chromium-review.googlesource.com/1222648
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>

[modify] https://crrev.com/5965d3363f9745a40c54d9cbda7302470ec0ebab/scripts/slave/README.recipes.md
[modify] https://crrev.com/5965d3363f9745a40c54d9cbda7302470ec0ebab/scripts/slave/recipes/blink_downstream.py
[modify] https://crrev.com/5965d3363f9745a40c54d9cbda7302470ec0ebab/scripts/slave/recipe_modules/chromium_tests/api.py
[modify] https://crrev.com/5965d3363f9745a40c54d9cbda7302470ec0ebab/scripts/slave/recipes/chromium_trybot.expected/compile_failure_without_patch_deapply_fn.json
[modify] https://crrev.com/5965d3363f9745a40c54d9cbda7302470ec0ebab/scripts/slave/recipe_modules/test_utils/api.py

Project Member

Comment 5 by bugdroid1@chromium.org, Sep 13

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/6dc3ad72d7ff982d54391165588d798822e0ec36

commit 6dc3ad72d7ff982d54391165588d798822e0ec36
Author: erikchen <erikchen@chromium.org>
Date: Thu Sep 13 20:24:17 2018

Refactor in preparation for roll-checkout-apply-patch retries.

This CL adds a parameter to summarize_retried_test to prevent emission of a
failing step. This is in preparation for roll-checkout-apply-patch retries, for
which a failure in retry without patch will not be the last step in the retry
process.

Change-Id: I71fc05efac0fbf1ea254af888cfcb3eed08cc0be
Bug:  883321 
Reviewed-on: https://chromium-review.googlesource.com/1225152
Commit-Queue: Erik Chen <erikchen@chromium.org>
Reviewed-by: John Budorick <jbudorick@chromium.org>

[modify] https://crrev.com/6dc3ad72d7ff982d54391165588d798822e0ec36/scripts/slave/recipes/blink_downstream.py
[modify] https://crrev.com/6dc3ad72d7ff982d54391165588d798822e0ec36/scripts/slave/recipes/blink_downstream.expected/full_client_v8_fyi_V8_Blink_Mac_fail.json
[modify] https://crrev.com/6dc3ad72d7ff982d54391165588d798822e0ec36/scripts/slave/recipes/chromium_trybot.expected/swarmed_webkit_tests_unexpected_error.json
[modify] https://crrev.com/6dc3ad72d7ff982d54391165588d798822e0ec36/scripts/slave/recipes/blink_downstream.expected/full_client_v8_fyi_V8_Blink_Win_fail.json
[modify] https://crrev.com/6dc3ad72d7ff982d54391165588d798822e0ec36/scripts/slave/recipes/blink_downstream.expected/minimal_pass_continues.json
[modify] https://crrev.com/6dc3ad72d7ff982d54391165588d798822e0ec36/scripts/slave/recipes/blink_downstream.expected/full_client_v8_fyi_V8_Blink_Linux_64__dbg__fail.json
[modify] https://crrev.com/6dc3ad72d7ff982d54391165588d798822e0ec36/scripts/slave/README.recipes.md
[modify] https://crrev.com/6dc3ad72d7ff982d54391165588d798822e0ec36/scripts/slave/recipes/blink_downstream.expected/full_client_v8_fyi_V8_Blink_Linux_64___future_fail.json
[modify] https://crrev.com/6dc3ad72d7ff982d54391165588d798822e0ec36/scripts/slave/recipe_modules/test_utils/api.py
[modify] https://crrev.com/6dc3ad72d7ff982d54391165588d798822e0ec36/scripts/slave/recipes/blink_downstream.expected/full_client_v8_fyi_V8_Blink_Linux_64_fail.json
[modify] https://crrev.com/6dc3ad72d7ff982d54391165588d798822e0ec36/scripts/slave/recipe_modules/chromium_tests/api.py
[modify] https://crrev.com/6dc3ad72d7ff982d54391165588d798822e0ec36/scripts/slave/recipes/chromium_trybot.expected/swarmed_webkit_tests_interrupted.json
[modify] https://crrev.com/6dc3ad72d7ff982d54391165588d798822e0ec36/scripts/slave/recipes/blink_downstream.expected/too_many_failures_for_retcode.json
[modify] https://crrev.com/6dc3ad72d7ff982d54391165588d798822e0ec36/scripts/slave/recipes/chromium_trybot.expected/swarmed_layout_tests_too_many_failures_for_retcode.json

Project Member

Comment 6 by bugdroid1@chromium.org, Sep 14

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/4b8f4a6db7d57e70dc51fef43459266d104decd7

commit 4b8f4a6db7d57e70dc51fef43459266d104decd7
Author: erikchen <erikchen@chromium.org>
Date: Fri Sep 14 20:30:05 2018

Add support for 'retry with patch' to trybot configurations.

This CL implements logic for 'retry with patch' behind a trybot configuration
flag 'retry_with_patch'. This logic is only used in tests for now. This CL
should not change the behavior of production code.

This CL makes the following changes:
  * Adds a '--dest-filename' flag to archive_layout_test_retry_summary.py so
    that the two different retries 'without patch' and 'retry with patch' can
    upload results to different destinations.
  * Adds logic to _run_tests_on_tryserver() to implement 'retry with patch'.
    This primarily consists of moving the business logic from
    _deapply_patch_build_isolate to _build_and_isolate_failing_tests, and then
    adding a new method _reapply_patch_build_isolate which also calls this new
    method.
  * Moves the business logic from summarize_test_with_patch_deapplied to
    _summarize_new_and_ignored_failures. Adds a new method
    summarize_test_with_patch_reapplied which also calls out to
    _summarize_new_and_ignored_failures.

Change-Id: I27cdb417780d4921e733da4d594c64d5702e2cca
Bug:  883321 
Reviewed-on: https://chromium-review.googlesource.com/1226311
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>

[modify] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/recipes/blink_downstream.expected/full_client_v8_fyi_V8_Blink_Win_fail.json
[modify] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/recipes/blink_downstream.expected/full_client_v8_fyi_V8_Blink_Mac_fail.json
[add] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/recipe_modules/chromium_tests/tests/api/run_tests_on_tryserver.expected/enable_retry_with_patch_succeed_after_deapply.json
[modify] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/recipes/chromium_trybot.expected/swarmed_webkit_tests_unexpected_error.json
[add] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/recipe_modules/chromium_tests/tests/api/run_tests_on_tryserver.expected/enable_retry_with_patch_invalid_test_results.json
[modify] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/recipes/blink_downstream.expected/full_client_v8_fyi_V8_Blink_Linux_64_fail.json
[modify] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/recipes/blink_downstream.expected/minimal_pass_continues.json
[modify] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/recipes/blink_downstream.expected/full_client_v8_fyi_V8_Blink_Linux_64__dbg__fail.json
[modify] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/README.recipes.md
[modify] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/recipes/blink_downstream.expected/full_client_v8_fyi_V8_Blink_Linux_64___future_fail.json
[modify] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/recipes/chromium_trybot.expected/compile_failure_without_patch_deapply_fn.json
[modify] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/chromium/archive_layout_test_retry_summary.py
[add] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/recipe_modules/chromium_tests/tests/api/run_tests_on_tryserver.expected/enable_retry_with_patch_recipes.json
[modify] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/recipe_modules/test_utils/api.py
[modify] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/recipe_modules/chromium_tests/api.py
[modify] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/recipes/chromium_trybot.expected/swarmed_webkit_tests_interrupted.json
[modify] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/recipes/blink_downstream.expected/too_many_failures_for_retcode.json
[modify] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/recipe_modules/chromium_tests/tests/api/run_tests_on_tryserver.py
[modify] https://crrev.com/4b8f4a6db7d57e70dc51fef43459266d104decd7/scripts/slave/recipes/chromium_trybot.expected/swarmed_layout_tests_too_many_failures_for_retcode.json

liaoyuke@: we need to follow up with this upcoming change, because it might affect our query to detect flaky tests.
Project Member

Comment 8 by bugdroid1@chromium.org, Sep 14

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/6da36f643531d55fb4be8748781d349cbe09fed3

commit 6da36f643531d55fb4be8748781d349cbe09fed3
Author: erikchen <erikchen@chromium.org>
Date: Fri Sep 14 21:02:59 2018

Add support for 'retry with patch' to chromium_tests base Test class.

This CL does not change any production functionality. The new logic is only used
in tests.

This CL adds a method tests_to_retry() to the Test base class. It can be called
from any subclass and will correctly return the tests to run.

This allows removal of quite a bit of duplicated code. It also allows for the
addition of a new suffix 'retry with patch'.

This CL fixes one small bug in order to make tests pass:
  * In blink_test.py, the 'without patch' step was never being run because it
    was outside of the finally block.

A side effect of this CL is that test suites will never be passed an empty list
of tests to filter/test. This behavior is poorly defined [should all tests run?
no tests run?].

Change-Id: I0ec82b0ca4fdaf597b1ef713a8eba10a37c3ab5a
Bug:883321
Reviewed-on: https://chromium-review.googlesource.com/1225712
Commit-Queue: Erik Chen <erikchen@chromium.org>
Reviewed-by: Stephen Martinis <martiniss@chromium.org>

[modify] https://crrev.com/6da36f643531d55fb4be8748781d349cbe09fed3/scripts/slave/recipe_modules/chromium_tests/tests/steps/blink_test.expected/android.json
[modify] https://crrev.com/6da36f643531d55fb4be8748781d349cbe09fed3/scripts/slave/recipe_modules/chromium_tests/tests/steps/local_gtest_test.expected/android.json
[modify] https://crrev.com/6da36f643531d55fb4be8748781d349cbe09fed3/scripts/slave/recipe_modules/chromium_tests/tests/api/run_tests_on_tryserver.expected/enable_retry_with_patch_invalid_test_results.json
[modify] https://crrev.com/6da36f643531d55fb4be8748781d349cbe09fed3/scripts/slave/recipe_modules/chromium_tests/tests/steps/local_gtest_test.py
[modify] https://crrev.com/6da36f643531d55fb4be8748781d349cbe09fed3/scripts/slave/recipe_modules/chromium_tests/tests/steps/blink_test.expected/big.json
[modify] https://crrev.com/6da36f643531d55fb4be8748781d349cbe09fed3/scripts/slave/recipe_modules/chromium_tests/tests/steps/blink_test.py
[modify] https://crrev.com/6da36f643531d55fb4be8748781d349cbe09fed3/scripts/slave/README.recipes.md
[modify] https://crrev.com/6da36f643531d55fb4be8748781d349cbe09fed3/scripts/slave/recipe_modules/chromium_tests/steps.py
[modify] https://crrev.com/6da36f643531d55fb4be8748781d349cbe09fed3/scripts/slave/recipe_modules/chromium_tests/tests/steps/blink_test.expected/win.json
[add] https://crrev.com/6da36f643531d55fb4be8748781d349cbe09fed3/scripts/slave/recipe_modules/chromium_tests/tests/steps/local_gtest_test.expected/retry.json
[modify] https://crrev.com/6da36f643531d55fb4be8748781d349cbe09fed3/scripts/slave/recipe_modules/chromium_tests/tests/api/run_tests_on_tryserver.expected/enable_retry_with_patch_recipes.json
[modify] https://crrev.com/6da36f643531d55fb4be8748781d349cbe09fed3/scripts/slave/recipe_modules/chromium_tests/tests/steps/blink_test.expected/unexpected_flakes.json
[modify] https://crrev.com/6da36f643531d55fb4be8748781d349cbe09fed3/scripts/slave/recipes/blink_downstream.expected/too_many_failures_for_retcode.json
[modify] https://crrev.com/6da36f643531d55fb4be8748781d349cbe09fed3/scripts/slave/recipe_modules/chromium_tests/tests/steps/local_gtest_test.expected/basic.json

Project Member

Comment 9 by bugdroid1@chromium.org, Sep 14

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/150f1b24841ed7d1cbcb38e4fb2b484ff0726bfc

commit 150f1b24841ed7d1cbcb38e4fb2b484ff0726bfc
Author: erikchen <erikchen@chromium.org>
Date: Fri Sep 14 21:10:40 2018

Add 'retry with patch' step to win7_chromium_rel_ng trybots.

Prior research at
https://bugs.chromium.org/p/chromium/issues/detail?id=882969#c8 suggests that at
least 77% of retries in win7_chromium_rel_ng are flakes. This CL turns on the
'retry with patch' step which retries only the failing tests in the chromium
trybot recipe.

This should greatly reduce cycle time on win7_chromium_rel_ng by [frequently]
skipping full retries caused by flakiness.

This change has been tested via led at
https://chromium-swarm.appspot.com/task?id=3ff2793164cdda10&refresh=10.

Bug:  882969 ,  883321 
Change-Id: Ibb85e3d13cb464aa3aef0db30ba339368917c82d
Reviewed-on: https://chromium-review.googlesource.com/1226313
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>

[modify] https://crrev.com/150f1b24841ed7d1cbcb38e4fb2b484ff0726bfc/scripts/slave/recipe_modules/chromium_tests/trybots.py

Project Member

Comment 10 by bugdroid1@chromium.org, Sep 17

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/e10399ad98774a1fd5fcf127f30110941ea79a10

commit e10399ad98774a1fd5fcf127f30110941ea79a10
Author: erikchen <erikchen@chromium.org>
Date: Mon Sep 17 18:27:35 2018

Add 'retry with patch' step to android-marshmallow-arm64-rel trybots.

This change has been tested via led at
https://chromium-swarm.appspot.com/task?id=3ff2c4bea8af1d10.

Bug:  882969 ,  883321 
Change-Id: I91a27452091fc7d6457993b96de1d089fb309170
Reviewed-on: https://chromium-review.googlesource.com/1226314
Reviewed-by: Stephen Martinis <martiniss@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>

[modify] https://crrev.com/e10399ad98774a1fd5fcf127f30110941ea79a10/scripts/slave/recipe_modules/chromium_tests/trybots.py

Cc: yvesg@google.com phoglund@chromium.org
Hi, is it possible that one of these patches are affecting https://ci.chromium.org/p/chromium/builders/luci.chromium.try/mac_chromium_archive_rel_ng?

If yes, it is blocking the WebRTC roll into Chromium.

On 2018-09-14 we had the last green run:
https://ci.chromium.org/p/chromium/builders/luci.chromium.try/mac_chromium_archive_rel_ng/2198

And since that we see a failure in the "without patch" part:
https://ci.chromium.org/p/chromium/builders/luci.chromium.try/mac_chromium_archive_rel_ng/2201

This is the error message:
Traceback (most recent call last):
  File "/b/s/w/ir/kitchen-checkout/recipe_engine/recipe_engine/run.py", line 287, in _new_run
    recipe_result = recipe_script.run(api, self.properties, self.environ)
  File "/b/s/w/ir/kitchen-checkout/recipe_engine/recipe_engine/loader.py", line 108, in run
    self.run_steps, properties, environ, self.PROPERTIES, api=api)
  File "/b/s/w/ir/kitchen-checkout/recipe_engine/recipe_engine/loader.py", line 636, in invoke_with_properties
    arg_names, **additional_args)
  File "/b/s/w/ir/kitchen-checkout/recipe_engine/recipe_engine/loader.py", line 599, in _invoke_with_properties
    return callable_obj(*props, **additional_args)
  File "/b/s/w/ir/kitchen-checkout/build/scripts/slave/recipes/chromium_trybot.py", line 46, in RunSteps
    return api.chromium_tests.trybot_steps()
  File "/b/s/w/ir/kitchen-checkout/recipe_engine/recipe_engine/recipe_api.py", line 765, in _inner
    return func(*a, **kw)
  File "/b/s/w/ir/kitchen-checkout/build/scripts/slave/recipe_modules/chromium_tests/api.py", line 1110, in trybot_steps
    enable_retry_with_patch=enable_retry_with_patch)
  File "/b/s/w/ir/kitchen-checkout/recipe_engine/recipe_engine/recipe_api.py", line 765, in _inner
    return func(*a, **kw)
  File "/b/s/w/ir/kitchen-checkout/build/scripts/slave/recipe_modules/chromium_tests/api.py", line 897, in _run_tests_on_tryserver
    self.m.test_utils.run_tests(self.m, failing_tests, 'without patch')
  File "/b/s/w/ir/kitchen-checkout/recipe_engine/recipe_engine/recipe_api.py", line 765, in _inner
    return func(*a, **kw)
  File "/b/s/w/ir/kitchen-checkout/build/scripts/slave/recipe_modules/test_utils/api.py", line 159, in run_tests
    t.run(caller_api, suffix)
  File "/b/s/w/ir/kitchen-checkout/build/scripts/slave/recipe_modules/chromium_tests/steps.py", line 499, in run
    '--filter-file', api.json.input(tests_to_retry)
  File "/b/s/w/ir/kitchen-checkout/recipe_engine/recipe_engine/recipe_api.py", line 765, in _inner
    return func(*a, **kw)
  File "/b/s/w/ir/kitchen-checkout/recipe_engine/recipe_engine/util.py", line 135, in inner
    ret = static_call(self, func, *args, **kwargs)
  File "/b/s/w/ir/kitchen-checkout/recipe_engine/recipe_engine/util.py", line 122, in static_call
    return func(obj, *args, **kwargs)
  File "/b/s/w/ir/kitchen-checkout/recipe_engine/recipe_modules/json/api.py", line 105, in input
    return self.m.raw_io.input_text(self.dumps(data), '.json')
  File "/b/s/w/ir/kitchen-checkout/recipe_engine/recipe_modules/json/api.py", line 20, in dumps
    return json.dumps(*args, **kwargs)
  File "/b/s/w/ir/cipd_bin_packages/lib/python2.7/json/__init__.py", line 251, in dumps
    sort_keys=sort_keys, **kw).encode(obj)
  File "/b/s/w/ir/cipd_bin_packages/lib/python2.7/json/encoder.py", line 209, in encode
    chunks = list(chunks)
  File "/b/s/w/ir/cipd_bin_packages/lib/python2.7/json/encoder.py", line 442, in _iterencode
    o = _default(o)
  File "/b/s/w/ir/kitchen-checkout/recipe_engine/recipe_engine/config_types.py", line 26, in json_fixup
    raise TypeError("%r is not JSON serializable" % obj)
TypeError: set(['mac-release/sizes/chrome-si/initializers']) is not JSON serializable


Hi -- it looks like the root problem is that the sizes step is failing. [both with and without patch]

There appears to be a second problem wherein the recipe is trying to serialize a set() to a JSON. I'll look into that.
Screen Shot 2018-09-18 at 9.29.46 AM.png
768 KB View Download
Ah -- looks like my change caused us to incorrectly use sets where we should be using lists. Fix incomign.
Project Member

Comment 14 by bugdroid1@chromium.org, Sep 18

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/dcd03e0eab2de222ec020d54add908f589691c2d

commit dcd03e0eab2de222ec020d54add908f589691c2d
Author: erikchen <erikchen@chromium.org>
Date: Tue Sep 18 14:54:33 2018

Use list instead of set for tests_to_retry.

Bug:  883321 
Change-Id: Ibeeafb720ad1cfcd243d9bd3361750ca3b13763e
TBR:martiniss@chromium.org
Reviewed-on: https://chromium-review.googlesource.com/1230414
Commit-Queue: Erik Chen <erikchen@chromium.org>
Reviewed-by: Marc-Antoine Ruel <maruel@chromium.org>

[modify] https://crrev.com/dcd03e0eab2de222ec020d54add908f589691c2d/scripts/slave/recipe_modules/chromium_tests/tests/steps/swarming_isolated_script_test.expected/without_patch_filter.json
[modify] https://crrev.com/dcd03e0eab2de222ec020d54add908f589691c2d/scripts/slave/recipe_modules/chromium_tests/tests/steps/blink_test.expected/big.json
[modify] https://crrev.com/dcd03e0eab2de222ec020d54add908f589691c2d/scripts/slave/recipe_modules/chromium_tests/steps.py
[modify] https://crrev.com/dcd03e0eab2de222ec020d54add908f589691c2d/scripts/slave/recipes/blink_downstream.expected/too_many_failures_for_retcode.json
[modify] https://crrev.com/dcd03e0eab2de222ec020d54add908f589691c2d/scripts/slave/recipes/chromium_trybot.expected/dynamic_isolated_script_test_on_trybot_failing.json
[modify] https://crrev.com/dcd03e0eab2de222ec020d54add908f589691c2d/scripts/slave/recipes/chromium_trybot.expected/swarmed_webkit_tests_interrupted.json
[modify] https://crrev.com/dcd03e0eab2de222ec020d54add908f589691c2d/scripts/slave/recipes/chromium_trybot.expected/swarmed_webkit_tests_unexpected_error.json
[modify] https://crrev.com/dcd03e0eab2de222ec020d54add908f589691c2d/scripts/slave/recipes/chromium_trybot.expected/swarmed_layout_tests_too_many_failures_for_retcode.json

Project Member

Comment 15 by bugdroid1@chromium.org, Sep 24

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/tools/build/+/6f802d525fd8cc689be520f4340d3cd51af2f94d

commit 6f802d525fd8cc689be520f4340d3cd51af2f94d
Author: erikchen <erikchen@chromium.org>
Date: Mon Sep 24 22:24:00 2018

All chromium tests should use 'retry with patch' by default.

'retry with patch' is much cheaper than full CQ retries, since it only
reruns failing tests. For the two builders that fail most frequently, 'retry
with patch' reduces failures by 4-11X. Turning it on for all builders should
both reduce fleet utilization, and reduce false rejects.

For more details, see  https://crbug.com/882969#c23 .

Bug:  882969 ,  883321 
Change-Id: I03bc3c2680e488891688587878e00a093286aefb
Reviewed-on: https://chromium-review.googlesource.com/1241655
Reviewed-by: John Budorick <jbudorick@chromium.org>
Commit-Queue: Erik Chen <erikchen@chromium.org>

[modify] https://crrev.com/6f802d525fd8cc689be520f4340d3cd51af2f94d/scripts/slave/recipes/chromium_trybot.expected/invalid_results.json
[modify] https://crrev.com/6f802d525fd8cc689be520f4340d3cd51af2f94d/scripts/slave/recipes/chromium_trybot.expected/swarming_test_failure.json
[modify] https://crrev.com/6f802d525fd8cc689be520f4340d3cd51af2f94d/scripts/slave/recipes/chromium_trybot.expected/dynamic_swarmed_isolated_script_test_failure_no_result_json.json
[modify] https://crrev.com/6f802d525fd8cc689be520f4340d3cd51af2f94d/scripts/slave/recipes/chromium_trybot.expected/swarming_trigger_failure.json
[modify] https://crrev.com/6f802d525fd8cc689be520f4340d3cd51af2f94d/scripts/slave/recipe_modules/chromium_tests/api.py
[modify] https://crrev.com/6f802d525fd8cc689be520f4340d3cd51af2f94d/scripts/slave/recipes/chromium_trybot.expected/dynamic_isolated_script_test_on_trybot_failing.json
[modify] https://crrev.com/6f802d525fd8cc689be520f4340d3cd51af2f94d/scripts/slave/recipes/chromium_trybot.expected/swarmed_webkit_tests_interrupted.json
[modify] https://crrev.com/6f802d525fd8cc689be520f4340d3cd51af2f94d/scripts/slave/recipes/chromium_trybot.expected/swarmed_webkit_tests_unexpected_error.json
[modify] https://crrev.com/6f802d525fd8cc689be520f4340d3cd51af2f94d/scripts/slave/recipes/chromium_trybot.expected/swarmed_layout_tests_too_many_failures_for_retcode.json

Status: Fixed (was: Assigned)
Blocking: 906166

Sign in to add a comment