{"action":"opened","issue":{"url":"https://api.github.com/repos/bazelbuild/bazel/issues/4082","repository_url":"https://api.github.com/repos/bazelbuild/bazel","labels_url":"https://api.github.com/repos/bazelbuild/bazel/issues/4082/labels{/name}","comments_url":"https://api.github.com/repos/bazelbuild/bazel/issues/4082/comments","events_url":"https://api.github.com/repos/bazelbuild/bazel/issues/4082/events","html_url":"https://github.com/bazelbuild/bazel/issues/4082","id":273490471,"number":4082,"title":"Bazel mis-interprets errors while executing tests remotely","user":{"login":"EricBurnett","id":201307,"avatar_url":"https://avatars1.githubusercontent.com/u/201307?v=4","gravatar_id":"","url":"https://api.github.com/users/EricBurnett","html_url":"https://github.com/EricBurnett","followers_url":"https://api.github.com/users/EricBurnett/followers","following_url":"https://api.github.com/users/EricBurnett/following{/other_user}","gists_url":"https://api.github.com/users/EricBurnett/gists{/gist_id}","starred_url":"https://api.github.com/users/EricBurnett/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/EricBurnett/subscriptions","organizations_url":"https://api.github.com/users/EricBurnett/orgs","repos_url":"https://api.github.com/users/EricBurnett/repos","events_url":"https://api.github.com/users/EricBurnett/events{/privacy}","received_events_url":"https://api.github.com/users/EricBurnett/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-11-13T16:23:41Z","updated_at":"2017-11-13T16:23:41Z","closed_at":null,"author_association":"NONE","body":"### Description of the problem / feature request / question:\r\n\r\nWhen test execution fails for unexpected reasons, the error is re-thrown as a SpawnExecException: https://github.com/bazelbuild/bazel/blob/57a2ad72d954b6986fbc857d44694ffb516cdb1b/src/main/java/com/google/devtools/build/lib/remote/RemoteSpawnRunner.java#L223-L248\r\n\r\nThe test strategy catches this and translates it into a test failure:\r\n\r\nhttps://github.com/bazelbuild/bazel/blob/57a2ad72d954b6986fbc857d44694ffb516cdb1b/src/main/java/com/google/devtools/build/lib/exec/StandaloneTestStrategy.java#L369-L376\r\n\r\nThe net effect of this is that all execution failures during the running of tests are reported to the user as test failures instead of as the underlying issue, which in turn masks the underlying issues.\r\n\r\n### If possible, provide a minimal example to reproduce the problem:\r\n\r\nNo repro provided, but it could probably be forced by injecting an IOException somewhere like https://github.com/bazelbuild/bazel/blob/57a2ad72d954b6986fbc857d44694ffb516cdb1b/src/main/java/com/google/devtools/build/lib/remote/RemoteSpawnRunner.java#L139 when the action being run is a test.\r\n\r\n### Environment info\r\n* Operating System:\r\n\r\nTested on linux; should be OS agnostic.\r\n\r\n* Bazel version (output of `bazel info release`):\r\n\r\nHEAD\r\n\r\n* If `bazel info release` returns \"development version\" or \"(@non-git)\", please tell us what source tree you compiled Bazel from; git commit hash is appreciated (`git rev-parse HEAD`):\r\n\r\nSometime later than c35fe50e9210d10aba2fb578e46d8203c8451adb (built from internal, so not exactly known)."}}
{"actor":{"display_login":"EricBurnett"}}