periplu 0.1.1__tar.gz

periplu-0.1.1/LICENSE

@@ -0,0 +1,373 @@
+Mozilla Public License Version 2.0
+==================================
+
+1. Definitions
+--------------
+
+1.1. "Contributor"
+    means each individual or legal entity that creates, contributes to
+    the creation of, or owns Covered Software.
+
+1.2. "Contributor Version"
+    means the combination of the Contributions of others (if any) used
+    by a Contributor and that particular Contributor's Contribution.
+
+1.3. "Contribution"
+    means Covered Software of a particular Contributor.
+
+1.4. "Covered Software"
+    means Source Code Form to which the initial Contributor has attached
+    the notice in Exhibit A, the Executable Form of such Source Code
+    Form, and Modifications of such Source Code Form, in each case
+    including portions thereof.
+
+1.5. "Incompatible With Secondary Licenses"
+    means
+
+    (a) that the initial Contributor has attached the notice described
+        in Exhibit B to the Covered Software; or
+
+    (b) that the Covered Software was made available under the terms of
+        version 1.1 or earlier of the License, but not also under the
+        terms of a Secondary License.
+
+1.6. "Executable Form"
+    means any form of the work other than Source Code Form.
+
+1.7. "Larger Work"
+    means a work that combines Covered Software with other material, in
+    a separate file or files, that is not Covered Software.
+
+1.8. "License"
+    means this document.
+
+1.9. "Licensable"
+    means having the right to grant, to the maximum extent possible,
+    whether at the time of the initial grant or subsequently, any and
+    all of the rights conveyed by this License.
+
+1.10. "Modifications"
+    means any of the following:
+
+    (a) any file in Source Code Form that results from an addition to,
+        deletion from, or modification of the contents of Covered
+        Software; or
+
+    (b) any new file in Source Code Form that contains any Covered
+        Software.
+
+1.11. "Patent Claims" of a Contributor
+    means any patent claim(s), including without limitation, method,
+    process, and apparatus claims, in any patent Licensable by such
+    Contributor that would be infringed, but for the grant of the
+    License, by the making, using, selling, offering for sale, having
+    made, import, or transfer of either its Contributions or its
+    Contributor Version.
+
+1.12. "Secondary License"
+    means either the GNU General Public License, Version 2.0, the GNU
+    Lesser General Public License, Version 2.1, the GNU Affero General
+    Public License, Version 3.0, or any later versions of those
+    licenses.
+
+1.13. "Source Code Form"
+    means the form of the work preferred for making modifications.
+
+1.14. "You" (or "Your")
+    means an individual or a legal entity exercising rights under this
+    License. For legal entities, "You" includes any entity that
+    controls, is controlled by, or is under common control with You. For
+    purposes of this definition, "control" means (a) the power, direct
+    or indirect, to cause the direction or management of such entity,
+    whether by contract or otherwise, or (b) ownership of more than
+    fifty percent (50%) of the outstanding shares or beneficial
+    ownership of such entity.
+
+2. License Grants and Conditions
+--------------------------------
+
+2.1. Grants
+
+Each Contributor hereby grants You a world-wide, royalty-free,
+non-exclusive license:
+
+(a) under intellectual property rights (other than patent or trademark)
+    Licensable by such Contributor to use, reproduce, make available,
+    modify, display, perform, distribute, and otherwise exploit its
+    Contributions, either on an unmodified basis, with Modifications, or
+    as part of a Larger Work; and
+
+(b) under Patent Claims of such Contributor to make, use, sell, offer
+    for sale, have made, import, and otherwise transfer either its
+    Contributions or its Contributor Version.
+
+2.2. Effective Date
+
+The licenses granted in Section 2.1 with respect to any Contribution
+become effective for each Contribution on the date the Contributor first
+distributes such Contribution.
+
+2.3. Limitations on Grant Scope
+
+The licenses granted in this Section 2 are the only rights granted under
+this License. No additional rights or licenses will be implied from the
+distribution or licensing of Covered Software under this License.
+Notwithstanding Section 2.1(b) above, no patent license is granted by a
+Contributor:
+
+(a) for any code that a Contributor has removed from Covered Software;
+    or
+
+(b) for infringements caused by: (i) Your and any other third party's
+    modifications of Covered Software, or (ii) the combination of its
+    Contributions with other software (except as part of its Contributor
+    Version); or
+
+(c) under Patent Claims infringed by Covered Software in the absence of
+    its Contributions.
+
+This License does not grant any rights in the trademarks, service marks,
+or logos of any Contributor (except as may be necessary to comply with
+the notice requirements in Section 3.4).
+
+2.4. Subsequent Licenses
+
+No Contributor makes additional grants as a result of Your choice to
+distribute the Covered Software under a subsequent version of this
+License (see Section 10.2) or under the terms of a Secondary License (if
+permitted under the terms of Section 3.3).
+
+2.5. Representation
+
+Each Contributor represents that the Contributor believes its
+Contributions are its original creation(s) or it has sufficient rights
+to grant the rights to its Contributions conveyed by this License.
+
+2.6. Fair Use
+
+This License is not intended to limit any rights You have under
+applicable copyright doctrines of fair use, fair dealing, or other
+equivalents.
+
+2.7. Conditions
+
+Sections 3.1, 3.2, 3.3, and 3.4 are conditions of the licenses granted
+in Section 2.1.
+
+3. Responsibilities
+-------------------
+
+3.1. Distribution of Source Form
+
+All distribution of Covered Software in Source Code Form, including any
+Modifications that You create or to which You contribute, must be under
+the terms of this License. You must inform recipients that the Source
+Code Form of the Covered Software is governed by the terms of this
+License, and how they can obtain a copy of this License. You may not
+attempt to alter or restrict the recipients' rights in the Source Code
+Form.
+
+3.2. Distribution of Executable Form
+
+If You distribute Covered Software in Executable Form then:
+
+(a) such Covered Software must also be made available in Source Code
+    Form, as described in Section 3.1, and You must inform recipients of
+    the Executable Form how they can obtain a copy of such Source Code
+    Form by reasonable means in a timely manner, at a charge no more
+    than the cost of distribution to the recipient; and
+
+(b) You may distribute such Executable Form under the terms of this
+    License, or sublicense it under different terms, provided that the
+    license for the Executable Form does not attempt to limit or alter
+    the recipients' rights in the Source Code Form under this License.
+
+3.3. Distribution of a Larger Work
+
+You may create and distribute a Larger Work under terms of Your choice,
+provided that You also comply with the requirements of this License for
+the Covered Software. If the Larger Work is a combination of Covered
+Software with a work governed by one or more Secondary Licenses, and the
+Covered Software is not Incompatible With Secondary Licenses, this
+License permits You to additionally distribute such Covered Software
+under the terms of such Secondary License(s), so that the recipient of
+the Larger Work may, at their option, further distribute the Covered
+Software under the terms of either this License or such Secondary
+License(s).
+
+3.4. Notices
+
+You may not remove or alter the substance of any license notices
+(including copyright notices, patent notices, disclaimers of warranty,
+or limitations of liability) contained within the Source Code Form of
+the Covered Software, except that You may alter any license notices to
+the extent required to remedy known factual inaccuracies.
+
+3.5. Application of Additional Terms
+
+You may choose to offer, and to charge a fee for, warranty, support,
+indemnity or liability obligations to one or more recipients of Covered
+Software. However, You may do so only on Your own behalf, and not on
+behalf of any Contributor. You must make it absolutely clear that any
+such warranty, support, indemnity, or liability obligation is offered by
+You alone, and You hereby agree to indemnify every Contributor for any
+liability incurred by such Contributor as a result of warranty, support,
+indemnity or liability terms You offer. You may include additional
+disclaimers of warranty and limitations of liability specific to any
+jurisdiction.
+
+4. Inability to Comply Due to Statute or Regulation
+---------------------------------------------------
+
+If it is impossible for You to comply with any of the terms of this
+License with respect to some or all of the Covered Software due to
+statute, judicial order, or regulation then You must: (a) comply with
+the terms of this License to the maximum extent possible; and (b)
+describe the limitations and the code they affect. Such description must
+be placed in a text file included with all distributions of the Covered
+Software under this License. Except to the extent prohibited by statute
+or regulation, such description must be sufficiently detailed for a
+recipient of ordinary skill to be able to understand it.
+
+5. Termination
+--------------
+
+5.1. The rights granted under this License will terminate automatically
+if You fail to comply with any of its terms. However, if You become
+compliant, then the rights granted under this License from a particular
+Contributor are reinstated (a) provisionally, unless and until such
+Contributor explicitly and finally terminates Your grants, and (b) on an
+ongoing basis, if such Contributor fails to notify You of the
+non-compliance by some reasonable means prior to 60 days after You have
+come back into compliance. Moreover, Your grants from a particular
+Contributor are reinstated on an ongoing basis if such Contributor
+notifies You of the non-compliance by some reasonable means, this is the
+first time You have received notice of non-compliance with this License
+from such Contributor, and You become compliant prior to 30 days after
+Your receipt of the notice.
+
+5.2. If You initiate litigation against any entity by asserting a patent
+infringement claim (excluding declaratory judgment actions,
+counter-claims, and cross-claims) alleging that a Contributor Version
+directly or indirectly infringes any patent, then the rights granted to
+You by any and all Contributors for the Covered Software under Section
+2.1 of this License shall terminate.
+
+5.3. In the event of termination under Sections 5.1 or 5.2 above, all
+end user license agreements (excluding distributors and resellers) which
+have been validly granted by You or Your distributors under this License
+prior to termination shall survive termination.
+
+************************************************************************
+*                                                                      *
+*  6. Disclaimer of Warranty                                           *
+*  -------------------------                                           *
+*                                                                      *
+*  Covered Software is provided under this License on an "as is"       *
+*  basis, without warranty of any kind, either expressed, implied, or  *
+*  statutory, including, without limitation, warranties that the       *
+*  Covered Software is free of defects, merchantable, fit for a        *
+*  particular purpose or non-infringing. The entire risk as to the     *
+*  quality and performance of the Covered Software is with You.        *
+*  Should any Covered Software prove defective in any respect, You     *
+*  (not any Contributor) assume the cost of any necessary servicing,   *
+*  repair, or correction. This disclaimer of warranty constitutes an   *
+*  essential part of this License. No use of any Covered Software is   *
+*  authorized under this License except under this disclaimer.         *
+*                                                                      *
+************************************************************************
+
+************************************************************************
+*                                                                      *
+*  7. Limitation of Liability                                          *
+*  --------------------------                                          *
+*                                                                      *
+*  Under no circumstances and under no legal theory, whether tort      *
+*  (including negligence), contract, or otherwise, shall any           *
+*  Contributor, or anyone who distributes Covered Software as          *
+*  permitted above, be liable to You for any direct, indirect,         *
+*  special, incidental, or consequential damages of any character      *
+*  including, without limitation, damages for lost profits, loss of    *
+*  goodwill, work stoppage, computer failure or malfunction, or any    *
+*  and all other commercial damages or losses, even if such party      *
+*  shall have been informed of the possibility of such damages. This   *
+*  limitation of liability shall not apply to liability for death or   *
+*  personal injury resulting from such party's negligence to the       *
+*  extent applicable law prohibits such limitation. Some               *
+*  jurisdictions do not allow the exclusion or limitation of           *
+*  incidental or consequential damages, so this exclusion and          *
+*  limitation may not apply to You.                                    *
+*                                                                      *
+************************************************************************
+
+8. Litigation
+-------------
+
+Any litigation relating to this License may be brought only in the
+courts of a jurisdiction where the defendant maintains its principal
+place of business and such litigation shall be governed by laws of that
+jurisdiction, without reference to its conflict-of-law provisions.
+Nothing in this Section shall prevent a party's ability to bring
+cross-claims or counter-claims.
+
+9. Miscellaneous
+----------------
+
+This License represents the complete agreement concerning the subject
+matter hereof. If any provision of this License is held to be
+unenforceable, such provision shall be reformed only to the extent
+necessary to make it enforceable. Any law or regulation which provides
+that the language of a contract shall be construed against the drafter
+shall not be used to construe this License against a Contributor.
+
+10. Versions of the License
+---------------------------
+
+10.1. New Versions
+
+Mozilla Foundation is the license steward. Except as provided in Section
+10.3, no one other than the license steward has the right to modify or
+publish new versions of this License. Each version will be given a
+distinguishing version number.
+
+10.2. Effect of New Versions
+
+You may distribute the Covered Software under the terms of the version
+of the License under which You originally received the Covered Software,
+or under the terms of any subsequent version published by the license
+steward.
+
+10.3. Modified Versions
+
+If you create software not governed by this License, and you want to
+create a new license for such software, you may create and use a
+modified version of this License if you rename the license and remove
+any references to the name of the license steward (except to note that
+such modified license differs from this License).
+
+10.4. Distributing Source Code Form that is Incompatible With Secondary
+Licenses
+
+If You choose to distribute Source Code Form that is Incompatible With
+Secondary Licenses under the terms of this version of the License, the
+notice described in Exhibit B of this License must be attached.
+
+Exhibit A - Source Code Form License Notice
+-------------------------------------------
+
+  This Source Code Form is subject to the terms of the Mozilla Public
+  License, v. 2.0. If a copy of the MPL was not distributed with this
+  file, You can obtain one at https://mozilla.org/MPL/2.0/.
+
+If it is not possible or desirable to put the notice in a particular
+file, then You may include the notice in a location (such as a LICENSE
+file in a relevant directory) where a recipient would be likely to look
+for such a notice.
+
+You may add additional accurate notices of copyright ownership.
+
+Exhibit B - "Incompatible With Secondary Licenses" Notice
+---------------------------------------------------------
+
+  This Source Code Form is "Incompatible With Secondary Licenses", as
+  defined by the Mozilla Public License, v. 2.0.

periplu-0.1.1/PKG-INFO

@@ -0,0 +1,138 @@
+Metadata-Version: 2.4
+Name: periplu
+Version: 0.1.1
+Summary: A pytest plugin for deterministic container tests: waits end on events, never on clocks
+License-Expression: MPL-2.0
+License-File: LICENSE
+Classifier: Framework :: Pytest
+Classifier: Operating System :: POSIX :: Linux
+Classifier: Topic :: Software Development :: Testing
+Requires-Dist: pytest>=8.4
+Requires-Dist: pytest-xdist>=3.8
+Requires-Python: >=3.14
+Project-URL: Repository, https://github.com/recregt/periplu
+Description-Content-Type: text/markdown
+
+<!--
+This Source Code Form is subject to the terms of the Mozilla Public
+License, v. 2.0. If a copy of the MPL was not distributed with this
+file, You can obtain one at https://mozilla.org/MPL/2.0/.
+-->
+
+# periplu
+
+A pytest plugin for end-to-end tests in Podman containers. Waits end on events, not on clocks, and parallel tests are admitted by what they measurably use.
+
+- A systemd container counts as booted when systemd itself sends `READY=1`.
+- A test waits for a process, a FIFO or a signal, and fails as soon as the thing it waits on has ended. There are no deadlines.
+- Tests run in parallel only while their measured memory, CPU and inotify instances fit the machine. A waiting test sleeps until another test starts, ends or dies.
+- The longest tests start first.
+- A failed test leaves a bundle with every command it recorded and a description of the machine.
+
+## Requirements
+
+- Linux with cgroup v2 and kernel 5.19 or newer, for `memory.peak`.
+- Rootless Podman.
+- Python 3.14 or newer.
+
+## Install
+
+```sh
+uv add periplu
+```
+
+Then configure it in `pyproject.toml`:
+
+```toml
+[tool.pytest.ini_options]
+periplu_project = "myproject"
+periplu_baseline = "resources.json"
+periplu_failures = "failures"
+```
+
+All three settings are required.
+
+- `periplu_project` names the cache (`~/.cache/periplu/<project>/`), the containers (`<project>-test-…`) and the images (`<project>-test:…`, `<project>-snapshot:…`).
+- `periplu_baseline` is the committed file of resource estimates. It may be missing at first.
+- `periplu_failures` is where failure bundles are written.
+
+Both paths are relative to the pytest rootdir.
+
+## A first suite
+
+[`examples/systemd`](https://github.com/recregt/periplu/tree/main/examples/systemd) is a complete suite. Run it from a clone:
+
+```sh
+git clone https://github.com/recregt/periplu
+cd periplu/examples/systemd
+uv run pytest -n auto
+```
+
+Its fixture is the whole integration:
+
+```python
+@pytest.fixture(scope="session")
+def image():
+    return periplu.image(Path(__file__).parent / "Containerfile")
+
+
+@pytest.fixture
+def machine(request, image):
+    with periplu.admitted(
+        request.node.nodeid, image, run_args=[], systemd=True, variant="fresh"
+    ) as name:
+        yield periplu.Container(name)
+```
+
+## Containers
+
+From `periplu.container`:
+
+- `image(containerfile)` builds the file once per content and returns the image name.
+- `admitted(test, image, *, run_args, systemd, variant)` waits until the machine has room for `test`, starts the container, measures it while the test runs, and removes it afterwards. With `systemd=True` it returns once systemd has booted. `variant` keeps separate estimates for the same test started different ways, for example from a snapshot.
+- `snapshot(key, image, *, run_args, systemd, build)` runs `build(name)` in a fresh container and commits the result. It is built once per test session and removed when the session ends.
+- `Container(name)` has `exec(*args, env=, user=, check=)`, `start_background(*args)`, `path_exists(path)`, `process_tree()`, and `record(command, returncode, stdout, stderr)` for commands that should appear in a failure bundle. Override `probes()` to add what a failure bundle describes.
+
+## Waiting
+
+- `start_background(...)` returns a `BackgroundProcess`. Its `ended` event is set when the process exits, `wait()` returns the result, `pid()` and `signal(name)` reach the process inside the container.
+- `wait_any(*events)` blocks until any of the events is set. Pair what a test waits for with the process it depends on, so the test fails at once instead of hanging. The example test does this with a FIFO.
+- `until(wanted, what, unless=)` repeats `wanted()` until it is true and fails when `unless` has ended. It polls, so use it only for a state that has no event to wait on.
+
+## Resources
+
+For each pool, a test starts only if what is in use outside the suite, plus the demand of every running test, plus its own demand, fits the capacity:
+
+| Pool | Capacity | Demand of a test |
+|---|---|---|
+| Memory | `MemAvailable` when nothing of the suite runs, within the cgroup's `memory.max` | `memory.peak` of its container, a peak the kernel records |
+| CPU | CPUs in the affinity mask, within `cpu.max` | average cores over its run |
+| inotify instances | `fs.inotify.max_user_instances` minus the instances in use when nothing of the suite runs | instances held by the container's processes, its conmon and exec sessions and its pasta process, counted after boot and at the end |
+
+Rootless containers charge inotify instances to the user who runs Podman, so all containers share one pool. At the kernel default of 128 that is about 16 systemd containers, whatever the number of CPUs. The end of every run shows how many workers each pool allows, so you can see which one holds a run back.
+
+When inotify is the limit, raise it. The value you need is the instances in use outside the suite plus the workers you want times the largest per-test count, both printed in the run summary. For 24 workers at 12 instances each with 10 in use elsewhere, that is 10 + 24 × 12 = 298:
+
+```sh
+sudo sysctl fs.inotify.max_user_instances=298
+```
+
+This lasts until the next reboot. To keep it, put the line `fs.inotify.max_user_instances = 298` in a file under `/etc/sysctl.d/` and run `sudo sysctl --system`. On NixOS, set `boot.kernel.sysctl."fs.inotify.max_user_instances" = 298;`.
+
+Memory is the only pool with a kernel-recorded peak. CPU only slows tests down when oversubscribed. The inotify count is sampled twice, so an instance a test holds only briefly between the samples is not seen.
+
+A test without an estimate of its own is assumed to need as much as the largest known test. When nothing is known yet, it runs only when nothing else does. To measure a new suite in parallel, set `PERIPLU_CALIBRATE=1` and choose a worker count that fits by hand. Then write the baseline:
+
+```sh
+python -m periplu.resources <project> <rootdir> <baseline>
+```
+
+`pytest -n auto` picks the number of workers from the estimates: the smallest number any pool allows. A run ends with a line such as `workers allowed by: tests 83, longest test 12, cpu 40, memory 7, inotify 28`, where memory sets the number.
+
+## Failure bundles
+
+When a test that uses a `Container` fails, periplu writes `run-N.txt` for every recorded command and `machine.txt` with the output of `probes()` to `<periplu_failures>/<test id>/`. The paths are listed at the end of the run.
+
+## License
+
+[Mozilla Public License 2.0](https://github.com/recregt/periplu/blob/main/LICENSE)

periplu-0.1.1/README.md

@@ -0,0 +1,123 @@
+<!--
+This Source Code Form is subject to the terms of the Mozilla Public
+License, v. 2.0. If a copy of the MPL was not distributed with this
+file, You can obtain one at https://mozilla.org/MPL/2.0/.
+-->
+
+# periplu
+
+A pytest plugin for end-to-end tests in Podman containers. Waits end on events, not on clocks, and parallel tests are admitted by what they measurably use.
+
+- A systemd container counts as booted when systemd itself sends `READY=1`.
+- A test waits for a process, a FIFO or a signal, and fails as soon as the thing it waits on has ended. There are no deadlines.
+- Tests run in parallel only while their measured memory, CPU and inotify instances fit the machine. A waiting test sleeps until another test starts, ends or dies.
+- The longest tests start first.
+- A failed test leaves a bundle with every command it recorded and a description of the machine.
+
+## Requirements
+
+- Linux with cgroup v2 and kernel 5.19 or newer, for `memory.peak`.
+- Rootless Podman.
+- Python 3.14 or newer.
+
+## Install
+
+```sh
+uv add periplu
+```
+
+Then configure it in `pyproject.toml`:
+
+```toml
+[tool.pytest.ini_options]
+periplu_project = "myproject"
+periplu_baseline = "resources.json"
+periplu_failures = "failures"
+```
+
+All three settings are required.
+
+- `periplu_project` names the cache (`~/.cache/periplu/<project>/`), the containers (`<project>-test-…`) and the images (`<project>-test:…`, `<project>-snapshot:…`).
+- `periplu_baseline` is the committed file of resource estimates. It may be missing at first.
+- `periplu_failures` is where failure bundles are written.
+
+Both paths are relative to the pytest rootdir.
+
+## A first suite
+
+[`examples/systemd`](https://github.com/recregt/periplu/tree/main/examples/systemd) is a complete suite. Run it from a clone:
+
+```sh
+git clone https://github.com/recregt/periplu
+cd periplu/examples/systemd
+uv run pytest -n auto
+```
+
+Its fixture is the whole integration:
+
+```python
+@pytest.fixture(scope="session")
+def image():
+    return periplu.image(Path(__file__).parent / "Containerfile")
+
+
+@pytest.fixture
+def machine(request, image):
+    with periplu.admitted(
+        request.node.nodeid, image, run_args=[], systemd=True, variant="fresh"
+    ) as name:
+        yield periplu.Container(name)
+```
+
+## Containers
+
+From `periplu.container`:
+
+- `image(containerfile)` builds the file once per content and returns the image name.
+- `admitted(test, image, *, run_args, systemd, variant)` waits until the machine has room for `test`, starts the container, measures it while the test runs, and removes it afterwards. With `systemd=True` it returns once systemd has booted. `variant` keeps separate estimates for the same test started different ways, for example from a snapshot.
+- `snapshot(key, image, *, run_args, systemd, build)` runs `build(name)` in a fresh container and commits the result. It is built once per test session and removed when the session ends.
+- `Container(name)` has `exec(*args, env=, user=, check=)`, `start_background(*args)`, `path_exists(path)`, `process_tree()`, and `record(command, returncode, stdout, stderr)` for commands that should appear in a failure bundle. Override `probes()` to add what a failure bundle describes.
+
+## Waiting
+
+- `start_background(...)` returns a `BackgroundProcess`. Its `ended` event is set when the process exits, `wait()` returns the result, `pid()` and `signal(name)` reach the process inside the container.
+- `wait_any(*events)` blocks until any of the events is set. Pair what a test waits for with the process it depends on, so the test fails at once instead of hanging. The example test does this with a FIFO.
+- `until(wanted, what, unless=)` repeats `wanted()` until it is true and fails when `unless` has ended. It polls, so use it only for a state that has no event to wait on.
+
+## Resources
+
+For each pool, a test starts only if what is in use outside the suite, plus the demand of every running test, plus its own demand, fits the capacity:
+
+| Pool | Capacity | Demand of a test |
+|---|---|---|
+| Memory | `MemAvailable` when nothing of the suite runs, within the cgroup's `memory.max` | `memory.peak` of its container, a peak the kernel records |
+| CPU | CPUs in the affinity mask, within `cpu.max` | average cores over its run |
+| inotify instances | `fs.inotify.max_user_instances` minus the instances in use when nothing of the suite runs | instances held by the container's processes, its conmon and exec sessions and its pasta process, counted after boot and at the end |
+
+Rootless containers charge inotify instances to the user who runs Podman, so all containers share one pool. At the kernel default of 128 that is about 16 systemd containers, whatever the number of CPUs. The end of every run shows how many workers each pool allows, so you can see which one holds a run back.
+
+When inotify is the limit, raise it. The value you need is the instances in use outside the suite plus the workers you want times the largest per-test count, both printed in the run summary. For 24 workers at 12 instances each with 10 in use elsewhere, that is 10 + 24 × 12 = 298:
+
+```sh
+sudo sysctl fs.inotify.max_user_instances=298
+```
+
+This lasts until the next reboot. To keep it, put the line `fs.inotify.max_user_instances = 298` in a file under `/etc/sysctl.d/` and run `sudo sysctl --system`. On NixOS, set `boot.kernel.sysctl."fs.inotify.max_user_instances" = 298;`.
+
+Memory is the only pool with a kernel-recorded peak. CPU only slows tests down when oversubscribed. The inotify count is sampled twice, so an instance a test holds only briefly between the samples is not seen.
+
+A test without an estimate of its own is assumed to need as much as the largest known test. When nothing is known yet, it runs only when nothing else does. To measure a new suite in parallel, set `PERIPLU_CALIBRATE=1` and choose a worker count that fits by hand. Then write the baseline:
+
+```sh
+python -m periplu.resources <project> <rootdir> <baseline>
+```
+
+`pytest -n auto` picks the number of workers from the estimates: the smallest number any pool allows. A run ends with a line such as `workers allowed by: tests 83, longest test 12, cpu 40, memory 7, inotify 28`, where memory sets the number.
+
+## Failure bundles
+
+When a test that uses a `Container` fails, periplu writes `run-N.txt` for every recorded command and `machine.txt` with the output of `probes()` to `<periplu_failures>/<test id>/`. The paths are listed at the end of the run.
+
+## License
+
+[Mozilla Public License 2.0](https://github.com/recregt/periplu/blob/main/LICENSE)

periplu-0.1.1/pyproject.toml

@@ -0,0 +1,36 @@
+[project]
+name = "periplu"
+version = "0.1.1"
+description = "A pytest plugin for deterministic container tests: waits end on events, never on clocks"
+readme = "README.md"
+license = "MPL-2.0"
+license-files = ["LICENSE"]
+requires-python = ">=3.14"
+classifiers = [
+    "Framework :: Pytest",
+    "Operating System :: POSIX :: Linux",
+    "Topic :: Software Development :: Testing",
+]
+dependencies = [
+    "pytest>=8.4",
+    "pytest-xdist>=3.8",
+]
+
+[project.urls]
+Repository = "https://github.com/recregt/periplu"
+
+[project.entry-points.pytest11]
+periplu = "periplu.plugin"
+
+[tool.pytest.ini_options]
+addopts = [
+    "-p",
+    "no:periplu",
+    "-p",
+    "no:cacheprovider",
+]
+testpaths = ["tests"]
+
+[build-system]
+requires = ["uv_build>=0.13,<0.14"]
+build-backend = "uv_build"