From: Ruediger Meier <sweet_f_a@gmx.de>
To: Karel Zak <kzak@redhat.com>
Cc: Bernhard Voelker <mail@bernhard-voelker.de>, util-linux@vger.kernel.org
Subject: Re: sfdisk, latest fixes break ppc64
Date: Wed, 22 Apr 2015 18:10:46 +0200 [thread overview]
Message-ID: <201504221810.47262.sweet_f_a@gmx.de> (raw)
In-Reply-To: <20150422154656.GG27969@ws.net.home>
On Wednesday 22 April 2015 at 17:46, you wrote:
> We already use
>
> https://drone.io/github.com/karelzak/util-linux
>
> and
>
> https://travis-ci.org/karelzak/util-linux
>
> both connected to github, but for ppc64 and s390 I use machines in
> Red Hat labs and during -rc1 I usually use Coverity analyzer.
>
> It's also possible to use Fedora/Suse build farms, but we don't
> execute all the tests (especially tests where is necessary root
> perms) by default.
You can get root permission there with such a trick "root4abuild" rpm
https://build.opensuse.org/package/view_file/home:rudi_m/root4abuild/root4abuild.spec?expand=1
BTW we could also add some more non-root tests. For example it's very
easy to duplicate most *fdisk checks to use simple files additionally
to loop devices only.
> Anyway, this is no problem, the problem is real life testing.
> Fortunately, I can push unstable stuff to Fedora Rawhide :)
cu,
Rudi
next prev parent reply other threads:[~2015-04-22 16:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 10:34 sfdisk, latest fixes break ppc64 Ruediger Meier
2015-04-22 10:13 ` Karel Zak
2015-04-22 10:42 ` Ruediger Meier
2015-04-22 13:28 ` Karel Zak
2015-04-22 14:20 ` Ruediger Meier
2015-04-22 14:50 ` Bernhard Voelker
2015-04-22 15:46 ` Karel Zak
2015-04-22 16:10 ` Ruediger Meier [this message]
2015-04-22 16:02 ` Ruediger Meier
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=201504221810.47262.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=kzak@redhat.com \
--cc=mail@bernhard-voelker.de \
--cc=util-linux@vger.kernel.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