All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: Martin Doucha <martin.doucha@suse.com>,
	lkft@linaro.org, lkft-triage@lists.linaro.org,
	ltp@lists.linux.it
Subject: Re: [LTP] [REGRESSION] lkft ltp for cea142b
Date: Mon, 19 Sep 2022 14:57:50 +0200	[thread overview]
Message-ID: <YyhnTtDE5Mh3w04k@pevik> (raw)
In-Reply-To: <207b6fed-27df-6d1d-113c-6f9c771cabe5@suse.cz>

> On 19. 09. 22 5:13, Petr Vorel wrote:
> > Hi all,

> > > ## Build
> > > * kernel: 5.18.19
> > > * git: https://gitlab.com/Linaro/lkft/mirrors/stable/linux-stable-rc
> > > * git branch: linux-5.18.y
> > > * git commit: 22a992953741ad79c07890d3f4104585e52ef26b
> > > * git describe: cea142b
FYI talking below about this line.

> > > * test details: https://qa-reports.linaro.org/lkft/ltp/build/cea142b

> > > ## Test Regressions (compared to 98140f3)
> > > * qemu_i386, ltp-controllers
> > >    - cpuacct_100_100

> > > * qemu_x86_64, ltp-cve
> > >    - cve-2018-1000204
> > OK, 3252ea38d ("ioctl_sg01: Add max_runtime") didn't help.

> > looking at the log [1] I don't see anything obvious why test timeouts:

> > tst_test.c:1524: TINFO: Timeout per run is 0h 00m 30s

> I do. The line above is supposed to say "Timeout per run is 1h 00m 30s"
> instead. Whatever LTP version this was, it did not have the ioctl_sg01
> max_runtime patch applied.

Hi Martin,

thanks for info. I expected the line above document LTP version, i.e.
cea142b73 ("df01.sh: Convert to TST_ALL_FILESYSTEMS=1")
which contains .max_runtime = 3600 (i.e. 1 hour runtime + 30 sec for basic
cleanup). Although "git describe" could mean any git repository.

Kind regards,
Petr

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

      reply	other threads:[~2022-09-19 12:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-17 12:00 [LTP] [REGRESSION] lkft ltp for cea142b lkft
2022-09-19  3:13 ` Petr Vorel
2022-09-19  3:27   ` Li Wang
2022-09-19  3:35     ` Li Wang
2022-09-19  8:28       ` Cyril Hrubis
2022-09-19  8:39         ` Li Wang
2022-09-19  8:50           ` Cyril Hrubis
2022-09-19  8:57   ` Martin Doucha
2022-09-19 12:57     ` 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=YyhnTtDE5Mh3w04k@pevik \
    --to=pvorel@suse.cz \
    --cc=lkft-triage@lists.linaro.org \
    --cc=lkft@linaro.org \
    --cc=ltp@lists.linux.it \
    --cc=martin.doucha@suse.com \
    --cc=mdoucha@suse.cz \
    /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.