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

bazel_rules_test broken at HEAD #5607

Closed
c-parsons opened this issue Jul 16, 2018 · 3 comments
Closed

bazel_rules_test broken at HEAD #5607

c-parsons opened this issue Jul 16, 2018 · 3 comments
Assignees
Labels
breakage P1 I'll work on this now. (Assignee required)

Comments

@c-parsons
Copy link
Contributor

Description of the problem / feature request:

Bazel with downstream projects: "Bazel Remote Execution" is broken at HEAD.
Example run:
https://buildkite.com/bazel/bazel-with-downstream-projects-bazel/builds/341#b1274694-06b0-4b16-8ff9-d967073f0efe

Relevant snip:

** test_genrule_default_env ****************************************************
/b/s/w/ir/run/bazel-out/k8-fastbuild/bin/src/test/shell/bazel/bazel_rules_test.runfiles/io_bazel/src/test/shell/bazel/bazel_rules_test: line 295: TMPDIR: unbound variable

I believe this was caused by f814454

we probably just need to not assume TMPDIR is set, which was the previous state before that change

@c-parsons c-parsons added P1 I'll work on this now. (Assignee required) breakage labels Jul 16, 2018
@laszlocsomor
Copy link
Contributor

Taking a look.

@laszlocsomor
Copy link
Contributor

we probably just need to not assume TMPDIR is set, which was the previous state before that change

$TMPDIR should always be set, see

However, it seems to be unset here. Let me take a look as to why.

@laszlocsomor
Copy link
Contributor

Ah, because we're talking about remote execution, not local ones. I don't know how the remote executor sets up envvars, so let me add code that allows an empty TMPDIR.

laszlocsomor added a commit to laszlocsomor/bazel that referenced this issue Jul 17, 2018
Allow the `$TMPDIR` to be empty in
//src/test/shell/bazel:bazel_rules_test.

This used to be the case before commit
bazelbuild@f814454

Bazel only guarantees to set TMPDIR for locally
executed tests, but not (to my knowledge) for
remote execution.

Fixes bazelbuild#5607

Change-Id: I2e97c13d137f94c7f668b7a6c7fc5020a19e4a0b
werkt pushed a commit to werkt/bazel that referenced this issue Aug 2, 2018
Allow the `$TMPDIR` to be empty in
//src/test/shell/bazel:bazel_rules_test.

This used to be the case before commit
bazelbuild@f814454

Bazel only guarantees to set TMPDIR for locally
executed tests, but not (to my knowledge) for
remote execution.

Fixes bazelbuild#5607

Change-Id: I2e97c13d137f94c7f668b7a6c7fc5020a19e4a0b

Closes bazelbuild#5610.

Change-Id: I2e97c13d137f94c7f668b7a6c7fc5020a19e4a0b
PiperOrigin-RevId: 205039105
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breakage P1 I'll work on this now. (Assignee required)
Projects
None yet
Development

No branches or pull requests

2 participants