Bug #19967
Updated by Brett Smith about 1 year ago
Currently the container cost is recorded as 0 in this case.
This should ensure the cost of a cancel-retry-cancel-retry-cancel-fail cycle is reflected properly.
Have crunch-run periodically update the price while the container is running, perhaps each time it gets a SIGUSR2 after loadPrices (i.e., on each dispatcher probe).