Hi,
On Sat, 5 Oct 2019 at 20:42, Joe Hershberger joe.hershberger@ni.com wrote:
Hi Bin,
On Sat, Oct 5, 2019 at 9:13 PM Bin Meng bmeng.cn@gmail.com wrote:
Hi Joe,
On Sun, Oct 6, 2019 at 9:05 AM Joe Hershberger joe.hershberger@ni.com wrote:
Hi Bin,
On Fri, Oct 4, 2019 at 9:27 PM Bin Meng bmeng.cn@gmail.com wrote:
Hi Simon,
On Sat, Oct 5, 2019 at 10:16 AM Bin Meng bmeng.cn@gmail.com wrote:
Hi Simon,
On Wed, Sep 25, 2019 at 10:58 PM Simon Glass sjg@chromium.org wrote:
These warnings appear every thing sandbox is run (see below) and dwarf the actual useful output. Suppress them.
Hopefully at some point a way can be found to fix the root cause.
Does removing ethaddr env from SANDBOX_ETH_SETTINGS in sandbox.h fix this problem?
I was able to reproduce this, and confirmed that removing ethaddr* envs from SANDBOX_ETH_SETTINGS in sandbox.h could fix the issue you were seeing.
While that fixes the issue, it also breaks the unit tests.
Yes, it fixes sandbox with "-D" but fails with "-T".
Maybe we can make it work for both by removing them from the header, but then setting the needed ethaddr's in the unit tests.
It looks like I can get most of the way there with this change, but I still need to supress one warning.
Plus it breaks the tests, perhaps because the env vars are set after net is inited.
WIll send an updated patch.
Regards, Simon