Linux Test Project
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] LTP pre-release testing and freeze
Date: Thu, 28 Apr 2016 06:25:13 -0400 (EDT)	[thread overview]
Message-ID: <1728203866.1199576.1461839113790.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20160420143031.GB4004@rei>



----- Original Message -----
> From: "Cyril Hrubis" <chrubis@suse.cz>
> To: ltp@lists.linux.it
> Sent: Wednesday, 20 April, 2016 4:30:31 PM
> Subject: [LTP] LTP pre-release testing and freeze
> 
> Hi!
> Are we ready for the git repository freeze and pre-release testing?
> 
> Are there any patches that were not reviewed/pushed yet that should be
> part of the next release?
> 
> Ideally I would like to proceed with the freeze at the end of this week
> then have at least a week for running the tests and if everything goes
> well the release would be carried on end of April or beginning of May.
> Does that sound reasonable?

Looks good from my side. I ran the usual set we use as smoke test
(syscalls, selection of mem/io/etc.) on
  RHEL6.2 through RHEL6.8 (i386, x86_64, ppc64, s390x)
  RHEL7.0 through RHEL7.2 (x86_64, ppc64, ppc64le, s390x, aarch64)
and ran mostly into known bugs in kernel / glibc.

Other than known issues, there were couple failures to note:

epoll_wait02
There is a tolerance, but it goes only one way (oversleep).
I occasionally see it waking up a ms earlier and then testcase
reports it as failure. This was new addition, so there are
no historical data for comparison.

personality01
PER_LINUX32 is masked on powerpc as PER_LINUX, so this
always fails.

arch/powerpc/kernel/syscalls.c:
long ppc64_personality(unsigned long personality)
{
        long ret;

        if (personality(current->personality) == PER_LINUX32
            && personality(personality) == PER_LINUX)
                personality = (personality & ~PER_MASK) | PER_LINUX32;
        ret = sys_personality(personality);
        if (personality(ret) == PER_LINUX32)
                ret = (ret & ~PER_MASK) | PER_LINUX;
        return ret;
}

Regards,
Jan

> 
> --
> Cyril Hrubis
> chrubis@suse.cz
> 
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
> 

  reply	other threads:[~2016-04-28 10:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20 14:30 [LTP] LTP pre-release testing and freeze Cyril Hrubis
2016-04-28 10:25 ` Jan Stancek [this message]
2016-04-28 12:26   ` Cyril Hrubis
2016-05-02  9:10     ` Jan Stancek
2016-05-02  9:45       ` Cyril Hrubis
2016-05-02 10:06         ` Jan Stancek

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=1728203866.1199576.1461839113790.JavaMail.zimbra@redhat.com \
    --to=jstancek@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox