-
Notifications
You must be signed in to change notification settings - Fork 15
Fails to handle environment variables changes from build.rs #137
Comments
This is an interesting case, the solution would be whenever something like Right now The problem is how to get this info outside of |
I discovered this issue with the following use case: including the current commit-id in a I was wondering if including the |
If that helps, the output of Actually, I don't think we need to care about |
Does your build script create any files or update any file's content? |
I do not create any file. But as previously stated, cargo does save its output into a file. |
@montekki: If the path is predictable, we could simply add this to the cached paths if the manifest contains a |
I simplified a bit, its more like I guess that |
@drahnr
And parse all the necessary outputs. the |
Hello. Is there any update on this issue? Otherwise, I may try to fix this in the days to come |
Hmmm, well I'm not sure I'll have enough free time to see this after all. I'll have a try but maybe I won't be able to complete this fix :-( If that helps, I'm sharing the workaround that currently works (at least for my own needs): all the environment-related behaviour of my |
There were some slowdowns related to the invasion of Russia into the Ukraine. If you can create a PR, even if it's just a rough draft, would be helpful. |
Issue
When defining environment variables in a build script within a workspace, they are not correctly handle by the cache. This is visible in non incremental build (in release with default config).
Setup:
Minimal reproducer
cachepot-env-vars.tar.gz
The text was updated successfully, but these errors were encountered: