Hi Tom,
On 19 December 2017 at 14:30, Tom Rini trini@konsulko.com wrote:
On Tue, Dec 19, 2017 at 02:27:06PM -0700, Simon Glass wrote:
Hi Tom,
On 19 December 2017 at 14:19, Tom Rini trini@konsulko.com wrote:
On Tue, Dec 19, 2017 at 06:30:48AM -0700, Simon Glass wrote:
Hi Tom,
Here is the remainder of my queue for u-boot-dm, including the test patches that were dropped. If any of the test patches cause a problem with your workflow, please let me know. If you would rather hold these off until next release that's fine too.
The problem is that travis doesn't (yet? I suppose we could add that into the matrix) run 'make tests' but I do. And the new binman tests don't pass, both due to dtc things: 15:56:55 FATAL ERROR: Unrecognized check name "unit_address_vs_reg"
That sounds like you need a newer dtc. I wonder if we should run the one in the U-Boot tree?
Yes, not running the one in the U-Boot tree would be a bug :)
Ah OK. Then that means that the coverage patch needs to be dropped / respun.
and utils: 15:56:58 sh: 1: coverage: not found 15:56:58 Exception: Error running 'coverage report': <type 'str'>
Yes you need the coverage tools:
To enable Python test coverage on Debian-type distributions (e.g. Ubuntu):
$ sudo apt-get install python-pip python-pytest $ sudo pip install coverage
Is this documented already somewhere? I can update my docker slaves to include python-coverage.
Yes, tools/binman/README
-- Tom
Regards, Simon