omus
commented
3 years ago The Julia 1.6 build behavior shouldn't have changed. If you remove the TimeZones package and re-add it can you reproduce the problem? Also, can you post your versioninfo()?
Closed bencottier closed 1 year ago
omus
commented
3 years ago The Julia 1.6 build behavior shouldn't have changed. If you remove the TimeZones package and re-add it can you reproduce the problem? Also, can you post your versioninfo()?
bencottier
commented
3 years ago The Julia 1.6 build behavior shouldn't have changed. If you remove the TimeZones package and re-add it can you reproduce the problem? Also, can you post your
versioninfo()?
Note the problem was originally found in an internal Invenia CI job. I reproduced it locally with fresh activate --temp environments.
But it's true that I can't reproduce the problem after removing and re-adding the package. So I guess this is a problem with Invenia's CI for 1.6.
1.6:
julia> versioninfo()
Julia Version 1.6.0
Commit f9720dc2eb (2021-03-24 12:55 UTC)
Platform Info:
OS: macOS (x86_64-apple-darwin19.6.0)
CPU: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-11.0.1 (ORCJIT, skylake)
Environment:
JULIA_EDITOR = code1.5:
julia> versioninfo()
Julia Version 1.5.2
Commit 539f3ce943 (2020-09-23 23:17 UTC)
Platform Info:
OS: macOS (x86_64-apple-darwin18.7.0)
CPU: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-9.0.1 (ORCJIT, skylake)
Environment:
JULIA_EDITOR = codeIt's possible that a network issue resulted in the build step failing.
Thanks for mentioning activate --temp as I can also reproduce the problem. This does seem to be a Pkg.jl issue but I'll need to investigate further.
iamed2
commented
3 years ago Could the files being created by the build process be being removed by Pkg? I know they're moving towards using stuff like https://github.com/JuliaPackaging/Scratch.jl, maybe that's because there's some problem with package-local, package-managed files in 1.6?
kafisatz
commented
3 years ago Updating to 1.6, I ran into this "issue" (the fix is straightforward as the error message is very informative) as well on two different computers. I do not think this is related to a network issue.
rikhuijzer
commented
3 years ago I also ran into this issue in two different contexts.
omus
commented
3 years ago I'll try to get this fixed tomorrow
rikhuijzer
commented
3 years ago Suddenly, it now works when building Heroku on Julia 1.6.1.
I notice that the TimeZones versions differ. So, maybe this has already been fixed?
omus
commented
3 years ago I'm not having any luck reproducing the problem today. The failures previously seemed limited to Julia 1.6.0 and TimeZones 1.5.3.
I notice that the TimeZones versions differ. So, maybe this has already been fixed?
The new 1.5.4 release mainly adds tz2021a as the default release. The only way I could see this fixing the issue is if people are using JULIA_TZ_VERSION=latest with 1.5.3.
I'll take another run at this but I may need more information.
iamed2
commented
2 years ago We're still observing this with Julia 1.6.5 and TimeZones 1.7.0. It's hard to predict when it will happen but it seems to happen periodically on users' machines (the issue is mitigated in CI where we call Pkg.build() explicitly).
omus
commented
1 year ago In PR https://github.com/JuliaTime/TimeZones.jl/pull/441 the deps/build.jl was removed so this is no longer an issue. Included in TimeZones release 1.12.
It seems that Julia 1.6 does not build the package automatically. Is this a bug?
Julia 1.6:
Julia 1.5: