I got the test to run but there were tons of errors. I haven't touched any of the source or really dived into it.
RTEMS Testing - Tester, 5.0.not_released Command Line: /home/zakonrockets/development/rtems/5/bin/rtems-test --rtems-tools=/home/zakonrockets/development/rtems/5 --rtems-bsp=pc-qemu /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites --rtems-prefix=/home/zakonrockets/development/rtems/5 Host: Linux zakonrockets-Inspiron-15-7000-Gaming 5.3.0-64-generic #58-Ubuntu SMP Fri Jul 10 19:33:51 UTC 2020 x86_64 Python: 3.7.5 (default, Apr 19 2020, 20:18:17) [GCC 9.2.1 20191008] Host: Linux-5.3.0-64-generic-x86_64-with-Ubuntu-19.10-eoan (Linux zakonrockets-Inspiron-15-7000-Gaming 5.3.0-64-generic #58-Ubuntu SMP Fri Jul 10 19:33:51 UTC 2020 x86_64 x86_64) [ 3/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 | i386/pc686: cdtest.exe [ 6/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 | i386/pc686: hello.exe [ 4/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 | i386/pc686: cxx_iostream.exe error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/hello.exe: exit-code:2 error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/hello.exe: exit-code:2 error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/cxx_iostream.exe: exit-code:2 error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/cdtest.exe: exit-code:2 error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/cxx_iostream.exe: exit-code:2 warning: switched to dry run due to errors error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/cdtest.exe: exit-code:2 warning: switched to dry run due to errors warning: switched to dry run due to errors [ 2/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:3 W:0 | i386/pc686: capture.exe [ 8/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:3 W:0 | i386/pc686: minimum.exe error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/capture.exe: exit-code:2 error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/capture.exe: exit-code:2 warning: switched to dry run due to errors [ 7/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:4 W:0 | i386/pc686: loopback.exe [ 1/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:4 W:0 | i386/pc686: base_sp.exe error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/minimum.exe: exit-code:2 error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/minimum.exe: exit-code:2 warning: switched to dry run due to errors [ 5/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:4 W:0 | i386/pc686: fileio.exe error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/loopback.exe: exit-code:2 error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/loopback.exe: exit-code:2 warning: switched to dry run due to errors error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/base_sp.exe: exit-code:2 error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/base_sp.exe: exit-code:2 warning: switched to dry run due to errors error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/fileio.exe: exit-code:2 error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/fileio.exe: exit-code:2 warning: switched to dry run due to errors [ 1/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:4 W:0 | i386/pc686: base_sp.exe Result: invalid Time: 0:00:00.017795 base_sp.exe => run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/base_sp.exe [ 2/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:3 W:0 | i386/pc686: capture.exe Result: invalid Time: 0:00:00.014453 capture.exe => run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/capture.exe [ 3/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 | i386/pc686: cdtest.exe Result: invalid Time: 0:00:00.054058 cdtest.exe => run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/cdtest.exe [ 4/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 | i386/pc686: cxx_iostream.exe Result: invalid Time: 0:00:00.026283 cxx_iostream.exe => run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/cxx_iostream.exe [ 5/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:4 W:0 | i386/pc686: fileio.exe Result: invalid Time: 0:00:00.010072 fileio.exe => run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/fileio.exe [ 6/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:0 W:0 | i386/pc686: hello.exe Result: invalid Time: 0:00:00.035287 hello.exe => run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/hello.exe [ 7/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:4 W:0 | i386/pc686: loopback.exe Result: invalid Time: 0:00:00.029105 loopback.exe => run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/loopback.exe [ 8/13] p:0 f:0 u:0 e:0 I:0 B:0 t:0 i:3 W:0 | i386/pc686: minimum.exe [10/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:7 W:0 | i386/pc686: paranoia.exe error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/paranoia.exe: exit-code:2 error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/paranoia.exe: exit-code:2 warning: switched to dry run due to errors [13/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:8 W:0 | i386/pc686: unlimited.exe error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/unlimited.exe: exit-code:2 error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/unlimited.exe: exit-code:2 warning: switched to dry run due to errors [11/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:9 W:0 | i386/pc686: pppd.exe [12/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:9 W:0 | i386/pc686: ticker.exe error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/pppd.exe: exit-code:2 error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/pppd.exe: exit-code:2 warning: switched to dry run due to errors error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/ticker.exe: exit-code:2 error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/ticker.exe: exit-code:2 warning: switched to dry run due to errors [ 9/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:11 W:0 | i386/pc686: nsecs.exe error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/nsecs.exe: exit-code:2 error: qemu.cfg:85: execute failed: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/nsecs.exe: exit-code:2 warning: switched to dry run due to errors [ 9/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:11 W:0 | i386/pc686: nsecs.exe Result: invalid Time: 0:00:00.004524 nsecs.exe => run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/nsecs.exe [10/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:7 W:0 | i386/pc686: paranoia.exe Result: invalid Time: 0:00:00.006776 paranoia.exe => run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/paranoia.exe [11/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:9 W:0 | i386/pc686: pppd.exe Result: invalid Time: 0:00:00.018013 pppd.exe => run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/pppd.exe [12/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:9 W:0 | i386/pc686: ticker.exe Result: invalid Time: 0:00:00.008560 ticker.exe => run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/ticker.exe [13/13] p:1 f:0 u:0 e:0 I:0 B:0 t:0 i:8 W:0 | i386/pc686: unlimited.exe Result: invalid Time: 0:00:00.006357 unlimited.exe => run: qemu-system-i386 -no-reboot -nographic -monitor none -serial stdio -append --console=/dev/com1 -kernel /home/zakonrockets/development/rtems/kernels-5/pcp-386/i386-rtems5/c/pc386/testsuites/samples/unlimited.exe Passed: 1 Failed: 0 User Input: 0 Expected Fail: 0 Indeterminate: 0 Benchmark: 0 Timeout: 0 Invalid: 12 Wrong Version: 0 Wrong Build: 0 Wrong Tools: 0 ----------------- Total: 13 Invalid: cdtest.exe hello.exe cxx_iostream.exe capture.exe loopback.exe base_sp.exe fileio.exe paranoia.exe unlimited.exe pppd.exe ticker.exe nsecs.exe Average test time: 0:00:00.060904 Testing time : 0:00:00.791756 regards zack Il giorno lun 10 ago 2020 alle ore 21:51 Vijay Kumar Banerjee < vi...@rtems.org> ha scritto: > On Tue, Aug 11, 2020 at 7:14 AM Zacchaeus Liang <zliang...@gmail.com> > wrote: > > > > Do i add it as an argument and what is the argument name (didn't reply > all sorry? > > > You don't need a separate option just add the location with the > command line you're using. Something like this: > > rtems-test \ > --rtems-tools=$HOME/development/rtems/5 \ > --rtems-bsp=lpc-qemu \ > $HOME/development/rtems/kernel/pc386/i386-rtems5/c/pc386/testsuites/samples > > > Thanks > > zack > > > > Il giorno lun 10 ago 2020 alle ore 21:31 Vijay Kumar Banerjee < > vi...@rtems.org> ha scritto: > >> > >> On Tue, Aug 11, 2020 at 6:57 AM Zacchaeus Liang <zliang...@gmail.com> > wrote: > >> > > >> > It says that there is not supplied executable > >> Looks like you're in the right direction. > >> > >> Add the location to the samples directory to the command line and > >> it'll work. The location will be in the bsp build location. > >> something like pc-386/i386-rtems5/c/pc386/testsuites/samples > >> > >> > >> Best regards, > >> Vijay > >> > zack > >> > > >> > Il giorno lun 10 ago 2020 alle ore 21:10 Vijay Kumar Banerjee < > vi...@rtems.org> ha scritto: > >> >> > >> >> Hi Zack, > >> >> > >> >> I have posted a comment below... > >> >> > >> >> On Tue, Aug 11, 2020 at 5:54 AM Zacchaeus Liang <zliang...@gmail.com> > wrote: > >> >> > > >> >> > I tried to add the prefix and i had the prefix with this > >> >> > rtems-test --rtems-bsp=i386-rtems5 > --rtems-tools=$HOME/development/rtems/5 > --rtems-prefix=$HOME/development/rtems/5 > >> >> > i get the same error. Was the prefix correct based on the > instructions? > >> >> > > >> >> > Thanks > >> >> > zack > >> >> > > >> >> > Il giorno lun 10 ago 2020 alle ore 00:31 Niteesh G. S. < > niteesh...@gmail.com> ha scritto: > >> >> >> > >> >> >> Hello, > >> >> >> > >> >> >>> > >> >> >>> Hello, > >> >> >>> > >> >> >>> I'm Zack and I'm currently finishing up my university degree in > comp sci. > >> >> >>> I'm really interested in aviation and aerospace systems. I want > to get into > >> >> >>> rtems to learn more about rtos and contribute to rtems ! > >> >> >>> > >> >> >>> Currently I'm trying to build rtems and test and bsp. Hoping to > then > >> >> >>> contribute. I followed one of you GSOC student's tutorials and > tried to go > >> >> >>> ahead. I'm trying to build the test the bsp right now. > >> >> >>> here is his blog post > >> >> >>> > https://medium.com/@mritunjaysharma394/installing-rtems-ecosystem-and-building-your-first-bsp-993d1cf38902 > >> >> >>> I tried to run the bsp testing like this and it says the ini > file is not > >> >> >>> found. Is this the right bsp argument? After this i'm going to > try to > >> >> >>> build an application and would like to know the right path to > install it. > >> >> >>> Any tips on looking for easy things to learn to patch? Thanks in > advance i > >> >> >>> know it's a handful for questions! > >> >> >>> > >> >> >>> > >> >> >>> > >> >> >>> zakonrockets@zakonrockets-Inspiron-15-7000-Gaming > :~/development/rtems/kernels-5/pcp-386$ > >> >> >>> rtems-test --rtems-bsp=i386-rtems5 > >> >> >>> --rtems-tools=$HOME/development/rtems/5 > >> >> >>> RTEMS Testing - Tester, 5.0.not_released > >> >> >>> Command Line: > /home/zakonrockets/development/rtems/5/bin/rtems-test > >> >> >>> --rtems-bsp=i386-rtems5 > >> >> > >> >> --rtems-bsp option should have the bsp and not the architecture. > >> >> Please try --rtems-bsp=pc-qemu >
_______________________________________________ users mailing list users@rtems.org http://lists.rtems.org/mailman/listinfo/users
