Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

List of Bazel shell tests that fail on RBE #5234

Closed
buchgr opened this issue May 22, 2018 · 1 comment
Closed

List of Bazel shell tests that fail on RBE #5234

buchgr opened this issue May 22, 2018 · 1 comment
Assignees
Labels
P2 We'll consider working on this in future. (Assignee optional) team-Remote-Exec Issues and PRs for the Execution (Remote) team

Comments

@buchgr
Copy link
Contributor

buchgr commented May 22, 2018

I have enabled //src/test/shell/bazel/... on our Remote Execution pipeline using the latest bazel-toolchain release: https://github.com/bazelbuild/bazel-toolchains/releases

The following tests don't work, because of some tools not being installed in the docker container:

//src/test/shell/bazel/android/...
Not running Android tests due to lack of an Android SDK.

//src/test/shell:bazel/bazel_execute_testlog
/usr/bin/less: No such file or directory

//src/test/shell/bazel:bazel_repository_cache_test
remote_helpers.sh: line 27: nc: command not found

//src/test/shell/bazel:bazel_spawnstats_test
ERROR: 'linux-sandbox' is an invalid value for linux-sandbox spawn strategy. Valid values are: local, processwrapper-sandbox, remote, sandboxed, standalone, worker

//src/test/shell/bazel:external_integration_test
Failed to fetch Maven dependency: Could not transfer artifact com.example.carnivore:carnivore:jar:1.23 from/to endangered (http://127.0.0.1:36142/): Connection refused (Connection refused) and referenced by '//external:mongoose'

nc: command not found

//src/test/shell/bazel:external_patching_test
bash: patch: command not found

//src/test/shell/bazel:maven_test
nc: command not found

//src/test/shell/integration:java_integration_test
/b/s/w/ir/run/bazel-out/k8-fastbuild/bin/src/test/shell/integration/java_integration_test.runfiles/io_bazel/usr/lib/jvm/java-8-openjdk-amd64/bin/java: No such file or directory

//third_party/ijar/...
java.io.IOError: java.io.FileNotFoundException: Can't find langtools jar: /b/s/w/ir/run/bazel-out/k8-fastbuild/bin/third_party/ijar/test/IjarTests.runfiles/run/third_party/java/jdk/langtools/javac-9+181-r4173-1.jar

@buchgr buchgr added this to the Remote Execution milestone May 22, 2018
@buchgr buchgr self-assigned this May 22, 2018
@buchgr buchgr added area-EngProd Bazel CI, infrastructure, bootstrapping, release, and distribution tooling team-Remote-Exec Issues and PRs for the Execution (Remote) team P2 We'll consider working on this in future. (Assignee optional) and removed category: remote execution / caching labels Feb 5, 2019
@dslomov dslomov removed the area-EngProd Bazel CI, infrastructure, bootstrapping, release, and distribution tooling label Feb 15, 2019
@dslomov
Copy link
Contributor

dslomov commented Feb 15, 2019

Please do not assign issues to more than one team.

@buchgr buchgr removed this from the Remote Execution milestone Mar 13, 2019
@buchgr buchgr closed this as completed Apr 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P2 We'll consider working on this in future. (Assignee optional) team-Remote-Exec Issues and PRs for the Execution (Remote) team
Projects
None yet
Development

No branches or pull requests

3 participants