public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] LTP release status
Date: Mon, 16 Jan 2017 08:19:40 -0500 (EST)	[thread overview]
Message-ID: <1116838376.3405880.1484572780617.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170116130237.GA26610@rei.lan>



----- Original Message -----
> From: "Cyril Hrubis" <chrubis@suse.cz>
> To: "Jan Stancek" <jstancek@redhat.com>
> Cc: ltp@lists.linux.it
> Sent: Monday, 16 January, 2017 2:02:38 PM
> Subject: Re: [LTP] LTP release status
> 
> Hi!
> > > > Couple more days would be great. I'll try to schedule tests on various
> > > > RHELs
> > > > tomorrow, but some reserve would be nice to have.
> > > 
> > > Okay then, just let me know once we are ready.
> > 
> > Looks good over here, I've been running tests on RHEL6.2 up to 7.3,
> > plus a RHEL7.3 with recent upstream kernel.
> > 
> > I found only 2 problems (and sent 2 patches) for:
> > - tst_resm_hexd
> > - quotactl01 on big endian systems
> 
> Good. I've acked these two already.
> 
> And also pushed the fix for unprobable munmap_2-1 failure from Richie
> since I'm pretty sure that it will not break anything and that it fixes
> real segfaults.
> 
> I have one more problem, zram01 fails on ppc64le since minimal btrfs
> size there is larger due to larger page size. I think that I may be able
> to parse mkfs.btrfs output to get the minimal size and adjust the size
> of the zram device in the test setup but I consider this too risky for
> the release.

I recall running into something similar in one non-LTP test.
I had to bump (back in 2013) ramdisk (brd) size to 384M on ppc systems.

> 
> So I guess I should tag the git and write the release notes once you
> push your patches, okay?

Fine by me. I'm going to look at pushing those 2 patches.

Regards,
Jan

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

  reply	other threads:[~2017-01-16 13:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-12 14:28 [LTP] LTP release status Cyril Hrubis
2017-01-12 14:58 ` Jan Stancek
2017-01-12 15:39   ` Cyril Hrubis
2017-01-16 12:51     ` Jan Stancek
2017-01-16 13:02       ` Cyril Hrubis
2017-01-16 13:19         ` Jan Stancek [this message]
2017-01-16 13:30           ` Cyril Hrubis
2017-01-16 14:09             ` Jan Stancek
2017-01-16 14:13               ` Cyril Hrubis
2017-01-16 14:45                 ` Jan Stancek
2017-01-16 14:46                   ` Cyril Hrubis
2017-01-16 15:25               ` Eryu Guan
2017-01-16 15:31                 ` Cyril Hrubis
2017-01-16 15:46                   ` Eryu Guan
2017-01-16 15:40                 ` Jan Stancek
2017-01-13 11:08 ` Alexey Kodanev
  -- strict thread matches above, loose matches on Subject: below --
2016-01-14 18:46 Cyril Hrubis

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=1116838376.3405880.1484572780617.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