The e2e job now removes any leftover arr-e2e-qbittorrent container before starting one, and tears it down at the end whatever the outcome. Runs are serialised with a concurrency group, because the container has a fixed name and binds host port 8080.
The qBittorrent config is now copied into the container with docker cp instead of bind-mounted. docker in the job talks to the runner host's daemon, so /tmp/qbt was resolved on the host, where the job never wrote it. The readiness loop now fails the step if qBittorrent never answers, instead of carrying on.
The health e2e test also turns subtitle providers off before asserting ok. The seed enables OpenSubtitles and the test daemon has no credentials for it, so the report was correctly degraded.
Why
Every e2e run since 2026-08-29 has failed with Conflict. The container name "/arr-e2e-qbittorrent" is already in use. The step never removed its container, so the first run's container (f4212de4a2fd) blocked every run after it. The last run before that (1520) got past setup and failed in the qBittorrent tests, which fits a config that never reached the container.
Verification
e2e on this branch passes: 4 tests, run on the PR.
<!-- claude-projects-attribution: {"github_login":"naps62"} -->
_Requested by **naps**_
The e2e job now removes any leftover `arr-e2e-qbittorrent` container before starting one, and tears it down at the end whatever the outcome. Runs are serialised with a `concurrency` group, because the container has a fixed name and binds host port 8080.
The qBittorrent config is now copied into the container with `docker cp` instead of bind-mounted. `docker` in the job talks to the runner host's daemon, so `/tmp/qbt` was resolved on the host, where the job never wrote it. The readiness loop now fails the step if qBittorrent never answers, instead of carrying on.
The health e2e test also turns subtitle providers off before asserting `ok`. The seed enables OpenSubtitles and the test daemon has no credentials for it, so the report was correctly `degraded`.
<details><summary>Why</summary>
Every e2e run since 2026-08-29 has failed with `Conflict. The container name "/arr-e2e-qbittorrent" is already in use`. The step never removed its container, so the first run's container (`f4212de4a2fd`) blocked every run after it. The last run before that (1520) got past setup and failed in the qBittorrent tests, which fits a config that never reached the container.
</details>
<details><summary>Verification</summary>
e2e on this branch passes: 4 tests, run on the PR.
</details>
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The e2e job never removed its fixed-name qBittorrent container, so every
run since late August failed on the name conflict. Remove a leftover
first, tear down on any outcome, and serialise runs. The config is now
copied in rather than bind-mounted, since the bind path is resolved on
the runner host, not in the job container.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
The seed enables OpenSubtitles and the e2e daemon has no credentials for
it, so the health report is degraded by design. The test is about the
core upstreams.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Requested by naps
The e2e job now removes any leftover
arr-e2e-qbittorrentcontainer before starting one, and tears it down at the end whatever the outcome. Runs are serialised with aconcurrencygroup, because the container has a fixed name and binds host port 8080.The qBittorrent config is now copied into the container with
docker cpinstead of bind-mounted.dockerin the job talks to the runner host's daemon, so/tmp/qbtwas resolved on the host, where the job never wrote it. The readiness loop now fails the step if qBittorrent never answers, instead of carrying on.The health e2e test also turns subtitle providers off before asserting
ok. The seed enables OpenSubtitles and the test daemon has no credentials for it, so the report was correctlydegraded.Why
Every e2e run since 2026-08-29 has failed with
Conflict. The container name "/arr-e2e-qbittorrent" is already in use. The step never removed its container, so the first run's container (f4212de4a2fd) blocked every run after it. The last run before that (1520) got past setup and failed in the qBittorrent tests, which fits a config that never reached the container.Verification
e2e on this branch passes: 4 tests, run on the PR.
🤖 Generated with Claude Code