-
### Context
In the CI of this repo, the integration tests are packing up to 8 charms in a single GH runner. This is problematic because it is very time consuming and causing pressure on disk space.…
-
I will take the opportunity to report another small glitch: On Debian, the build by default invokes "make" with parallel tasks (`-j` option). This worked well in the past, but now I see a reproducible…
-
By not having parallel tests loopy [missed an issue regarding mismatching hashes between ranks](https://github.com/inducer/loopy/pull/886#issuecomment-2507860688). I think if you had parallel tests th…
-
We currently run all tests sequentially because we bind to the same set of ports throughout different tests. We can run the tests in parallel if we bind the sockets to port 0 - that would force the ke…
-
### Context
Currently, the UATs driver runs all tests consecutively. Since this repo is now hosting multiple tests, we should investigate the possibility of running them in some kind of parallel.
##…
-
[sbt parallelizes munit tests](https://scalameta.org/munit/docs/tests.html#run-tests-in-parallel) but scala-cli won't be able to parallelize munit tests. as scala-cli is included as default scala tool…
-
The `QCheck-STM` test framework allows to test a library in parallel, using domains.
This is simply done by instantiating another functor (`STM_domain.Make` instead of `STM_sequential.Make`).
The pr…
-
### Describe the bug
Trying to execute multiple unit tests in parallel with xdist `-n X` on Windows leads to failures. It happens most likely because one worker compiles and starts executing a kernel…
-
As the title said, when using python 3.13, the tests in `tests/text_area` fails, despite succeeding on other python version and when not running in parallel.
```bash
# Succeed
poetry run pytest t…
-
### Proposal
Let's save some time.
- The packages/subdirectories to be checked:
- [x] `cmd/prometheus`, see https://github.com/prometheus/prometheus/pull/14618
- [x] `cmd/promtool`, see ht…