3 Commits

Include renames

Author	SHA1	Message	Date
dtourolle	9bcc765408	fix(ci): the builder image has no unzip, so the replay tier had no input ... Found by CI itself, on run 1437 -- the first run that ever got far enough to try. Everything ahead of it worked: checkout brought both submodules, v2 pulled and passed its own version assert, and the fixtures resolved at the pinned version. Then: scripts/artifacts/pull_artifacts.sh: line 54: unzip: command not found The replay fixtures ship as a zip in the generic package registry and pull_artifacts.sh unpacks them with unzip. Without it the step exits 127 and the T2 tier has no input -- reported as a missing fixture by the verify step below, which is a missing tool wearing the wrong label. Worth naming why the local rehearsal missed this and CI did not: the rehearsal had the dumps staged in the working tree by hand, so it built and ran the tier without ever executing the script that fetches them. The image was checked against the build, not against the job. Tag v2 -> v3, in all three places, in one commit. TRACES: DP-007 | PR-004	2026-08-31 08:04:43 +02:00
dtourolle	80c23d39d1	fix(ci): sae-builder-cpu could not configure this repository at all ... v1 has no libfftw3. SAE_SCENE_XGB is on by default and pulls the learned scene-boundary detector into result_sink, whose find_library(FFTW3_LIB fftw3 REQUIRED) at CMakeLists.txt:377 runs at CONFIGURE time -- so cmake fails before any target is chosen, and building only `sae_tests` does not get you past it. The image predates the detector; nothing rebuilt it when the detector landed, which is precisely the gap DP-007's own register row records. -DSAE_SCENE_XGB=OFF would also have made the configure pass. It is the wrong fix and worth saying why: CI is the only place these tests run, so a flag that silences a subsystem there silences it everywhere, and the job would have gone green over a detector nobody was compiling. The image's self-check gains a line, because an image that ships a library CMake cannot find the way CMake looks for it is the failure this block exists to catch. FFTW is checked as a bare .so rather than through pkg-config, since find_library is what CMakeLists.txt actually calls -- checking fftw3.pc would pass on an image whose libfftw3.so was absent. Tag bumped v1 -> v2 here, in build_builder_image.sh and in the workflow's run-time assert, in one commit, as this image's contract requires. v2 is built and published. Rehearsed in the image before pinning it: configure, build and 151 tests now run. TRACES: DP-007 | PR-004	2026-08-30 22:42:15 +02:00
dtourolle	a3827646b9	feat(ci): CPU builder image for the unit-test workflow ... TRACES: DP-007 | PR-004 Pinned by tag rather than :latest, so a workflow run is reproducible against the image it was written for.	2026-08-04 14:53:12 +02:00