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
Unrecoverable error while evaluating node 'ActionLookupData{...}' #6170
Comments
So one thing I found while debugging is that the assertion that's failing (code here) is due to a directory being in the list of
The code doesn't handle that case so I assume it doesn't expect directories to be passed as source artifacts? Is that by design? Is the bug that the directory is there or is the bug that the code isn't handling directories here? |
Lo and behold... the rules's
|
Looks like a legit bug. Sergio, David, how would you resolve this? Not allow directory entries in |
The fact that bazel allows a directory in a We do have execution-time validation in the tools, but this error is way before the tool gets executed, so there's no action we can do right now. I would bring this up with the Starlark team instead and get to a consensus whether directories are valid targets, and if so, to fix |
@laurentlb can you clarify that this is a bug with how bazel accepts directories as inputs to |
I have no background to offer, (the implementation of That is:
... so i'll just offer my take: It seems like a bug. This will need some further investigation -- how usable are the |
We hit a similar issue to this:
|
The core error doesn't seem related to the directory issue, so maybe I should create a separate issue? |
Indeed, please file a separate issue. That looks different enough where I think it needs separate investigation :) (and anything you can offer in the realm of repro instructions would be appreciated) |
Actually looks like this case might be fixed, I'll tack on to #6136 if needed |
I'm running into this issue as well, where |
Thank you for contributing to the Bazel repository! This issue has been marked as stale since it has not had any activity in the last 3 years. It will be closed in the next 14 days unless any other activity occurs or one of the following labels is added: "not stale", "awaiting-bazeler". Please reach out to the triage team ( |
This issue has been automatically closed due to inactivity. If you're still interested in pursuing this, please reach out to the triage team ( |
Following up from #5296:
I'm seeing this error with Bazel's master, 0.17.1 and the 0.18.0 branch while building an iOS application using rules_apple 0.7.0, rules_swift at 7bbcf9584613169cda709b9c217f5ac29cc5a089 and a remote-cache.
It's reproducible and I can debug. However, I can't share the app.
It only happens when the remote cache is enabled.
The text was updated successfully, but these errors were encountered: