On 18/05/2014 9:52 pm, Kumar Amit Mehta wrote:
On Sat, May 17, 2014 at 09:27:37AM -0500, Joel Sherrill wrote:
Post results for what you have and we can comment.
<snip>
RTEMS Testing - Tester, v0.2.0
Command Line: ./rtems-test --log=log_sis_run --rtems-bsp=sis-run
--rtems-tools=/home/rtems/development/rtems/4.11
/home/rtems/development/rtems/kernel/sis
Python: 2.6.6 (r266:84292, Sep 11 2012, 08:28:27) [GCC 4.4.6 20120305
(Red Hat 4.4.6-4)]
.....
....
Passed: 492
Failed: 1
Timeouts: 1
Invalid: 0
-------------
Total: 494
Failures:
sp2038.exe
Timeouts:
pppd.exe
Testing time: 0:24:37.792244
<snip>
<Failures>
[286/494] p:284 f:0 t:1 i:0 | sparc/sis: sp2038.exe
run: /home/rtems/development/rtems/4.11/bin/sparc-rtems4.11-run -a
-nouartrx
/home/rtems/development/rtems/kernel/sis/sparc-rtems4.11/c/sis/testsuites/sptests/sp2038/sp2038.exe
] unknown option -nouartrx
]
]
] *** BEGIN OF TEST SP 2038 ***
]
../../../../../../../rtems.git/c/src/../../testsuites/sptests/sp2038/init.c:
269 memcmp(&now, problem, sizeof(now)) == 0
Result: failed Time: 0:00:01.045045
<Failures>
I thought this one was fixed. I am not seeing a failure with it.
<timeout>
[264/494] p:263 f:0 t:0 i:0 | sparc/sis: pppd.exe
run: /home/rtems/development/rtems/4.11/bin/sparc-rtems4.11-run -a
-nouartrx
/home/rtems/development/rtems/kernel/sis/sparc-rtems4.11/c/sis/testsuites/samples/pppd/pppd.exe
] unknown option -nouartrx
]
]
] *** BEGIN OF TEST PPPD ***
] pppd: In secrets file: unrecognized option '/dev/ttyS1'
] Serial connection established.
] ioctl(TIOCGETD): Bad file number
] ioctl(TIOCSETD): Bad file number
] ioctl(PPPIOCGUNIT): Bad file number
] Couldn't set device to non-blocking mode: Bad file number
] *** TIMEOUT TIMEOUT
<timeout>
This test is interactive and needs to be patched with a key a hit to
start like some of the other interactive tests.
In an organization, where I have worked before, somebody setup
jenkins[1] for building, invoking test and notification through email.
Great to hear continuous integration being used.
Maybe same, can be implemented for rtems tests too.
[1] http://jenkins-ci.org/
We will use buildbot. It is something Amar knows well as he is involved
in the buildbot project.
Chris
_______________________________________________
rtems-devel mailing list
rtems-devel@rtems.org
http://www.rtems.org/mailman/listinfo/rtems-devel
