On Wed, Sep 09, 2020 at 04:24:00PM +0800, 罗勇刚(Yonggang Luo) wrote: > On Wed, Sep 9, 2020 at 4:17 PM Daniel P. Berrangé <berra...@redhat.com> > wrote: > > > On Wed, Sep 09, 2020 at 03:48:18AM +0800, Yonggang Luo wrote: > > > freebsd 1 hour limit not hit anymore > > > > How long does the combined job take with this change ? If it is > > within 10 minutes of the limit, then we still want the split, as > > transient changes in the CI system can push it over the limit > > making the test unreliable. > > > I think we going to a wrong direction, I think there is some tests a stall > the test runner, > please look at > https://cirrus-ci.com/task/5110577531977728 > When its running properly, the consumed time are little, but when tests > running too long, look at the cpu > usage, the cpu usage are nearly zero. does't consuming time. > > And look at > https://cirrus-ci.com/task/6119341601062912 > > If the tests running properly, the time consuming are little > > We should not hide the error by split them
Ok, please explain this in the commit message so reviewers know why the change is intentionally reverting the previous split. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
