Mark expected failures as such in testbench output
applied in r45366
Should not indeed - however, to avoid this we'd have to add extra clipping code to very performance criticial code (the crt emulator), only to fix it for some super uncommon, and mostly pointless, usecase. I'd rather leave it as is - Palettes will be removed alltogether some day in the future anyway.
print expected errors and timeouts in green, and unexpected ok in red. patch by Christian Bauer
good idea! btw, you can also use the maketable tool to produce a somewhat better report, it can also be used compare with previous results and only show the differences
Add Frodo support to testbench
Great - applied in r45365 Would be nice if you could add some option to Frodo so it starts minimized (or even headless), that would make it much more convenient (testbench can run in background while doing other things)
added support for Frodo, patch by Christian Bauer