Version 0.4.4 with CI/CD setup
Don't publish to TestPyPI on pushes to main

It turns out that it was complicated to set up because nobody does it,
and in fact it still doesn't work due to the tagging scheme used by
setuptools-scm. That could be worked around, but since that's not the
intended usage of TestPyPI, don't.

https://github.com/pypa/packaging-problems/issues/844 explains that the
setup guide is misleading since TestPyPI is not intended to be used for
pushes from a CI pipeline.

Hence, only push to TestPyPI on tag creation. This makes me question
the value of TestPyPI in the context of CI/CD, but whatever.
1 file changed
tree: 082155a7c1c40c320f89dd51395094e73ee6a8cf
  1. .github/
  2. deployment/
  3. docker/
  4. docs/
  5. examples/
  6. lnt/
  7. schemas/
  8. tests/
  9. utils/
  10. .gitignore
  11. docker-compose.yml
  12. Dockerfile
  13. LICENSE.TXT
  14. MANIFEST.in
  15. Procfile
  16. pyproject.toml
  17. README.md
  18. requirements.client.txt
  19. requirements.server.txt
  20. requirements.txt
README.md

LNT: LLVM Nightly Test Infrastructure

About

LNT is an infrastructure for performance testing. The software itself consists of two main parts, a web application for accessing and visualizing performance data, and command line utilities to allow users to generate and submit test results to the server.

The package was originally written for use in testing LLVM compiler technologies, but is designed to be usable for the performance testing of any software.

Documentation

The official LNT documentation is available online at: https://llvm.org/docs/lnt

Source

The LNT source is available in the llvm-lnt repository: https://github.com/llvm/llvm-lnt

Contributing

To get started, please look at the Developer Guide in the official documentation.