public inbox for gentoo-powerpc@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Anthony G. Basile" <basile@opensource.dyc.edu>
To: gentoo-powerpc@lists.gentoo.org
Subject: Re: [gentoo-powerpc] Re: osuosl openstack power8 powerpc64le for gentoo
Date: Wed, 20 Apr 2016 04:24:08 -0400	[thread overview]
Message-ID: <57173CA8.3000607@opensource.dyc.edu> (raw)
In-Reply-To: <CAGQVrL8SivYf+LkLocva_H4PHP9q1=M4sWbzrLzDAtE7DewSTA@mail.gmail.com>

On 4/19/16 10:31 PM, Leno Hou wrote:
> So currently I'll put the package.accept_keywords into /etc/portage. How to
> arch testing for keywords and stablereq?
> Did we have auto test framework for arch testing in Gentoo Community?  For
> example, Linux Test Project <https://linux-test-project.github.io>( abbrev.
> LTP)
> If we have some test strategy, anything could I help for this ?

you open a bug report and request that a package be keyworded and/or
stablelized and you cc the ppc64 team.  if packages are related you can
open one bug for each

this has nothing to do with the LTP.  That's for testing the kernel and
libc, not for arch testing.  you're confusing two different types of
testing.  package is only marked stable on ppc64 if it, and all its
dependencies work in gentoo.

finally the QA issues can't just be ignored.  if they are false
positives then you identify them as such and act accordingly.  but you
cant just ignore them, eg, if there are missing deps or unstable deps
for a stable pkg, then those QA results much be addressed.

-- 
Anthony G. Basile, Ph. D.
Chair of Information Technology
D'Youville College
Buffalo, NY 14201
(716) 829-8197


  reply	other threads:[~2016-04-20  8:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <56AAA483.6020403@gentoo.org>
2016-01-29 10:23 ` [gentoo-powerpc] Re: osuosl openstack power8 powerpc64le for gentoo Kevin Zhao
     [not found]   ` <CAK=rqNt31T9eygiQDJs6yVa7QvLAqkW4EKSgegmu_O_6cKO4ug@mail.gmail.com>
     [not found]     ` <56F3D3ED.1030702@gentoo.org>
     [not found]       ` <CAK=rqNuf-xapACSpEmNwvnKYfJLQBnzBpgt=FTkq4v+ii2Nh8g@mail.gmail.com>
     [not found]         ` <56F69C92.9010604@gentoo.org>
2016-04-19 10:11           ` Leno Hou
     [not found]             ` <5716097B.2040406@gentoo.org>
2016-04-20  2:31               ` Leno Hou
2016-04-20  8:24                 ` Anthony G. Basile [this message]
2016-04-20 11:22                   ` Leno Hou

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=57173CA8.3000607@opensource.dyc.edu \
    --to=basile@opensource.dyc.edu \
    --cc=gentoo-powerpc@lists.gentoo.org \
    /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