test/py: don't use mmc_rd config for other mmc tests
PATCH 1/1 test/py: don't use mmc_rd config for other mmc tests
From: Stephen Warren <[email protected]>
Fix test_mmc_dev(), test_mmc_rescan(), test_mmc_info() not to use the same configuration data that test_mmc_rd() does. Doing so causes the following issues:
* The new code uncondtionally expects certain keys to exist in the configuration data. These keys do not exist in existing configuration data since they were not previously required, and there was no notification re: a requirement to add these new keys. This causes test failures due to thrown exceptions when accessing the non-existent keys.
* The new tests logically operate on different objects. test_mmc_rd() operates on ranges of sectors on an MMC device (which may be the entire set of sectors of a device, or a part of a device), whereas all the new tests operate solely on entire devices. These are separate things, and it's entirely likely that the user will wish to runs the two types of tests on different sets of data; see the example configuration data that this commit adds. Ideally, the new tests would have been added to a separate Python file, since they aren' closely related to the existing tests.
FIXME: Marek, can you please replace the "???" in this patch with some reasonable looking data? Thanks.
--- test/py/tests/test_mmc_rd.py | 85 ++++++++++++++++++++++++++++-------- 1 file changed, 66 insertions(+), 19 deletions(-)
test/py/tests/test_mmc_rd.py +66 -19
@@ -13,6 +13,53 @@ import u_boot_utils This test relies on boardenv_* to containing configuration values to define which MMC devices should be tested. For example: +# Configuration data for test_mmc_dev, test_mmc_rescan, test_mmc_info; defines +# whole MMC devices that mmc dev/rescan/info commands may operate upon. +env__mmc_dev_configs = ( + { + 'fixture_id': 'emmc-boot0', + 'is_emmc': True, + 'devid': 0, + 'partid': 1, + 'info_device': ???, + 'info_speed': ???, + 'info_mode': ???, + 'info_buswidth': ???. + }, + { + 'fixture_id': 'emmc-boot1', + 'is_emmc': True, + 'devid': 0, + 'partid': 2, + 'info_device': ???, + 'info_speed': ???, + 'info_mode': ???, + 'info_buswidth': ???. + }, + { + 'fixture_id': 'emmc-data', + 'is_emmc': True, + 'devid': 0, + 'partid': 0, + 'info_device': ???, + 'info_speed': ???, + 'info_mode': ???, + 'info_buswidth': ???. + }, + { + 'fixture_id': 'sd', + 'is_emmc': False, + 'devid': 1, + 'partid': None, + 'info_device': ???, + 'info_speed': ???, + 'info_mode': ???, + 'info_buswidth': ???. + }, +} + +# Configuration data for test_mmc_rd; defines regions of the MMC (entire +# devices, or ranges of sectors) which can be read: env__mmc_rd_configs = ( { 'fixture_id': 'emmc-boot0',
@@ -85,12 +132,12 @@ def mmc_dev(u_boot_console, is_emmc, devid, partid): assert good_response in response @pytest.mark.buildconfigspec('cmd_mmc') -def test_mmc_dev(u_boot_console, env__mmc_rd_config): +def test_mmc_dev(u_boot_console, env__mmc_dev_config): """Test the "mmc dev" command. Args: u_boot_console: A U-Boot console connection. - env__mmc_rd_config: The single MMC configuration on which + env__mmc_dev_config: The single MMC configuration on which to run the test. See the file-level comment above for details of the format.
@@ -98,20 +145,20 @@ def test_mmc_dev(u_boot_console, env__mmc_rd_config): Nothing. """ - is_emmc = env__mmc_rd_config['is_emmc'] - devid = env__mmc_rd_config['devid'] - partid = env__mmc_rd_config.get('partid', 0) + is_emmc = env__mmc_dev_config['is_emmc'] + devid = env__mmc_dev_config['devid'] + partid = env__mmc_dev_config.get('partid', 0) # Select MMC device mmc_dev(u_boot_console, is_emmc, devid, partid) @pytest.mark.buildconfigspec('cmd_mmc') -def test_mmc_rescan(u_boot_console, env__mmc_rd_config): +def test_mmc_rescan(u_boot_console, env__mmc_dev_config): """Test the "mmc rescan" command. Args: u_boot_console: A U-Boot console connection. - env__mmc_rd_config: The single MMC configuration on which + env__mmc_dev_config: The single MMC configuration on which to run the test. See the file-level comment above for details of the format.
@@ -119,9 +166,9 @@ def test_mmc_rescan(u_boot_console, env__mmc_rd_config): Nothing. """ - is_emmc = env__mmc_rd_config['is_emmc'] - devid = env__mmc_rd_config['devid'] - partid = env__mmc_rd_config.get('partid', 0) + is_emmc = env__mmc_dev_config['is_emmc'] + devid = env__mmc_dev_config['devid'] + partid = env__mmc_dev_config.get('partid', 0) # Select MMC device mmc_dev(u_boot_console, is_emmc, devid, partid)
@@ -132,12 +179,12 @@ def test_mmc_rescan(u_boot_console, env__mmc_rd_config): assert 'no card present' not in response @pytest.mark.buildconfigspec('cmd_mmc') -def test_mmc_info(u_boot_console, env__mmc_rd_config): +def test_mmc_info(u_boot_console, env__mmc_dev_config): """Test the "mmc info" command. Args: u_boot_console: A U-Boot console connection. - env__mmc_rd_config: The single MMC configuration on which + env__mmc_dev_config: The single MMC configuration on which to run the test. See the file-level comment above for details of the format.
@@ -145,13 +192,13 @@ def test_mmc_info(u_boot_console, env__mmc_rd_config): Nothing. """ - is_emmc = env__mmc_rd_config['is_emmc'] - devid = env__mmc_rd_config['devid'] - partid = env__mmc_rd_config.get('partid', 0) - info_device = env__mmc_rd_config['info_device'] - info_speed = env__mmc_rd_config['info_speed'] - info_mode = env__mmc_rd_config['info_mode'] - info_buswidth = env__mmc_rd_config['info_buswidth'] + is_emmc = env__mmc_dev_config['is_emmc'] + devid = env__mmc_dev_config['devid'] + partid = env__mmc_dev_config.get('partid', 0) + info_device = env__mmc_dev_config['info_device'] + info_speed = env__mmc_dev_config['info_speed'] + info_mode = env__mmc_dev_config['info_mode'] + info_buswidth = env__mmc_dev_config['info_buswidth'] # Select MMC device mmc_dev(u_boot_console, is_emmc, devid, partid)
Signature · 1 line
2.21.0
PATCH 1/1 test/py: don't use mmc_rd config for other mmc tests
Quoted 22 lines · Stephen Warren
From: Stephen Warren <[email protected]>
Fix
test_mmc_dev(),test_mmc_rescan(),test_mmc_info()not to use the same configuration data thattest_mmc_rd()does. Doing so causes the following issues:* The new code uncondtionally expects certain keys to exist in the configuration data. These keys do not exist in existing configuration data since they were not previously required, and there was no notification re: a requirement to add these new keys. This causes test failures due to thrown exceptions when accessing the non-existent keys.
* The new tests logically operate on different objects.
test_mmc_rd()operates on ranges of sectors on an MMC device (which may be the entire set of sectors of a device, or a part of a device), whereas all the new tests operate solely on entire devices. These are separate things, and it's entirely likely that the user will wish to runs the two types of tests on different sets of data; see the example configuration data that this commit adds. Ideally, the new tests would have been added to a separate Python file, since they aren' closely related to the existing tests.
Quoted 2 lines
FIXME: Marek, can you please replace the "???" in this patch with some reasonable looking data? Thanks.
Tom, Marek, any chance of applying this? Right now, every mainline branch is failing 5 tests on every push, which wastes my time having to go through all the logs to manually check that the failures aren't anything new/unknown. Thanks.
PATCH 1/1 test/py: don't use mmc_rd config for other mmc tests
Quoted 23 lines · Stephen Warren
Quoted 22 lines · Stephen Warren
From: Stephen Warren <[email protected]>
Fix
test_mmc_dev(),test_mmc_rescan(),test_mmc_info()not to use the same configuration data thattest_mmc_rd()does. Doing so causes the following issues:* The new code uncondtionally expects certain keys to exist in the configuration data. These keys do not exist in existing configuration data since they were not previously required, and there was no notification re: a requirement to add these new keys. This causes test failures due to thrown exceptions when accessing the non-existent keys.
* The new tests logically operate on different objects.
test_mmc_rd()operates on ranges of sectors on an MMC device (which may be the entire set of sectors of a device, or a part of a device), whereas all the new tests operate solely on entire devices. These are separate things, and it's entirely likely that the user will wish to runs the two types of tests on different sets of data; see the example configuration data that this commit adds. Ideally, the new tests would have been added to a separate Python file, since they aren' closely related to the existing tests.
Quoted 7 lines
Quoted 2 lines
FIXME: Marek, can you please replace the "???" in this patch with some reasonable looking data? Thanks.
Tom, Marek, any chance of applying this? Right now, every mainline branch is failing 5 tests on every push, which wastes my time having to go through all the logs to manually check that the failures aren't anything new/unknown. Thanks.
I'm still overloaded, and didn't have time to look into this. But I'm really not fond of the duplication here -- now we have two big tables describing very much the same thing, which SD/MMC to test .
Signature · 2 lines
Best regards, Marek Vasut
PATCH 1/1 test/py: don't use mmc_rd config for other mmc tests
Quoted 27 lines · Marek Vasut
Quoted 26 lines · Stephen Warren
Quoted 24 lines · Stephen Warren
From: Stephen Warren <[email protected]>
Fix
test_mmc_dev(),test_mmc_rescan(),test_mmc_info()not to use the same configuration data thattest_mmc_rd()does. Doing so causes the following issues:* The new code uncondtionally expects certain keys to exist in the configuration data. These keys do not exist in existing configuration data since they were not previously required, and there was no notification re: a requirement to add these new keys. This causes test failures due to thrown exceptions when accessing the non-existent keys.
* The new tests logically operate on different objects.
test_mmc_rd()operates on ranges of sectors on an MMC device (which may be the entire set of sectors of a device, or a part of a device), whereas all the new tests operate solely on entire devices. These are separate things, and it's entirely likely that the user will wish to runs the two types of tests on different sets of data; see the example configuration data that this commit adds. Ideally, the new tests would have been added to a separate Python file, since they aren' closely related to the existing tests.FIXME: Marek, can you please replace the "???" in this patch with some reasonable looking data? Thanks.
Quoted 8 lines
Quoted 4 lines
Tom, Marek, any chance of applying this? Right now, every mainline branch is failing 5 tests on every push, which wastes my time having to go through all the logs to manually check that the failures aren't anything new/unknown. Thanks.
I'm still overloaded, and didn't have time to look into this. But I'm really not fond of the duplication here -- now we have two big tables describing very much the same thing, which SD/MMC to test .
There's no redundancy; the two different tests are semantically entirely different and don't share any configuration. See the patch description above for the full details.
PATCH 1/1 test/py: don't use mmc_rd config for other mmc tests
Quoted 34 lines · Stephen Warren
Quoted 33 lines · Marek Vasut
Quoted 31 lines · Stephen Warren
Quoted 23 lines · Stephen Warren
From: Stephen Warren <[email protected]>
Fix
test_mmc_dev(),test_mmc_rescan(),test_mmc_info()not to use the same configuration data thattest_mmc_rd()does. Doing so causes the following issues:* The new code uncondtionally expects certain keys to exist in the configuration data. These keys do not exist in existing configuration data since they were not previously required, and there was no notification re: a requirement to add these new keys. This causes test failures due to thrown exceptions when accessing the non-existent keys.
* The new tests logically operate on different objects.
test_mmc_rd()operates on ranges of sectors on an MMC device (which may be the entire set of sectors of a device, or a part of a device), whereas all the new tests operate solely on entire devices. These are separate things, and it's entirely likely that the user will wish to runs the two types of tests on different sets of data; see the example configuration data that
this commit adds. Ideally, the new tests would have been added to a separate Python file, since they aren' closely related to the existing tests.Quoted 2 lines
FIXME: Marek, can you please replace the "???" in this patch with some reasonable looking data? Thanks.
Tom, Marek, any chance of applying this? Right now, every mainline branch is failing 5 tests on every push, which wastes my time having to go through all the logs to manually check that the failures aren't anything new/unknown. Thanks.
Quoted 7 lines
Quoted 3 lines
I'm still overloaded, and didn't have time to look into this. But I'm really not fond of the duplication here -- now we have two big tables describing very much the same thing, which SD/MMC to test .
There's no redundancy; the two different tests are semantically entirely different and don't share any configuration. See the patch description above for the full details.
Tom, could you please apply this patch to fix the test failures. Thanks.
PATCH 1/1 test/py: don't use mmc_rd config for other mmc tests
In reply to Stephen WarrenQuoted 22 lines · Stephen Warren
From: Stephen Warren <[email protected]>
Fix
test_mmc_dev(),test_mmc_rescan(),test_mmc_info()not to use the same configuration data thattest_mmc_rd()does. Doing so causes the following issues:* The new code uncondtionally expects certain keys to exist in the configuration data. These keys do not exist in existing configuration data since they were not previously required, and there was no notification re: a requirement to add these new keys. This causes test failures due to thrown exceptions when accessing the non-existent keys.
* The new tests logically operate on different objects.
test_mmc_rd()operates on ranges of sectors on an MMC device (which may be the entire set of sectors of a device, or a part of a device), whereas all the new tests operate solely on entire devices. These are separate things, and it's entirely likely that the user will wish to runs the two types of tests on different sets of data; see the example configuration data that this commit adds. Ideally, the new tests would have been added to a separate Python file, since they aren' closely related to the existing tests.
Quoted 8 lines
FIXME: Marek, can you please replace the "???" in this patch with some reasonable looking data? Thanks.
Cc Marek Vasut <[email protected]>Fixes 4ffec8cdf512 ("test/py: mmc: Add 'mmc info' test")Fixes ce4b2cafa79c ("test/py: mmc: Add 'mmc rescan' test")Fixes 86dfd152c917 ("test/py: mmc: Add 'mmc dev' test")Signed-off-by Stephen Warren <[email protected]>
Applied to u-boot/master, thanks!
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <http://lists.denx.de/pipermail/u-boot/attachments/20190510/5de038c8/attachment.sig>
PATCH 1/1 test/py: don't use mmc_rd config for other mmc tests
Quoted 27 lines · Tom Rini
Quoted 25 lines · Stephen Warren
From: Stephen Warren <[email protected]>
Fix
test_mmc_dev(),test_mmc_rescan(),test_mmc_info()not to use the same configuration data thattest_mmc_rd()does. Doing so causes the following issues:* The new code uncondtionally expects certain keys to exist in the configuration data. These keys do not exist in existing configuration data since they were not previously required, and there was no notification re: a requirement to add these new keys. This causes test failures due to thrown exceptions when accessing the non-existent keys.
* The new tests logically operate on different objects.
test_mmc_rd()operates on ranges of sectors on an MMC device (which may be the entire set of sectors of a device, or a part of a device), whereas all the new tests operate solely on entire devices. These are separate things, and it's entirely likely that the user will wish to runs the two types of tests on different sets of data; see the example configuration data that this commit adds. Ideally, the new tests would have been added to a separate Python file, since they aren' closely related to the existing tests.FIXME: Marek, can you please replace the "???" in this patch with some reasonable looking data? Thanks.
Quoted 7 lines
Quoted 5 lines
Cc Marek Vasut <[email protected]>Fixes 4ffec8cdf512 ("test/py: mmc: Add 'mmc info' test")Fixes ce4b2cafa79c ("test/py: mmc: Add 'mmc rescan' test")Fixes 86dfd152c917 ("test/py: mmc: Add 'mmc dev' test")Signed-off-by Stephen Warren <[email protected]>Applied to u-boot/master, thanks!
Thanks. Testing of u-boot/master is all back to green now.