public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 2/2] travis: Enhance docparse testing
Date: Fri, 14 May 2021 12:45:08 +0200	[thread overview]
Message-ID: <YJ5UtOYnapjKtwJU@pevik> (raw)
In-Reply-To: <YJ5AzHNUAiSGwfS+@pevik>

Hi,

actually the longest one was caused by openSUSE Tumbleweed,
probably some temporary container update issue.

Thus merging both with your ack.

Kind regards,
Petr

> > Hi!
> > Looks good.

> > Is this making the build significantly slower? If not let's get this in
> > now so that we have metadata covered by travis as well.

> 53 min with [1] vs. 36 min [2] without. That's quite a big difference.
> But other build got only 39 min [3], thus running yet another build [4]
> to see what's going on. I'd like to have this docparse testing in travis.

> Kind regards,
> Petr

> [1] https://travis-ci.org/github/pevik/ltp/builds/770930869
> [2] https://travis-ci.org/github/pevik/ltp/builds/770895636
> [3] https://travis-ci.org/github/pevik/ltp/builds/771055881
> [4] https://travis-ci.org/github/pevik/ltp/builds/771117708

  reply	other threads:[~2021-05-14 10:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-12 16:57 [LTP] [PATCH 1/2] build.sh: Support passing configure options Petr Vorel
2021-05-12 16:57 ` [LTP] [PATCH 2/2] travis: Enhance docparse testing Petr Vorel
2021-05-14  7:44   ` Cyril Hrubis
2021-05-14  9:20     ` Petr Vorel
2021-05-14 10:45       ` Petr Vorel [this message]
2021-05-14  7:42 ` [LTP] [PATCH 1/2] build.sh: Support passing configure options Cyril Hrubis
2021-05-14  9:14   ` Petr Vorel
2021-05-14 11:02     ` Petr Vorel

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YJ5UtOYnapjKtwJU@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox