From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rini Date: Tue, 19 Dec 2017 16:30:34 -0500 Subject: [U-Boot] Please pull u-boot-dm In-Reply-To: References: <20171219211925.GO14220@bill-the-cat> Message-ID: <20171219213034.GQ14220@bill-the-cat> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Tue, Dec 19, 2017 at 02:27:06PM -0700, Simon Glass wrote: > Hi Tom, > > On 19 December 2017 at 14:19, Tom Rini 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 :) > > and utils: > > 15:56:58 sh: 1: coverage: not found > > 15:56:58 Exception: Error running 'coverage report': > > 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. -- Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: