maruel@ (or one of the cc'ed folks): can you look at these failures? They seem pretty unlikely (hence, odd).

https://build.chromium.org/p/tryserver.chromium.android/builders/linux_android_rel_ng/builds/62747/steps/isolate%20tests%20%282%29/logs/stdio
isolate: lstat /b/build/slave/android/build/src/out/Release/gen/out/Release/icudtl.dat: no such file or directory

maybe a missing dependency?

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

Still seems flaky and is reported to the Chromium sheriff.
Removing label again.

I think probably there's something wrong in the "mb isolate" step.

"out/Release/gen/out/Release/icudtl.dat" should just be: "out/Release/icudtl.dat"

Also note this bot is still on GYP, but will be switched to GN today / tomorrow, which possibly might make this problem go away?

> Also note this bot is still on GYP, but will be switched to GN today / tomorrow, which possibly might make this problem go away?

agrieve@, that sounds lovely to me. Let's not fix it if it's not needed. :)

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

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

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

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

Detected 3 new flakes for test/step "isolate". To see the actual flakes, please visit https://chromium-try-flakes.appspot.com/all_flake_occurrences?key=ahVzfmNocm9taXVtLXRyeS1mbGFrZXNyEgsSBUZsYWtlIgdpc29sYXRlDA. This message was posted automatically by the chromium-try-flakes app.

 Issue 647744  has been merged into this issue.

Re-opening because its still flaky on the bots ( issue 647744 ).

stip@, Comment #7 suggests that this should be fixed. Should it be? Feel free to archive again if that makes more sense.

There are two issues: when there are missing files, the client code hangs.

So there's the actual problem: "no such file or directory". That's likely due a BUILD.gn deps misconfiguration.

and there's a hang in case of user error. While the later is annoying, it'll be fixed only after issue 648352 is resolved; as we're running 6 months old code at that point.