summaryrefslogtreecommitdiff
path: root/cmd/trimqueue?h=v0.5.3&id=923ed3d56e46bac4894f71d2c7e3d9a70c9be0e8
diff options
context:
space:
mode:
authorNick White <git@njw.name>2020-09-15 11:54:36 +0100
committerNick White <git@njw.name>2020-09-15 11:54:36 +0100
commit2d9546fe42c85e9882ff3ec041de75f7048e7d3a (patch)
tree37c255665fc524c2500b66b77b58a4ca61d514d7 /cmd/trimqueue?h=v0.5.3&id=923ed3d56e46bac4894f71d2c7e3d9a70c9be0e8
parentd1f2d7b47dd4349d91062f3a1cf6c418d476c4ca (diff)
Abort and delete a failed wipeonly job, like we do with preprocessing
There was no reason not to do this with wipeonly as well, and sure enough a single broken PNG image in a wipeonly task would cause the queue to exponentially fill as happened previously.
Diffstat (limited to 'cmd/trimqueue?h=v0.5.3&id=923ed3d56e46bac4894f71d2c7e3d9a70c9be0e8')
0 files changed, 0 insertions, 0 deletions