3.6.1-2 in the archive
build failed,
ours is 3.6.1-2+py315.1.
Nothing recorded is waiting on this one.
aborted,
3.6.1-2+py315.1,
as work request 1351410,
which ended in work request 1351412.
Which turned out to be build-failed: the workflow ended: build-failed, work request 1351412.
Sent before this one:
3.6.1-1+py315.1, 3.6.1-1+py315.2, 3.6.1-1+py315.3.
A version that was sent is spent, whatever came of it.
| Question | Answer | Said by | As of |
|---|---|---|---|
| Why did the build fail? |
superseded-dependency
Built against our own rebuild of a dependency, one generation back. The run is evidence, unlike an archive copy: re-run it against the current suite before reading the failure. python3-grpcio 1.51.1-9+py315.1: we publish 1.51.1-10+py315.1 |
deps/11 | not dated |
| Which known interpreter change does this failure show? |
load-module-removed
uses the removed loader method. `Loader.load_module()` has been removed from the import machinery. `Loader.exec_module()` replaces it. [1m[31mE AttributeError: 'SourceFileLoader' object has no attribute 'load_module'. Did you mean '.exec_module' instead of '.load_module'?[0m |
deps/11 | not dated |
| has anybody reported this under the usertag? |
1 bug
somebody has already reported this under the round's usertag, so it is tracked; the tag is the only record connecting what was sent to what this tracks #1149247 python-tavern: FTBFS against python 3.15rc2 |
the BTS usertag | not dated |
| Version | Arch | Kind | Result | Binaries | Interpreters | Closure | Finished |
|---|---|---|---|---|---|---|---|
3.6.1-2
|
amd64 | test | fail | archive | 3.14, 3.15 | — | 2026-09-26 03:22 |
3.6.1-2+py315.1
|
all | build | fail | unknown | not read yet | — | 2026-09-26 03:50 |
3.6.1-1+py315.3
|
all | build | fail | unknown | not read yet | — | 2026-09-25 03:12 |
3.6.1-1+py315.2
|
all | build | fail | unknown | not read yet | — | 2026-08-28 01:54 |
3.6.1-1
|
amd64 | test | pass | the archive's (reference arm) | 3.14 | — | 2026-08-27 03:28 |