All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Cyril Hrubis <chrubis@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] tst_test.sh: Fix missing cleanup run from setup
Date: Fri, 30 Sep 2022 16:51:45 +0200	[thread overview]
Message-ID: <YzcCgVovivI+lAPy@pevik> (raw)
In-Reply-To: <Yzb/WiPvCDvv8A36@yuki>

> Hi!
> > > I rerun whole LTP tests on 3 SLES versions, most of the shell tests on
> > > Tumbleweed, I'll also try some shell tests on some Debian version.
> > > Also CI passed (which runs make test-shell), + I run make test-shell manually
> > > (covers more than CI), but that's not that relevant as we don't cover much.

> > Tests results looks ok, looked into the output (not just the exit code),
> > thus I merged this. This should be the last commit, we can tag the release and
> > the rest of the release process.

> Sounds good to me. Feel free to tag the git, you signed for generating
> and uploading the tarballs anyway. I'm preparing release notes and send
> them once tarballs are uploaded on github.

Hi Cyril,

Right, LTP version updated and tagged, both with my GPG sign.
https://github.com/linux-test-project/ltp/commit/b763f81998f19f783982d3937d1fd05bcf649c16

I generated LTP 20220930 release:
https://github.com/linux-test-project/ltp/releases/tag/20220930

Please send release notes, I'll add them to the releases page in github.

Kind regards,
Petr

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

      reply	other threads:[~2022-09-30 14:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 11:24 [LTP] [PATCH 1/1] tst_test.sh: Fix missing cleanup run from setup Petr Vorel
2022-09-30 11:30 ` Petr Vorel
2022-09-30 11:41 ` Cyril Hrubis
2022-09-30 12:05   ` Petr Vorel
2022-09-30 14:27     ` Petr Vorel
2022-09-30 14:38       ` Cyril Hrubis
2022-09-30 14:51         ` 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=YzcCgVovivI+lAPy@pevik \
    --to=pvorel@suse.cz \
    --cc=chrubis@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 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.