On Thu, Sep 10, 2020 at 2:16 AM Daniel P. Berrangé <berra...@redhat.com>
wrote:
> On Wed, Sep 09, 2020 at 01:32:04PM -0400, Ed Maste wrote:
> > On Wed, 9 Sep 2020 at 05:47, Yonggang Luo <luoyongg...@gmail.com> wrote:
> > >
> > > freebsd 1 hour limit not hit anymore
> > >
> > > Signed-off-by: Yonggang Luo <luoyongg...@gmail.com>
> >
> > Reviewed-by: Ed Maste <ema...@freebsd.org>
> >
> > > 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.
>
> What would help most is if there's a way to convince meson to print
> the execution time of each test case, instead of merely its name.
> That way we could immediately spot the slow test when it hits
>
> Yeap, that's would be great, but now the tests are running by not by meson
>
> 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 :|
>
>
--
此致
礼
罗勇刚
Yours
sincerely,
Yonggang Luo
