CI: heapster-tests
take a mysteriously long time to complete
#1843
Labels
performance
Issues that involve or include performance problems
subsystem: heapster
Issues specifically related to memory verification using Heapster
tooling: CI
Issues involving CI/CD scripts or processes
The
heapster-tests
CI job takes approximately 2 hours to complete at the moment, which is even longer than it takes to run theawslc
job. See a recent example of this here. What's more, I don't have a keen sense as to why this happens. If you look at the log from that job, it does report some timing info for certain Coq commands:But none of them actually take that long. This suggests that something else is taking up the bulk of the time. We should track down what this is at try to reign it in, or at the very least, add some additional logging to make it obvious that it is the thing that takes up so much time.
The text was updated successfully, but these errors were encountered: