[Fuego] LTP Test Failure on x86 Ubuntu system

[dhinakar k]

Thanks Daniel, I actually wanted to execute all ltp tests excluding those
which hangs the system. We have already marked out tests to skip. I think
the next branch has the solution for most of my issues. I will try it, by
the way when is the next release planned?

Regards,
Dhinakar

On May 29, 2017 6:24 AM, "Daniel Sangorrin" <daniel.sangorrin at toshiba.co.jp>
wrote:

> > -----Original Message-----
> > From: fuego-bounces at lists.linuxfoundation.org [mailto:
> fuego-bounces at lists.linuxfoundation.org] On Behalf Of dhinakar k
> > Sent: Saturday, May 27, 2017 4:51 AM
> > To: fuego at lists.linuxfoundation.org
> > Subject: [Fuego] LTP Test Failure on x86 Ubuntu system
> >
> > Hi,
> >
> >
> > I executed LTP test on x86 pc with TESTSPEC = default but the test is
> failing repeatedly at the same point. I have pasted the console log.
> > Please let me know what is the issue.
> >
> >
> > Fuego test_build duration=2722.49635148 seconds
>
> It seems you needed 45 minutes just to build LTP.
>
> > ##### doing fuego phase: deploy ########
> > ##### doing fuego phase: pre_deploy ########
> > ##### doing fuego phase: test_deploy ########
> > Deploying LTP
> > ##### doing fuego phase: post_deploy ########
> > ##### doing fuego phase: run ########
> > Running LTP
> > WARNING: test log file parameter empty, so will use default
> > Checking for required user/group ids
> >
> > 'nobody' user id and group found.
> > 'bin' user id and group found.
> > 'daemon' user id and group found.
> > Users group found.
> > Sys group found.
> > Required users/groups exist.
> > ltp_target_run: syscalls  | SEM  |
> > ltp_target_run: doing test syscalls
> > /tmp/hudson7562853289027513181.sh: line 10:   382 Killed
>   timeout --signal=9 100m /bin/bash
> > $FUEGO_CORE/engine/tests/${TESTDIR}/${TESTNAME}.sh
> > Build step 'Execute shell' marked build as failure
> > [description-setter] Description set: <a href="/fuego/userContent/
> fuego.logs/Functional.LTP/docker.default.3.3/testlog.txt">log</a>
> > Finished: FAILURE
>
> It seems that 100m is a bit too short for the timeout. It depends on how
> fast your hardware is.  Please change the
> timeout from 100m to something like 400m for example. You can change it
> directly on jenkins (click configure and adjust it) or
> on the testplan (in this case you have to delete the jobs and add them
> again) for example. You can also specify it directly using ftc add-jobs.
>
> Also, there may be some tests that cause hangs. For that I added skiplist
> support on the next branch. If you are using the master branch
> then you can either try with the next branch, or use top on the target and
> if you notice that a process is consuming 100% of the cpu for
> too long just kill it.
>
> Thanks,
> Daniel
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/fuego/attachments/20170529/a94d4979/attachment.html>