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

minimal download breaks stable-status #8385

Closed
aherrmann opened this issue May 17, 2019 · 0 comments

Comments

Projects
None yet
3 participants
@aherrmann
Copy link
Contributor

commented May 17, 2019

Description of the problem:

The minimal download flags

build --experimental_inmemory_jdeps_files
build --experimental_inmemory_dotd_files
build --experimental_remote_download_outputs=minimal

on Bazel 0.25.2 seem to break the stable-status feature. I'm observing the following error

ERROR: Failed to run workspace status command bazel_tools/workspace_status.sh: /home/aj/.cache/bazel/_bazel_aj/10d2a8446c92e5dc655eb18c02f185fb/execroot/com_github_digital_asset_daml/bazel-out/stable-status.txt (Permission denied)

(Forcefully removing the file temporarily resolves the problem.)

Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Checkout digital-asset/daml@f6642ff and execute the following commands

. .envrc
bazel run //:buildifier
echo >> WORKSPACE
git add WORKSPACE
git commit -m 'dummy change'
bazel run //:buildifier

What operating system are you running Bazel on?

OpenSUSE Tumbleweed 20190510

What's the output of bazel info release?

release 0.25.2- (@non-git)

If bazel info release returns "development version" or "(@non-git)", tell us how you built Bazel.

Using Nix

Any other information, logs, or outputs that you want to share?

Not sure if related or not, but bazel run seems to be not working on some targets when using minimal downloads. E.g. on the same commit as above

$ bazel run damlc
...
ERROR: Non-existent or non-executable /home/aj/.cache/bazel/_bazel_aj/10d2a8446c92e5dc655eb18c02f185fb/execroot/com_github_digital_asset_daml/bazel

@buchgr buchgr removed the untriaged label May 22, 2019

buchgr added a commit to buchgr/bazel that referenced this issue Jun 19, 2019

remote: output files need to be writable. Fixes bazelbuild#8385
They need to be (over)writable by Bazel actions.

@bazel-io bazel-io closed this in c7e8a92 Jun 19, 2019

buchgr added a commit to buchgr/bazel that referenced this issue Jun 23, 2019

remote: output files need to be writable. Fixes bazelbuild#8385
They need to be (over)writable by Bazel actions.

Closes bazelbuild#8678.

PiperOrigin-RevId: 254017428

siberex added a commit to siberex/bazel that referenced this issue Jul 4, 2019

remote: output files need to be writable. Fixes bazelbuild#8385
They need to be (over)writable by Bazel actions.

Closes bazelbuild#8678.

PiperOrigin-RevId: 254017428

irengrig added a commit to irengrig/bazel that referenced this issue Jul 15, 2019

remote: output files need to be writable. Fixes bazelbuild#8385
They need to be (over)writable by Bazel actions.

Closes bazelbuild#8678.

PiperOrigin-RevId: 254017428
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.