On 21/03/2017 18:06, Tanu Hari Dixit wrote:
Also, how can we change the number of cores operational? I found the
--timeout option but none regarding the cores.
Have a look at the `--jobs` option (try --help). The option is the same
as the RSB and has its name. Maybe not the best name in this
On Tue, Mar 21, 2017 at 1:38 PM, Tanu Hari Dixit
wrote:
> Hello Chris, All,
>
> Regarding the ticket https://devel.rtems.org/ticket/2946
> for the test spcontext01 do we need to add a tag in a new .tcfg file ?
> If so what would be the name of the tcfg file?
>
>
This is Chris' to answer.
> Als
Hello Chris, All,
Regarding the ticket https://devel.rtems.org/ticket/2946
for the test spcontext01 do we need to add a tag in a new .tcfg file ?
If so what would be the name of the tcfg file?
Also, can you please help me investigate why 5 more test fail?
Thanks,
Tanu Hari Dixit.
On Tue, Mar 2
> I noticed you have 17 tests more than I do enabled. How did you configure?
../../rtems/configure --target=sparc-rtems4.12 --enable-tests
--enable-rtemsbsp=erc32
--prefix=/home/thd/development/rtems/install_path_erc32_alltest_new
I used Joel's configuration, that is:
../../rtems/configure --targ
On 20/03/2017 17:20, Sebastian Huber wrote:
On 18/03/17 21:52, Joel Sherrill wrote:
FWIW here are my results for sparc/erc32:
Passed: 548
Failed: 1
Timeouts: 5
Invalid:0
-
Total:554
Failures:
spcontext01.exe
Yes, this is expected.
Timeouts:
fileio.exe
top.
On 18/03/17 21:52, Joel Sherrill wrote:
FWIW here are my results for sparc/erc32:
Passed: 548
Failed: 1
Timeouts: 5
Invalid:0
-
Total:554
Failures:
spcontext01.exe
Yes, this is expected.
Timeouts:
fileio.exe
top.exe
termios.exe
capture.exe
monitor.exe
On 19/03/2017 07:52, Joel Sherrill wrote:
That is much better than yours and is really only the known
spcontext01.exe failure.
Please tag the test as expected-fail.
Thanks
Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/
On Sat, Mar 18, 2017 at 9:00 AM, Joel Sherrill wrote:
> These are all long running tests. Gedare is on a new computer which I
> assume is quite fast. So he has fewer timeouts.
>
> I am out of town but can try to remember to use tsim to get the running
> time for some of these in real CPU time. My
These are all long running tests. Gedare is on a new computer which I
assume is quite fast. So he has fewer timeouts.
I am out of town but can try to remember to use tsim to get the running
time for some of these in real CPU time. My recollection is that crypt01
takes a long time compared to other
Gedare,
By erc32 under gdb do you mean using --debug-trace=gdb option with rtems-test ?
I ran a normal
./rtems-test --log=log_erc32_run_alltest_new --rtems-bsp=erc32-run
--rtems-tools=$HOME/development/rtems/4.12
/home/thd/development/rtems/src/builds/b-erc32_allt/sparc-rtems4.12/c/erc32/testsuite
On 18/3/17 11:46 am, Gedare Bloom wrote:
> I just ran tests and observe the following on erc32 under gdb, can
> anyone confirm/replicate the timeouts and failure, and know why this
> is happening?
How many cores are you using with rtems-test and so how many tests are
running in parallel? This can
11 matches
Mail list logo
