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
env_vars not transferring successfully on debian-gcc-devel platform #174
Comments
Are you sure they are not set? Possibly they are set, and just not printed in the logs? |
The env vars are actually set, but your env var is called But there is still a bug in R-hub, because it seems that it escapes the |
The extra backslashes are coming from here: https://github.com/r-hub/rhub-backend/blob/50254305a45891327e0e869f4b40339cc2d483d7/lib/builder.js#L5 I don't think we need to quote anything for Linux, because Docker takes the environment variables literally. We might need to quote for the other OSes, though. :( |
OK, this is fixed on Linux and Windows: I still need to double check the Windows one, because we might need to quote sg, actually. I also need to check other platforms. |
Thanks Gabor. Yes, this was my faulty syntax. It appears to be transferring environmental variables fine and the runs as expected on debian-gcc-devel replicating the output from the CRAN checks on this system, even though the environmental variables do not print in the log. |
env_vars not transferring successfully on debian-gcc-devel platform but are OK on windows.
This seems to perhaps be a similar issue as encountered earlier this year on solaris? (#105).
On debian:
On windows:
The text was updated successfully, but these errors were encountered: