Make build_event_stream_test more robust

...by makeing it independent of the test executor; in particular,
do not rely on the wrapper to create the test.xml files if the test
fails to do so, and do not assume a particular name (e.g., remote
execution might decide to call the files "remote_1.xml").

Also, make the constructor of VisibilityErrorEvent public, to allow
extensions of bazel to generate visibility errors as well.

RELNOTES: None
PiperOrigin-RevId: 161087809

1 files changed, 1 insertions, 1 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/bazel/rules/VisibilityErrorEvent.java b/src/main/java/com/google/devtools/build/lib/bazel/rules/VisibilityErrorEvent.java
index a2c51a8a0f..5842a8e186 100644
--- a/src/main/java/com/google/devtools/build/lib/bazel/rules/VisibilityErrorEvent.java
+++ b/src/main/java/com/google/devtools/build/lib/bazel/rules/VisibilityErrorEvent.java
@@ -30,7 +30,7 @@ public class VisibilityErrorEvent implements BuildEventWithConfiguration {
   Label label;
   String errorMessage;
 
-  VisibilityErrorEvent(BuildConfiguration configuration, Label label, String errorMessage) {
+  public VisibilityErrorEvent(BuildConfiguration configuration, Label label, String errorMessage) {
     this.configuration = configuration;
     this.label = label;
     this.errorMessage = errorMessage;