Closed mforbes closed 2 years ago
BTW: I could not run all of the tests: Things stalled at "anaconda_project/internal/test/test_conda_api.py::test_resolve_dependencies_with_actual_conda_other_platforms" with this step taking close to an hour. (Mac OS X 10.14.6).
I also failed anaconda_project/test/test_prepare.py::test_default_to_system_environ
because my default ~/.condarc
used auto_stack: 1
and I start with a base environment active, which caused some path changing issues. This may relate to #336 where better control over global conda configuration may be needed for reproducibility.
Can we easily run tests with a repeatable configuration? In the meantime, I will add an additional exception.
Approved!
I'll give it a try on my system with auto_stack: 1
. I've opened a new issue for it #357
Ick, I have no idea what's up with tests. I've been having trouble with the Github actions for several weeks on this repo.
Anyway, #358 has some updates to CONTRIBUTING.md, more are certainly appreciated.
This is a minimal fix for issue #355. Note: after running the tests, many pieces of code were reformatted. I did not include these changes to keep the noise at a minimum. Should I first commit a
lint
revision with the reformatted code, then rebase my changes on top? (If so, this could be spelled out explicitly inCONTRIBUTING.md
. Let me know and I can include in a future documentation PR.)I am not comfortable enough with the project's CI to figure out why this error was not caught during CI. Does the CI provision from an environment that uses
conda/meta.yml
? If so, we might like to add some CI provisioning fromenvironment.yml
directly (for developers) and fromsetup.py
(for people who install frompip
).