[U-Boot] [U-Boot, v4, 2/2] test/py: add test for whitelist of variables while importing environment

[Stephen Warren <swarren@wwwdotorg.org>]

On 06/13/2018 12:53 PM, Quentin Schulz wrote:
> Hi Tom,
> 
> On Wed, Jun 13, 2018 at 11:43:32AM -0400, Tom Rini wrote:
>> On Mon, Jun 04, 2018 at 11:47:30AM +0200, Quentin Schulz wrote:
>>
>>> This tests that the importing of an environment with a specified
>>> whitelist works as intended.
>>>
>>> If there are variables passed as parameter to the env import command,
>>>     those only should be imported in the current environment.
>>>
>>> For each variable passed as parameter, if
>>>   - foo is bar in current env and bar2 in exported env, after importing
>>>   exported env, foo shall be bar2,
>>>   - foo does not exist in current env and foo is bar2 in exported env,
>>>   after importing exported env, foo shall be bar2,
>>>   - foo is bar in current env and does not exist in exported env (but is
>>>   passed as parameter), after importing exported env, foo shall be empty,
>>>
>>> Any variable not passed as parameter should be left untouched.
>>>
>>> Two other tests are made to test that size cannot be '-' if the checksum
>>> protection is enabled.
>>>
>>> Signed-off-by: Quentin Schulz <quentin.schulz@bootlin.com>
>>> Reviewed-by: Simon Glass <sjg@chromium.org>
>>> Reviewed-by: Stephen Warren <swarren@nvidia.com>
>>
>> This seems to not be working?
>>
>> https://travis-ci.org/trini/u-boot/jobs/391504525
>>
> 
> I just rebased on top of v2018.07-rc1, ran
> make mrproper
> ./test/py/test.py --bd sandbox --build
> 
> and the tests run fine ...

Most likely the failure is due to the test relying on some feature that 
isn't enabled on the board being tested (emulated via qemu); you'll need 
to add something like the following to indicate which feature the test 
relies upon:

@pytest.mark.buildconfigspec('cmd_echo')

All the test commands are in .travis.yml in the top-level of the U-Boot 
source tree. You can see the exact error at the very end of the log that 
Tom linked to.