[test-suite] Install LNT using requirements file #608
Conversation
Instead of "setup.py develop". Fixes llvm/llvm-lnt#76. The new process is tested in CI so we can catch problems before they get to the buildbots. The bots only use the client so I've used that specific requirement file as suggested. The requirement file has an entry ".". This means "install the package defined in the current directory". "current" means the current working directory, not the directory the requirement file is in. This is handled by running the install command from within the LNT checkout. LNT will still be installed in the sandbox as expected.
|
Note that while this might not be the final way we want to install |
|
Merging to try to make progress on the LNT side. |
Be aware that this does not propogate to the bots right away. The master needs to be restarted before that happens. I'll ask Galina for a restart. You can check the steps of one of the bots like https://lab.llvm.org/buildbot/#/builders/17 to see if the change has been applied yet. |
|
Actually I'll ask once I confirm whether setuptools is still needed. |
|
We need setuptools as long as we are using setup.py I think. Newer versions of virtualenv do not install it by default. I've requested a restart. |
|
Bots have been updated. |
2 participants
Instead of "setup.py develop". Fixes llvm/llvm-lnt#76.
The new process is tested in CI so we can catch problems before they get to the buildbots.
https://llvm.org/docs/lnt/quickstart.html#installation
The bots only use the client so I've used that specific requirement file as suggested.
The requirement file has an entry ".". This means "install the package defined in the current directory". "current" means the current working directory, not the directory the requirement file is in.
This is handled by running the install command from within the LNT checkout. LNT will still be installed in the sandbox as expected.