On Wed, 9 Sep 2020 at 05:47, Yonggang Luo <[email protected]> wrote: > > freebsd 1 hour limit not hit anymore > > Signed-off-by: Yonggang Luo <[email protected]>
Reviewed-by: Ed Maste <[email protected]> > 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. So it looks like we have a test getting stuck. After this change is in we could split the test execution out into its own script so to make it more obvious if/when this happens - for example, script: - mkdir build - cd build - ../configure --enable-werror || { cat config.log; exit 1; } - gmake -j8 test_script: - gmake V=1 check I can follow up with a proper patch for that (and making the change for macos as well) later.
