build.kde.org and `ping`
David Faure
faure at kde.org
Sat Nov 2 23:51:59 UTC 2013
On Sunday 03 November 2013 12:42:24 Ben Cooksley wrote:
> On Sun, Nov 3, 2013 at 12:27 PM, David Faure <faure at kde.org> wrote:
> > This error:
> >
> > http://build.kde.org/job/kdelibs_stable/886/testReport/(root)/TestSuite/kp
> > typrocesstest/
> >
> > is caused by this:
> >
> > jenkins at slave1:/srv/jenkins/workspace/kdelibs_master/build> ping -i 0.5
> > localhost
> > ping: icmp open socket: Operation not permitted
> >
> > because the code is doing exactly this:
> >
> > void KPtyProcessTest::test_suspend_pty()
> > {
> >
> > KPtyProcess p;
> > p.setPtyChannels(KPtyProcess::AllChannels);
> > p.setProgram("ping", QStringList() << "-i" << "0.5" << "localhost");
> > p.start();
> >
> > // verify that data is available to read from the pty
> > QVERIFY(p.pty()->waitForReadyRead(1500));
> >
> > [...]
> >
> >
> > Should we
> > 1) change build.kde.org's setup to allow running ping?
> > 2) write a helper program to replace ping? [sounds like the correct
> > solution, but
> >
> > needs a volunteer, since this kpty stuff isn't really maintained
> > anymore]
> >
> > 3) skip the test when that first check fails?
>
> It should already have been allowing ping to run - I have just conducted
> some tests and it seems to work fine. I have reinstalled the "iputils"
> package on slave1 however just in case.
>
> Can you please retest?
Yep, now running ping as the jenkins user works, thanks!
I've triggered a new kdelibs_stable build, we'll see if it goes back to green.
--
David Faure, faure at kde.org, http://www.davidfaure.fr
Working on KDE, in particular KDE Frameworks 5
More information about the Kde-frameworks-devel
mailing list