build.kde.org and `ping`

Ben Cooksley bcooksley at kde.org
Sat Nov 2 23:42:24 UTC 2013


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/kptyprocesstest/
>
> 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?


> --
> David Faure, faure at kde.org, http://www.davidfaure.fr
> Working on KDE, in particular KDE Frameworks 5
>
>
Thanks,
Ben
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20131103/f80504e2/attachment.html>


More information about the Kde-frameworks-devel mailing list