On Wed, 2023-12-20 at 09:53 +0000, Alex Bennée wrote: > Richard Purdie <[email protected]> writes: > > > On Tue, 2023-12-19 at 16:44 +0000, Alex Bennée wrote: > > > Richard Purdie <[email protected]> writes: > > > Yeah I'm only seeing A10/A11: > > > > > > o regression_1010.5 Invalid memory access 5 > > > regression_1010.5 OK > > > o regression_1010.6 Invalid memory access 6 > > > > > > WARNING: here A10 > > > WARNING: here A11 > > > WARNING: here A10 > > > WARNING: here A11 > > > WARNING: here A10 > > > WARNING: here A11 > > > WARNING: here A10 > > > WARNING: here A11 > > > WARNING: here A10 > > > WARNING: here A11 > > > WARNING: here A10 > > > WARNING: here A11 > > > WARNING: here A10 > > > WARNING: here A11 > > > WARNING: here A10 > > > WARNING: here A11 > > > WARNING: here A10 > > > WARNING: here A11 > > > WARNING: here A10 > > > WARNING: here A11 > > > NOTE: ... FAIL > > > DEBUG: Removed SIGALRM handler > > > Traceback (most recent call last): > > > File > > > "/home/alex/lsrc/tests/trs/build/../poky/meta/lib/oeqa/core/decorator/__init__.py", > > > line 35, in wrapped_f > > > return func(*args, **kwargs) > > > ^^^^^^^^^^^^^^^^^^^^^ > > > File > > > "/home/alex/lsrc/tests/trs/build/../poky/meta/lib/oeqa/core/decorator/__init__.py", > > > line 35, in wrapped_f > > > return func(*args, **kwargs) > > > ^^^^^^^^^^^^^^^^^^^^^ > > > File > > > "/home/alex/lsrc/tests/trs/meta-trs/lib/oeqa/runtime/cases/opteetest.py", > > > line 27, in test_opteetest_xtest > > > self.assertEqual(status, 0, msg='\n'.join([cmd, output])) > > > AssertionError: 255 != 0 : xtest > > > Run test suite with level=0 > > > > How long does it take for the test data to "back up" and timeout? The > > logging thread should take a maximum of 2s to notice data not being > > read/handled on the serial port. > > I don't think it goes around the logging loop more than once. I only > see: > > grep "got" > build/tmp_trs-qemuarm64/work/trs_qemuarm64-trs-linux/trs-image/1.0/temp/log.do_testimage > DEBUG: got [(12, 1)] > > from the poll. > > > > > What the code should be doing is noticing the run_serial function isn't > > using the port and if there is data there, reading it in the logging > > thread. You could put further warnings around the code there to see if > > it ever detects data to read on that port. A warning when it exits the > > run_serial command may help too to see if it is waiting for data there > > or not. > > > > I also ended up using: > > > > https://git.yoctoproject.org/poky-contrib/commit/?h=rpurdie/t222&id=febb0d892e4c3648cd88b8ecb9c0260edc45b68e > > > > to show what was going over the serial interface when I found it wasn't > > what I expected. > > I'll keep digging.
I've merged the patches into master since they are helping the stdout issue and helped a number of issues others were seeing. In the final version of the patch I did fix an issue where the exception handling from the thread was not working so well, it does at least print a, exception/traceback properly now (in threadtarget()). One of the reasons I asked about the warnings was in case that was showing an issue, previously it silently failed. I can believe there are other issues hiding in here :/. Cheers, Richard
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#192786): https://lists.openembedded.org/g/openembedded-core/message/192786 Mute This Topic: https://lists.openembedded.org/mt/103244415/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
