From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Warren Date: Tue, 5 Jul 2016 16:09:46 -0600 Subject: [U-Boot] Logging SPL output with test/py In-Reply-To: References: Message-ID: <577C302A.10409@wwwdotorg.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 07/04/2016 09:40 AM, Simon Glass wrote: > Hi Stephen, > > On 3 July 2016 at 22:14, Simon Glass wrote: >> Hi Stephen, >> >> I'd like to get access to SPL output from a test. It seems that only >> the output from U-Boot proper is logged, although I cannot see why. >> >> For background, I have a new sandbox_spl target which includes SPL >> code. I will likely merge it into the normal sandbox target... >> >> It is definitely running SPL because I see the SPL console output when >> I use the -s flag to test.py. But it does not appear in test-log.html. >> >> Let me know if you have any ideas... > > It turns it it was logged, but the ANSI characters were messing up the > html due to a bug in sandbox SPL. Nothing to do with the test/py > stuff, but confusing! Odd. test/py should escape (i.e. convert to a hex representation) any non-printable (or perhaps just < 32) character code. That should have left the HTML log readable. I guess that didn't work for some reason. Is it easy to reproduce? It might be worth fixing.