Skip to content

Enhance offline testing #8970

Open
Open
@mgorny

Description

@mgorny

I think uv's getting quite mature at this point. Unfortunately, the test suite is still largely dependent on accessing pypi.org online. FWICS, on top of 65e2f95 there are ~1250 tests skipped with it disabled, i.e. only ~10% of the test suite is run without it, and I suppose a lot of important features aren't tested.

Other points aside, the problem with the current approach to online testing is that it's very fragile to changes to PyPI packages. In the past, I've seen more than once that the tests were already failing within 24 hours from publishing a new version. While many of these failures can be trivially resolved, this effectively that means uv keeps being a rapidly moving target. As such, we can't really mark it stable in Gentoo — our rough guideline for the Python ecosystem is to mark stable after 2 weeks with no major issues, and by then the test suite must still be passing.

Could you please consider a long-term goal of making the tests less dependent on third-party services and more offline? Some Python packages run their own "PyPI server" (i.e. pypiserver PyPI package) for that purpose — I suppose a similar solution would be the cleanest approach to offline testing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    testingInternal testing of behavior

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions