Hello all,
I've been working on getting support into Qemu for the uC5282 board recently, and today got the rtems-test tool running with this Qemu emulation for that board. The results with the first run of the full test suite since the emulation has been operational appears very promising, which is great news! However, there are a couple tests that either fail or (in the case of sptests specifically) always timeout. Included at the bottom of this email are the results of running the tests through this emulation. Dr. Bloom mentioned that some of these results could likely be due to flawed TLS implementation of m68k. Any input, guidance, or suggestions about these results (especially the tests that failed/timed out) would be really valuable to this work of getting truly reliable uC5282 emulation running! Thanks so much, Harrison Gerber <mailto:gerberh...@gmail.com> gerberh...@gmail.com TEST RESULTS: Passed: 547 Failed: 7 User Input: 6 Expected Fail: 1 Indeterminate: 0 Benchmark: 3 Timeout: 7 Test too long: 0 Invalid: 0 Wrong Version: 0 Wrong Build: 0 Wrong Tools: 0 ------------------ Total: 571 Failures: sppercpudata01.exe sptimecounter02.exe <-- Passes when run individually ttest02.exe <-- Passes when run individually sptls02.exe ts-validation-0.exe stringto01.exe dl06.exe User Input: dl10.exe fileio.exe monitor.exe capture.exe termios.exe top.exe Expected Fail: psxfenv01.exe Benchmark: whetstone.exe dhrystone.exe linpack.exe Timeouts: spinternalerror01.exe spfatal26.exe spsysinit01.exe spfatal33.exe sptimecounter01.exe spfatal12.exe spfatal09.exe Average test time: 0:00:01.901600 Testing time : 0:18:05.814003 -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
_______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
