//src/test/shell/bazel:rule_test_test fails on CI (OSX)

[buchgr]

The test test_local_rule_test_in_root failed on OSX with

Server terminated abruptly (error code: 14, error message: '', log file: '...')

The error code maps to gRPC's UNAVAILABLE code, so this actually looks like the gRPC server crashed.

http://ci.bazel.io/job/Gerrit-bazel-tests/639/BAZEL_VERSION=latest,PLATFORM_NAME=darwin-x86_64/testReport/junit/(root)/(empty)/test_local_rule_test_in_root/

[buchgr]

cc @damienmg

[damienmg]

Probably a flake. /cc @lberki because gRPC.

[damienmg]

This is irreproducible because we don't have access to the jvm.log file. We should probably output it if we are running under test.

Assigning to Lukacs to evaluate.

[lberki]

Without a jvm.log there isn't a lot I can do.

[damienmg]

I was actually asking for idea on what we could do to get the lot if that happens again. Can we print it in certain case instead of just printing the file path?

…

On Fri, May 5, 2017, 9:15 AM lberki ***@***.***> wrote: Without a jvm.log there isn't a lot I can do. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#2939 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADjHf_xySgH6NxGU4ZZyjSMtYR8SuQJ_ks5r2syJgaJpZM4NQb93> .

[damienmg]

As discussed offline, in our test framework we should cat the jvm.log if we get that error.

[haxorz]

fyi, this sounds possibly like a bug introduced by 3e5edaf. it was diagnosed by @ericfelly internally. that commit was reverted in c4f271d. @philwo fixed the underlying issue recently with 67cea8f (see the third line of the commit message for the bug).

given that i'm pretty sure bazel.io was affected by another bug with the initial commit (see #2985), it's likely you're also being affected by this bug.