All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ilya Dryomov <idryomov@gmail.com>
To: Yuri Weinstein <yweinste@redhat.com>
Cc: "Development, Ceph" <ceph-devel@vger.kernel.org>
Subject: Re: Jewel 10.2.7 QE status
Date: Thu, 6 Apr 2017 11:28:15 +0200	[thread overview]
Message-ID: <CAOi1vP-TZog6Hb+ZKehmrU_cR534TQER1xUh0+KEZ+YZfXAyuA@mail.gmail.com> (raw)
In-Reply-To: <CAMMFjmH_DTdeQDB-C4+A7KsUyAF0jxsZRyGn-2drEOxFds7jsw@mail.gmail.com>

On Wed, Apr 5, 2017 at 10:16 PM, Yuri Weinstein <yweinste@redhat.com> wrote:
> Detailed summary of the QE Validation can be found here
> http://tracker.ceph.com/issues/19055#note-13
> The following suites were in scope of this point release validation:
>
> rados (subset 35/50 227 jobceph-ansibles)
> rbd
> rgw
> fs
> krbd
> kcephfs
> knfs
> rest
> hadoop - EXCLUDED
> samba - EXCLUDED
> ceph-deploy
> ceph-disk
> upgrade/client-upgrade
> upgrade/hammer-x (jewel)
> upgrade/jewel-x/point-to-point-x
> powercycle
> ceph-ansible
>
> (please let me know if any suites are missing from this ^ list)
>
> =====================
> Outstanding issues
>
> rados - two jobs failed, need Josh's approval
> krbd - seems similar to previous release, need Ilya's approval

The first two failed to compile ltp, both on 7.3 and 16.04:

smithi022.stderr:/tmp/ccHOwwst.o: In function `doio_fprintf':
smithi022.stderr:/home/ubuntu/cephtest/xfstests/ltp/doio.c:2410:
undefined reference to `va_start'
smithi022.stderr:/home/ubuntu/cephtest/xfstests/ltp/doio.c:2414:
undefined reference to `va_end'
smithi022.stderr:collect2: error: ld returned 1 exit status
smithi022.stderr:gmake[3]: *** [doio] Error 1
smithi022.stderr:gmake[3]: *** Waiting for unfinished jobs....

The rerun on 14.04 succeeded -- need to look into that.

Approved.

Thanks,

                Ilya

      parent reply	other threads:[~2017-04-06  9:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-05 20:16 Jewel 10.2.7 QE status Yuri Weinstein
2017-04-05 21:55 ` Yuri Weinstein
2017-04-06 16:23   ` Ken Dreyer
2017-04-06 17:32     ` Josh Durgin
2017-04-06  9:28 ` Ilya Dryomov [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=CAOi1vP-TZog6Hb+ZKehmrU_cR534TQER1xUh0+KEZ+YZfXAyuA@mail.gmail.com \
    --to=idryomov@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=yweinste@redhat.com \
    /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.