I'd love to disable compile (with patch) within 30 minutes but I suspect we'll need it for all of our testing.

Is chromium-try-flakes sophisticated enough to tell when compile failed on a patch vs. when it failed due to infrastructure failure?

Detected 4 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 8 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Yeah, the wording here could be improved a bit because this is not a flaky test, rather a flaky step which can't be disabled. I've filed issue 596286.

Detected 3 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 7 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 6 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

This is in the same class as issue 594612: the vast majority of these are failures to start goma. Assigning to Ukai to track both side-by-side.

Detected 3 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 3 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Removing troopers label, as it is currently assigned to Goma team.

According to https://goto.google.com/ytlnx, I do not see non 200 status code at initial ping since March 24th.  I suppose #10 is not caused by goma.  Let me check.

Not goma issue
file not found (possibly build script issue?) https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_rel_ng/builds/202439/steps/compile%20%28with%20patch%29/logs/stdio
compile error https://build.chromium.org/p/tryserver.chromium.android/builders/android_chromium_gn_compile_dbg/builds/40882/steps/compile%20%28with%20patch%29/logs/stdio
compile error https://build.chromium.org/p/tryserver.chromium.android/builders/android_clang_dbg_recipe/builds/40770/steps/compile%20%28with%20patch%29/logs/stdio

goma
timeout after GOMA Error https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_chromeos_ozone_rel_ng/builds/144462/steps/steps/logs/stdio
timeout after Goma Error https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_chromeos_rel_ng/builds/186170/steps/steps/logs/stdio
initial ping failure https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_chromeos_ozone_rel_ng/builds/144448/steps/compile%20%28with%20patch%29/logs/stdio

If possible I prefer to a bit increase timeout of initial ping but we might not usually see initial ping failure so much?

timeout after Goma Error looks strange but we do not have compiler_proxy.INFO for them.

Detected 4 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 4 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

found initial ping 408 in builder:linux_blink_oilpan_rel build number:22827, but nothing else. (twice)
Let me check why 6 new flakes shows up.

I checked last 4 entries reported in 595816.  All of them are not caused by goma.

User's issue:
https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_clobber_rel_ng/builds/149921/steps/compile%20%28with%20patch%29/logs/stdio
FAILED: /b/build/slave/linux_clobber/build/src/build/goma/client/gomacc ../../third_party/llvm-build/Release+Asserts/bin/clang++ -MMD -MF obj/chrome/browser/test_support_ui/password_manager_test_base.o.d -DV8_DEPRECATION_WARNINGS -DCLD_VERSION=2 -DENABLE_MDNS=1 -DENABLE_NOTIFICATIONS -DENABLE_PEPPER_CDMS -DENABLE_PLUGINS=1 -DENABLE_PDF=1 -DENABLE_PRINTING=1 -DENABLE_BASIC_PRINTING=1 -DENABLE_PRINT_PREVIEW=1 -DENABLE_SPELLCHECK=1 -DDCHECK_ALWAYS_ON=1 -DUSE_UDEV -DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 -DUSE_PANGO=1 -DUSE_CAIRO=1 -DUSE_CLIPBOARD_AURAX11=1 -DUSE_DEFAULT_RENDER_THEME=1 -DUSE_GLIB=1 -DUSE_OPENSSL=1 -DUSE_NSS_CERTS=1 -DUSE_NSS_VERIFIER=1 -DUSE_X11=1 -DENABLE_WEBRTC=1 -DENABLE_EXTENSIONS=1 -DENABLE_TASK_MANAGER=1 -DENABLE_THEMES=1 -DENABLE_CAPTIVE_PORTAL_DETECTION=1 -DENABLE_SESSION_SERVICE=1 -DENABLE_APP_LIST=1 -DENABLE_SETTINGS_APP=1 -DENABLE_SUPERVISED_USERS=1 -DENABLE_SERVICE_DISCOVERY=1 -DENABLE_AUTOFILL_DIALOG=1 -DENABLE_TOPCHROME_MD=1 -DFULL_SAFE_BROWSING -DSAFE_BROWSING_CSD -DSAFE_BROWSING_DB_LOCAL -DCHROMIUM_BUILD -DENABLE_MEDIA_ROUTER=1 -DFIELDTRIAL_TESTING_ENABLED -DCR_CLANG_REVISION=264334-1 -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 -DGOOGLE_PROTOBUF_NO_RTTI -DGOOGLE_PROTOBUF_NO_STATIC_INITIALIZER -DTOOLKIT_VIEWS=1 -DGL_GLEXT_PROTOTYPES -DGTEST_HAS_POSIX_RE=0 -DGTEST_LANG_CXX11=0 -DGTEST_HAS_RTTI=0 -DSK_IGNORE_LINEONLY_AA_CONVEX_PATH_OPTS -DSK_SUPPORT_GPU=1 -DUNIT_TEST -I../.. -Igen -I../../build/linux/debian_wheezy_amd64-sysroot/usr/include/glib-2.0 -I../../build/linux/debian_wheezy_amd64-sysroot/usr/lib/x86_64-linux-gnu/glib-2.0/include -I../../third_party/protobuf/src -Igen/protoc_out -I../../third_party/protobuf/src -I../../third_party/protobuf -I../../third_party/khronos -I../../gpu -I../../testing/gtest/include -I../../build/linux/debian_wheezy_amd64-sysroot/usr/include/nss -I../../build/linux/debian_wheezy_amd64-sysroot/usr/include/nspr -I../../third_party/boringssl/src/include -I../../testing/gmock/include -I../../skia/config -I../../skia/ext -I../../third_party/skia/include/c -I../../third_party/skia/include/config -I../../third_party/skia/include/core -I../../third_party/skia/include/effects -I../../third_party/skia/include/images -I../../third_party/skia/include/lazy -I../../third_party/skia/include/pathops -I../../third_party/skia/include/pdf -I../../third_party/skia/include/pipe -I../../third_party/skia/include/ports -I../../third_party/skia/include/utils -I../../third_party/skia/include/gpu -I../../third_party/skia/src/gpu -fno-strict-aliasing --param=ssp-buffer-size=4 -fstack-protector -funwind-tables -fPIC -pipe -B../../third_party/binutils/Linux_x64/Release/bin -fcolor-diagnostics -fdebug-prefix-map=/b/build/slave/linux_clobber/build/src=. -pthread -m64 -march=x86-64 -Wall -Werror -Wextra -Wno-missing-field-initializers -Wno-unused-parameter -Wno-c++11-narrowing -Wno-covered-switch-default -Wno-deprecated-register -Wno-unneeded-internal-declaration -Wno-inconsistent-missing-override -Wno-shift-negative-value -O2 -fno-ident -fdata-sections -ffunction-sections -g1 --sysroot=../../build/linux/debian_wheezy_amd64-sysroot -fvisibility=hidden -Xclang -load -Xclang ../../third_party/llvm-build/Release+Asserts/lib/libFindBadConstructs.so -Xclang -add-plugin -Xclang find-bad-constructs -Xclang -plugin-arg-find-bad-constructs -Xclang check-templates -Xclang -plugin-arg-find-bad-constructs -Xclang follow-macro-expansion -Wheader-hygiene -Wstring-conversion -Wno-header-guard -fno-threadsafe-statics -fvisibility-inlines-hidden -std=gnu++11 -fno-rtti -fno-exceptions -c ../../chrome/browser/password_manager/password_manager_test_base.cc -o obj/chrome/browser/test_support_ui/password_manager_test_base.o
In file included from ../../chrome/browser/password_manager/password_manager_test_base.cc:13:
In file included from ../../chrome/browser/password_manager/chrome_password_manager_client.h:15:
In file included from ../../components/password_manager/content/browser/credential_manager_impl.h:12:
In file included from gen/components/password_manager/content/public/interfaces/credential_manager.mojom.h:26:
gen/components/password_manager/content/public/interfaces/credential_manager.mojom-internal.h:14:10: fatal error: 'url/mojo/origin.mojom-internal.h' file not found
#include "url/mojo/origin.mojom-internal.h"

recipe engine's issue:
https://build.chromium.org/p/tryserver.chromium.android/builders/android_clang_dbg_recipe/builds/42038/steps/compile%20%28with%20patch%29/logs/stdio
https://build.chromium.org/p/tryserver.chromium.android/builders/android_clang_dbg_recipe/builds/42047/steps/compile%20%28with%20patch%29/logs/stdio
https://build.chromium.org/p/tryserver.chromium.android/builders/android_clang_dbg_recipe/builds/42049/steps/compile%20%28with%20patch%29/logs/stdio
[E 2016-03-29T14:21:09.495-07:00 3387 main.go:208] Failed during execution.                    {"error":"failed to run processor: read |0: bad file descriptor"}
[E 2016-03-29T14:21:09.604-07:00 3374 subcommand_run.go:262] Command failed.                             {"exitStatus":251}
[I 2016-03-29T14:21:09.674-07:00 3374 main.go:335] Terminating.                                {"returnCode":251}
WARNING:annotated_run:Could not bootstrap LogDog: LogDog Error (251)
INFO:annotated_run:Not using LogDog. Invoking `recipes.py` directly.
INFO:root:Freshening repository /b/build/scripts/slave/.recipe_deps/depot_tools
INFO:root:['git', 'reset', '-q', '--hard', '32b9f1cb57654fd28b515d60dd190cd17ee4e6a2'] (in /b/build/scripts/slave/.recipe_deps/depot_tools)
INFO:root:Freshening repository /b/build/scripts/slave/.recipe_deps/recipe_engine
INFO:root:['git', 'reset', '-q', '--hard', '3f3b7745bcc98cdcb2ae919660fd8974a5788c86'] (in /b/build/scripts/slave/.recipe_deps/recipe_engine)
INFO:root:Freshening repository /b/build/scripts/slave/.recipe_deps/recipe_engine
INFO:root:['git', 'reset', '-q', '--hard', '3f3b7745bcc98cdcb2ae919660fd8974a5788c86'] (in /b/build/scripts/slave/.recipe_deps/recipe_engine)
Traceback (most recent call last):
  File "/b/build/scripts/slave/.recipe_deps/recipe_engine/recipes.py", line 396, in <module>
    sys.exit(main())
  File "/b/build/scripts/slave/.recipe_deps/recipe_engine/recipes.py", line 366, in main
    return run(package_deps, args)
  File "/b/build/scripts/slave/.recipe_deps/recipe_engine/recipes.py", line 112, in run
    properties = get_properties_from_file(args.properties_file)
  File "/b/build/scripts/slave/.recipe_deps/recipe_engine/recipes.py", line 97, in get_properties_from_file
    properties_file = sys.stdin if filename == '-' else open(filename)
IOError: [Errno 2] No such file or directory: '/b/build/slave/android_clang_dbg_recipe/build/.recipe_runtime/tmpp0GE52/recipe_properties.json'

It seems that recent flakes come from issues of recipes.py (#18).

#18 was caused by a bug in a tool that I rolled out. I have since reverted the rollout, so it should not happen anymore.

Detected 23 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

I just checked several builds reported in #23.
Most of failures on compile step seems to be caused by:
Failing build because ninja reported work to do.


exceptions in compile step could be related to goma:
interrupt Connection to the other side was lost in a non-clean fashion.
https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_ng/builds/196047

command timed out: 2400 seconds without output, attempting to kill
(not sure why it did not show anything for 2400 seconds after FAILED)
https://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_chromeos_rel_ng/builds/188227/steps/compile%20%28with%20patch%29/logs/stdio

Anyway, majority of this flakiness cause seems not be goma but ninja.

Detected 59 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 4 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 3 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

I just checked last 6.
two of them are initial ping failure.

got 502 during the build...
https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_x64_rel_ng/builds/190798/steps/compile%20%28with%20patch%29/logs/stdio

network error continued for long time
https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/46553/steps/compile%20%28with%20patch%29/logs/stdio

build script issue?
https://build.chromium.org/p/tryserver.chromium.win/builders/win_chromium_rel_ng/builds/197677/steps/compile%20%28with%20patch%29/logs/stdio

Network was a bit flaky?

Detected 3 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 16 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 10 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 4 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

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

commit 463571701945e3c3b9210ccd88a1be4823d2584a
Author: yyanagisawa@chromium.org <yyanagisawa@chromium.org>
Date: Fri Apr 08 02:59:14 2016

Remove GOMA_PING_TIMEOUT_SEC and GOMA_PING_RETRY_INTERVAL.

Since large enough value are set by default from goma client version
103, we do not need to set them here.

BUG= 595816 

Review URL: https://codereview.chromium.org/1868603005

git-svn-id: svn://svn.chromium.org/chrome/trunk/tools/build@299788 0039d316-1c4b-4281-b951-d872f2087c98

[modify] https://crrev.com/463571701945e3c3b9210ccd88a1be4823d2584a/scripts/slave/compile.py

Detected 8 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Flakes #32 seems to come from config without #31 change because its timeout sec is 30 sec.
However, now goma compiler_proxy retries ping for 6 times with 10 seconds interval.  It actually wait initial ping for the 60 seconds.

It should be better for goma to treat such a case infra error, and make buildbot master or so to choose yet another buildslave.

What do you think?

Detected 4 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 9 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 8 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Removing this ticket from the trooper queue.

Detected 7 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

most of recent ping timeout/failure was on ccompute?
not so stable in GCE network?

Detected 3 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 4 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 101 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 105 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 3 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 7 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 7 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 35 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 9 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 3 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

Detected 9 new flakes for test/step "compile (with patch)". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyHwsSBUZsYWtlIhRjb21waWxlICh3aXRoIHBhdGNoKQw. This message was posted automatically by the chromium-try-flakes app. Since flakiness is ongoing, the issue was moved back into Trooper Bug Queue (unless already there).

The most recent iterations of this have been because of subprocess42 conversion (610041), which is fixed by now.

we haven't received flakiness report since May 3.
can we close this bug?

I think so.
flakiness used to occur failure of initial ping.  However, we rarely see that these days.

I think so, too.