Skip to content

Known broken explanation for test_init_dev_and_NoBaseEnvironmentError on macos #11128

@jaimergp

Description

@jaimergp

Checklist

  • I added a descriptive title
  • I searched for other issues and couldn't find a solution or duplication
  • I already searched in Google and didn't find any good information or help
  • I looked at the docs and didn't see anything to help

What happened?

This test fails on our macOS CI possibly due to how we are activating the conda installation there. It passes on Windows and Linux, so we should look into how those are done.

The gist is that this tests purposely installs old conda and python and on top of that adds the complications of initialization and development flags. Since that old conda uses #!/usr/bin/env python as the shebang, it might be getting our base installation's (instead of the testing one?) Python, which obviously points to the development conda. Instead, it should discover the test prefix Python (?) and point to the old conda. That's why the versions don't match.

If the $old_conda --version call gets replaced with $old_python -m conda --version it passes successfully.

Conda info

See CI in https://github.com/conda/conda/pull/10875

Conda config

See CI in https://github.com/conda/conda/pull/10875

Conda list

See CI in https://github.com/conda/conda/pull/10875

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    backlogissue has been triaged but has not been earmarked for any upcoming releaselocked[bot] locked due to inactivityos::macosrelevant to macOSseverity::2critical; broken functionality with an unacceptably complex workaroundsource::partnercreated by or for an Anaconda, Inc. partner companytype::bugdescribes erroneous operation, use severity::* to classify the type

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions