Skip to content

LNT client setup using setup.py should be tested in CI/Actions #68

@DavidSpickett

Description

@DavidSpickett

Linaro has a bunch of buildbots that do the following commands when running llvm-test-suite using LNT:

rm -rf sandbox
virtualenv --python=python3 sandbox
sandbox/bin/python -m pip install setuptools
sandbox/bin/python llvm-lnt/setup.py develop

This process has been broken a couple of times in the last few days as versions of dependencies get changed. Which is a good and overdue change, but we could verify it earlier.

We should:

  • Run this use case here in CI to check the setup.py command works for client use (and server?).
  • Consider whether we want to keep setup.py as the setup method, for clients or just generally. I don't personally care what we choose as long as it's not been removed from current Python versions.

If making changes to the buildbot's configurations would help, I can do that. At least for Linaro, we are using Python 3.10 at the moment. Most other buildbots are not using LNT, and if they really needed to stay on old Python, you can run llvm-test-suite just using cmake and ninja instead.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions