All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH V3] lib: multiply the max_runtime if detect slow kconfigs
Date: Thu, 19 Dec 2024 14:25:15 +0100	[thread overview]
Message-ID: <20241219132515.GB111004@pevik> (raw)
In-Reply-To: <CAEemH2ci3i+UTziZZegsQR+C-q_+ri9yHbNZyyGPk8ypAZF3KQ@mail.gmail.com>

> On Thu, Dec 19, 2024 at 9:19 PM Cyril Hrubis <chrubis@suse.cz> wrote:

> > Hi!
> > > > Sounds like we need to have two different runtime values in the tests,
> > > > max_runtime which is the timeout for the test and just runtime which is
> > > > for how long will the test loop.


> > > Agree, if we define the looping runtime in a separate value, that would
> > be
> > > helpful.

> > There was a problem with having the two different values in a single
> > variable before as well. We do have the LTP_RUNTIME_MUL which multiplied
> > both the timeout and runtime. These should be separate multipliers as
> > well which multiplied both the timeout and runtime. These should be
> > separate multipliers as well.


> I noticed that tests using max_runtime to control the test time
> always use another function tst_remaining_runtime(), so maybe
> we can utilize this to bypass that.

> Later I will look into details, now I have a meeting in the coming 2h.

> @Petr, @Martin, Feel free to revert the two patches if you needed.
> 2da30df24e676d5f4cfcf0b11674cbdf11a19b8a
> 64e11fec079480179aa9473ae5e1e8ad78ef9ac3

Thanks. OK, we can wait a bit (few days) until revert. There will be Xmas, thus
not much busy time for us.

Kind regards,
Petr


> > --
> > Cyril Hrubis
> > chrubis@suse.cz

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

      reply	other threads:[~2024-12-19 13:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-12  6:04 [LTP] [PATCH V3] lib: multiply the max_runtime if detect slow kconfigs Li Wang
2024-12-13 22:40 ` Petr Vorel
2024-12-16  9:37   ` Li Wang
2024-12-16 12:28     ` Petr Vorel
2024-12-17  2:40       ` Li Wang
2024-12-16 13:00   ` Cyril Hrubis
2024-12-16 17:29     ` Petr Vorel
2024-12-17  3:46     ` Li Wang
2024-12-18  3:23       ` Li Wang
2024-12-16 12:51 ` Cyril Hrubis
2024-12-19 12:53 ` Petr Vorel
2024-12-19 13:07   ` Li Wang
2024-12-19 12:57 ` Martin Doucha
2024-12-19 13:07   ` Petr Vorel
2024-12-19 13:12     ` Li Wang
2024-12-19 13:28       ` Petr Vorel
2024-12-19 13:29         ` Cyril Hrubis
2024-12-20  3:59           ` Li Wang
2024-12-20  7:19             ` Li Wang
2024-12-19 13:10   ` Cyril Hrubis
2024-12-19 13:14     ` Li Wang
2024-12-19 13:19       ` Cyril Hrubis
2024-12-19 13:22         ` Li Wang
2024-12-19 13:25           ` Petr Vorel [this message]

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=20241219132515.GB111004@pevik \
    --to=pvorel@suse.cz \
    --cc=liwang@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.