Dmytro Kashyn
Dmytro Kashyn
Based on it feels like sources might be a factor here. I'll keep an eye on this! `JUnitCore` is clickable now for me but some others don't.
@mai93 I'm able to repro it in Gateway Here is local where issue not happening for the very same project AND test here is Gateway not sure what to check......
[scratch_45.txt](https://github.com/bazelbuild/bazel/files/14544036/scratch_45.txt) here is the thread dump of Bazel server when this is happening
Let us try out to remove this!
Should it TO even with `keep alive` though?
Still happening even without `keep alive` ``` cat .bazelrc |grep keep #common:remote --experimental_remote_execution_keepalive ``` ``` [65,553 / 65,563] .... 1966s remote ```
[bazel_server_dump.txt](https://github.com/bazelbuild/bazel/files/14562250/bazel_server_dump.txt) another dump with `keep_alive` off
We are only starting to experiment with RBE so we don't have pre-7.0 baseline, unfortunately. Regarding remote server doing something: I've checked BuildFarm workers and there were no active tasks...
BEP is async and this is confirmed to be working properly in an async way starting from 7.0 ``` build --bes_backend=grpcs://... build --bes_upload_mode=fully_async build --build_event_text_file_upload_mode=fully_async build --build_event_binary_file_upload_mode=fully_async build --build_event_json_file_upload_mode=fully_async ```...
I'll try to repro it without BES/BEP in next couple of days. The issue still should be fixed though even if this is because of BEP/BES ;) We specifically asking...