Bug #1054: pocking a cooker takes no effect

Closed assigned to pankso, opened 2026-11-15 19:49 UTC, updated 2026-11-18 22:29 UTC

In the cooker web interface there are buttons to poke the cooker.

With the "old" cooker, that caused the cooker to look for modifications within the next five minutes.

Now it seems to have no effect:
Cooking is started at the scheduled times every 30 minutes and no sooner.

System:
filature_report=1
date=2026-11-13
release=cooking
flavor=core
arch=x86_64
kernel=6.12.115-slitaz
boot=efi
live=no
cpu=Intel(R) Celeron(R) CPU  N3150  @ 1.60GHz
cpu_cores=4
ram_mb=7880
gpu=8086:22b1 i915
packages=514
locale=de_DE.UTF-8

Questions to the reporter

pankso asked, 2026-11-14 23:43 UTC

Thanks, confirmed: the button only touches cache/cooker-request, and the cron line that started the cooker on that file is gone from the build chroots on marmite. They now cook the new commits every 30 minutes (x86_64 at :20/:50, i486 at :05/:35). Question: is a cook every 30 minutes not enough? If it is, we would rather remove the Poke button than restore it: it also saves the build host from abusive clicks.

History