This is an automated email from the git hooks/post-receive script.

unknown user pushed a change to branch users/amara/generalize-build-dir in repository llvm-lnt.

discards ff82019 Generalize --build-dir to work with all build modes discards 064aefe Add test and some fixes discards ba9592b Add interleaved benchmark execution for test-suite adds 1d9ce46 Fix mypy assertion error in upgrade_0_to_1 (#111) adds 3e71f65 Replace usage of "pipes" with shlex. (#112) adds 2b1e74f Add REQUIRES postgres to tests/utils/installation.shtest test (#113) adds 0eb6c92 Officially support Python 3.13 and 3.14, and add CI for them (#87) adds 0367895 [NFC] Reindent docker-entrypoint.sh with spaces adds 388d187 [NFC] Rename .yml files to .yaml for consistency adds b5dbb5c Automatically detect whether we should run the postgres tests (#114) adds fed3b58 [NFC] Create temporary DB directory after validating TEST_DIR adds d70af04 Update gunicorn to latest version (23.0.0) (#118) adds 4819b7b Remove Procfile (#119) new e554de7 Add interleaved benchmark execution for test-suite new 98e79ce Add test and some fixes new 9503657 Generalize --build-dir to work with all build modes new cdc77a0 Merge generalize-build-dir changes new 17ed608 Rename options to --build and --exec new 8d74447 Finish --build-dir generalize

This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this:

* -- * -- B -- O -- O -- O (ff82019) \ N -- N -- N refs/heads/users/amara/generalize-build-dir (8d74447)

You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B.

Any revisions marked "omits" are not gone; other references still refer to them. Any revisions marked "discards" are gone forever.

The 6 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "adds" were already present in the repository and have only been added to this reference.

Summary of changes: ...-package.yml => build-and-publish-package.yaml} | 0 .github/workflows/tox.yaml | 9 +- Procfile | 1 - docker-compose.yml => docker-compose.yaml | 0 docker/docker-entrypoint.sh | 36 +- docs/developer_guide.rst | 8 +- lnt/server/db/migrations/upgrade_0_to_1.py | 12 +- lnt/testing/profile/cPerf.cpython-312-darwin.so | Bin 0 -> 109336 bytes lnt/tests/nt.py | 3 +- lnt/tests/test_suite.py | 83 +- pyproject.toml | 8 +- requirements.server.txt | 2 +- tests/SharedInputs/postgres_wrapper.sh | 12 +- tests/lit.cfg | 10 +- tests/lnttool/PostgresDB.shtest | 2 +- tests/runtest/test_suite-interleaved-builds.shtest | 34 +- tests/utils/installation.shtest | 1 + uv.lock | 1192 ++++++++++++++++++++ 18 files changed, 1305 insertions(+), 108 deletions(-) rename .github/workflows/{build-and-publish-package.yml => build-and-publish-packa [...] delete mode 100644 Procfile rename docker-compose.yml => docker-compose.yaml (100%) create mode 100755 lnt/testing/profile/cPerf.cpython-312-darwin.so create mode 100644 uv.lock