From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v4 4/7] lib: Add script for running tests
Date: Wed, 14 Jul 2021 16:37:12 +0200 [thread overview]
Message-ID: <YO72mA9nhaCq1bLe@pevik> (raw)
In-Reply-To: <YO2f+P8Z9l6SISDG@yuki>
Hi all,
...
> > > Not sure what we can do here, I guess that timings would be hard to fix
> > > on VMs that run the tests.
> > If I remember correctly Richie suggested that FAIL is also OK. He said only
> > TBROK and TCONF is a problem. I'd prefer to fuzzy sync tests which always pass,
> > but after this effort I can work on API tests metadata, which would allow also
> > this.
> Another possibility would be relaxing the timings on VMs. I guess that
> we could change the treshold for reaching the criticall section to 10 on
> VMs.
I'd be for it, we have checks for VM. @Richie, any opinion about it?
Kind regards,
Petr
next prev parent reply other threads:[~2021-07-14 14:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 10:13 [LTP] [PATCH v4 0/7] Run tests in CI Petr Vorel
2021-07-13 10:13 ` [LTP] [PATCH v4 1/7] tst_device: Require root Petr Vorel
2021-07-13 12:53 ` Cyril Hrubis
2021-07-13 10:13 ` [LTP] [PATCH v4 2/7] tst_net.sh: Declare prefix variable as empty Petr Vorel
2021-07-13 12:59 ` Cyril Hrubis
2021-07-13 10:13 ` [LTP] [PATCH v4 3/7] tst_strstatus.c: Use musl compatible status number Petr Vorel
2021-07-13 13:03 ` Cyril Hrubis
2021-07-13 10:13 ` [LTP] [PATCH v4 4/7] lib: Add script for running tests Petr Vorel
2021-07-13 13:23 ` Cyril Hrubis
2021-07-13 14:16 ` Petr Vorel
2021-07-13 14:15 ` Cyril Hrubis
2021-07-14 14:37 ` Petr Vorel [this message]
2021-07-13 10:13 ` [LTP] [PATCH v4 5/7] make: Add make test{, -c, -shell} targets Petr Vorel
2021-07-13 14:30 ` Cyril Hrubis
2021-07-13 10:13 ` [LTP] [PATCH v4 6/7] build.sh: Add support for make test Petr Vorel
2021-07-13 14:45 ` Cyril Hrubis
2021-07-13 10:13 ` [LTP] [PATCH v4 7/7] CI: Run also " 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=YO72mA9nhaCq1bLe@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