Closed szcf-weiya closed 10 months ago
Patch coverage: 100.00%
and project coverage change: +0.06%
:tada:
Comparison is base (
79c5487
) 87.43% compared to head (fed4dbd
) 87.50%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Would be great to have a fix for this issue! Any problems with the PR? @stevengj @mkitti
Why are the Windows tests failing?
I think it is just a simple edit, and should not be related to the platform.
How can we rerun the test? (I found a way, just update my forked repo). Because I noticed the near commits also failed on Windows.
Windows failed during the installation of miniconda, so I am guessing (tried to check the documentation https://docs.conda.io/projects/conda/en/latest/user-guide/install/windows.html but failed to find related documentation) whether the error is due to the provided PREFIX folder is not empty since I created the file condarc-julia.yaml
in the package building step when (mini)conda was not yet installed.
So the updated version is to write the config file condarc-julia.yaml
after installing (mini)conda.
LGTM.
Hm, I tested half a hour ago, and turns out that the underlying issue was already fixed somehow: PyCall, PyPlot, and other dependent packages install just fine on GitHub Actions. The same action failed just two weeks ago with the ResolvePackageNotFound
error.
Not sure what changed, and where...
Probably Conda fixed their packages in the meantime? But I still feel like it is good practice not to upgrade unless the user specifically requests Conda.update()
.
The motivations come from #242 and #238, where the error "ResolvePackageNotFound: - conda==23.1.0" is thrown when conda automatically upgrades from 23.1.0 to 23.5.0.
Although I did not quite understand the real logic of the error, one simple workaround is to disable the auto-update of conda, i.e., fix its version.
On the other hand, since the package Conda.jl has already required to install the latest conda release,
https://github.com/JuliaPy/Conda.jl/blob/fe6c94c70609e6b6a8f853d72efc7d890df967e6/src/Conda.jl#L167-L179
I think the later update by
auto_update_conda
is just minor, like from 23.1.0 to 23.5.0, then disabling such minor aggressive updates should be reasonable. As a byproduct, it can save the upgrade time.