Skip to content

Unable to use "mbed test" with option "-n" #2511

Closed
@bogdanm

Description

@bogdanm

I'm trying to run this command on mbed-os 862db41:

> mbed test -m K64F -t GCC_ARM -n tests-mbed_drivers-generic_tests -v

The test compiles, but I get this error for running (observe the mbedhtrun-script.py: error: no such option: -t part):

[mbed] Exec "mbedgt --test-spec c:\work\mbed\morpheus\mbed-os-clean\.build/tests\K64F\GCC_ARM\test_spec.json -n tests-mbed_drivers-generic_tests -V" in c:\work\mbed\morpheus\mbed-os-clean
mbedgt: greentea test automation tool ver. 1.2.0
mbedgt: test specification file 'c:\work\mbed\morpheus\mbed-os-clean\.build/tests\K64F\GCC_ARM\test_spec.json' (specified with --test-spec option)
mbedgt: using 'c:\work\mbed\morpheus\mbed-os-clean\.build/tests\K64F\GCC_ARM\test_spec.json' from current directory!
mbedgt: detecting connected mbed-enabled devices...
mbedgt: detected 1 device
        +---------------+----------------------+-------------+-------------+--------------------------+
        | platform_name | platform_name_unique | serial_port | mount_point | target_id                |
        +---------------+----------------------+-------------+-------------+--------------------------+
        | K64F          | K64F[0]              | COM38       | F:          | 024002211E1B1E0EE3C5E3B6 |
        +---------------+----------------------+-------------+-------------+--------------------------+
mbedgt: processing target 'K64F' toolchain 'GCC_ARM' compatible platforms... (note: switch set to --parallel 1)
        +---------------+----------------------+-------------+-------------+--------------------------+
        | platform_name | platform_name_unique | serial_port | mount_point | target_id                |
        +---------------+----------------------+-------------+-------------+--------------------------+
        | K64F          | K64F[0]              | COM38:9600  | F:          | 024002211E1B1E0EE3C5E3B6 |
        +---------------+----------------------+-------------+-------------+--------------------------+
mbedgt: test case filter (specified with -n option)
        test filtered in 'tests-mbed_drivers-generic_tests'
mbedgt: running 1 test for platform 'K64F' and toolchain 'GCC_ARM'
        use 1 instance of execution threads for testing
mbedgt: checking for 'host_tests' directory above image directory structure
        'host_tests' directory not found: two directory levels above image path checked
mbedgt: selecting test case observer...
        calling mbedhtrun: mbedhtrun -m K64F -p COM38:9600 -f ".build/tests/K64F/GCC_ARM/TESTS/mbed_drivers/generic_tests/generic_tests.bin" -d F: -C 4 -c shell -t 024002211E1B1E0EE3C5E3B6
mbedgt: mbed-host-test-runner: started
Usage: mbedhtrun-script.py [options]

mbedhtrun-script.py: error: no such option: -t
mbedgt: checking for GCOV data...
mbedgt: mbed-host-test-runner: stopped and returned 'TIMEOUT'
mbedgt: test case summary event not found
        no test case report present, assuming test suite to be a single test case!
        test suite: tests-mbed_drivers-generic_tests
        test case: tests-mbed_drivers-generic_tests
mbedgt: test on hardware with target id: 024002211E1B1E0EE3C5E3B6
mbedgt: test suite 'tests-mbed_drivers-generic_tests' ................................................ TIMEOUT in 0.38 sec
        test case: 'tests-mbed_drivers-generic_tests' ................................................ ERROR in 0.38 sec
mbedgt: test case summary: 0 passes, 1 failure
mbedgt: all tests finished!
mbedgt: shuffle seed: 0.7228190045
mbedgt: test suite report:
+--------------+---------------+----------------------------------+---------+--------------------+-------------+
| target       | platform_name | test suite                       | result  | elapsed_time (sec) | copy_method |
+--------------+---------------+----------------------------------+---------+--------------------+-------------+
| K64F-GCC_ARM | K64F          | tests-mbed_drivers-generic_tests | TIMEOUT | 0.38               | shell       |
+--------------+---------------+----------------------------------+---------+--------------------+-------------+
mbedgt: test suite results: 1 TIMEOUT
mbedgt: test case report:
+--------------+---------------+----------------------------------+----------------------------------+--------+--------+--------+--------------------+
| target       | platform_name | test suite                       | test case                        | passed | failed | result | elapsed_time (sec) |
+--------------+---------------+----------------------------------+----------------------------------+--------+--------+--------+--------------------+
| K64F-GCC_ARM | K64F          | tests-mbed_drivers-generic_tests | tests-mbed_drivers-generic_tests | 0      | 1      | ERROR  | 0.38               |
+--------------+---------------+----------------------------------+----------------------------------+--------+--------+--------+--------------------+
mbedgt: test case results: 1 ERROR
mbedgt: completed in 0.44 sec
mbedgt: exited with code 1
[mbed] ERROR: "mbedgt" returned error code 1.
[mbed] ERROR: Command "mbedgt --test-spec c:\work\mbed\morpheus\mbed-os-clean\.build/tests\K64F\GCC_ARM\test_spec.json -n tests-mbed_drivers-generic_tests -V" in "c:\work\mbed\morpheus\mbed-os-clean"

OS: Windows 7

Python module versions (latest modules available in pip at the time of writing this):

mbed-cli (0.9.1)
mbed-greentea (1.2.0)
mbed-host-tests (1.1.0)
mbed-ls (1.2.1)
mbed-test-wrapper (1.0.0)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions