-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
5.0rc1: Remote cache read failure "java.lang.RuntimeException: java.io.IOException: file.tmp (Not a directory)" #14228
Comments
According to the stack trace:
it calls into NativePosixFiles.openWrite() which calls According to the doc, |
Might related #6393. |
@brentleyjones Is that possible to create a repro? |
It's weird, the parent directories are actually created before the download. |
It was on CI. All I can think of is the directories failed to be created, because of low disk space. |
We're seeing what I think is the same issue with bazel 5.1.1:
Unfortunately I think we're hiding the full stack trace https://dev.azure.com/cncf/envoy/_build/results?buildId=106443&view=logs&jobId=fa3d3e18-6969-5713-c3e7-3581195704fd&j=fa3d3e18-6969-5713-c3e7-3581195704fd&t=ba370bef-ca49-52f5-0c93-7c0c0f27c465 (this log will probably rotate) |
Hit this bug today when trying to use
so that I could do GoLinking locally while doing the rest of my build on RBE. Not sure if that information is helpful |
A lot of things have changed since 5. Please reopen if it's still happening. |
Description of the problem / feature request:
We encountered an error where bazel fails to read from the remote cache because it throws an execution locally. Seems to be from this code path: cff2ea5#diff-c0c72bba110eca25447686392b1f265feabe77c8a53ed7387f70f82bcdaba441R112.
LinuxMain.swift
is single file output from agenrule
.Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
I don't know of one.
What operating system are you running Bazel on?
macOS 11.6.1
What's the output of
bazel info release
?release 5.0.0rc1
The text was updated successfully, but these errors were encountered: