8000 Icetea must be run from the mbed-os root · Issue #8120 · ARMmbed/mbed-os · GitHub
[go: up one dir, main page]

Skip to content
Icetea must be run from the mbed-os root #8120
Closed
@SeppoTakalo

Description

@SeppoTakalo

Description

Apparently this method of running tests does not work anymore

mbed new test
cd test
mbed test -t <target> -m <toolchain>

In order to run Icetea tests, it seems to require that you are inside of Mbed OS folder.

$ mbed test --icetea --test-config tools/test_configs/HeapBlockDeviceAndEthernetInterface.json -v -m K66F -t GCC_ARM
[mbed] Working path "/Users/septak01/src/tmp/socket-test" (program)
[mbed] Exec "/Users/septak01/src/virtualenvs/mbed-build/bin/python2.7 -u /Users/septak01/src/tmp/socket-test/mbed-os/tools/run_icetea.py -m K66F -t GCC_ARM -v --application-list" in "/Users/septak01/src/tmp/socket-test"
[mbed] ERROR: "/Users/septak01/src/virtualenvs/mbed-build/bin/python2.7" returned error.
       Code: 1
       Path: "/Users/septak01/src/tmp/socket-test"
       Command: "/Users/septak01/src/virtualenvs/mbed-build/bin/python2.7 -u /Users/septak01/src/tmp/socket-test/mbed-os/tools/run_icetea.py -m K66F -t GCC_ARM -v --application-list"
       Tip: You could retry the last command with "-v" flag for verbose output
---

$ cd mbed-os
$ mbed test --icetea --test-config tools/test_configs/HeapBlockDeviceAndEthernetInterface.json -v -m K66F -t GCC_ARM
...
Build successes:
  * K66F::GCC_ARM::MBED-BUILD
  * K66F::GCC_ARM::TEST_APPS-DEVICE-SOCKET_APP

...
17:46:51.163 Suite creation complete.
17:46:51.193 Test cases prepared.
+-------+--------------------------------+----------+-------+---------+---------------------+--------------------------+---------+-------------------+
| Index |              Name              |  Status  |  Type | Subtype |        Group        |        Component         | Feature | Allowed platforms |
+-------+--------------------------------+----------+-------+---------+---------------------+--------------------------+---------+-------------------+
| 1     |          test_cmdline          | released | smoke |         |  testcases/example  |       ['cmdline']        |         |                   |
| 2     |      UDPSOCKET_BIND_PORT       | released | smoke |  socket | testcases/netsocket | ['mbed-os', 'netsocket'] |         |                   |
| 3     |      TCPSOCKET_BIND_PORT       | released | smoke |  socket | testcases/netsocket | ['mbed-os', 'netsocket'] |         |                   |
| 4     |        TCPSERVER_ACCEPT        | released | smoke |  socket | testcases/netsocket | ['mbed-os', 'netsocket'] |         |                   |
| 5     | TCPSOCKET_ECHOTEST_BURST_SHORT | released | smoke |  socket | testcases/netsocket | ['mbed-os', 'netsocket'] |         |                   |
+-------+--------------------------------+----------+-------+---------+---------------------+--------------------------+---------+-------------------+

So it starts to run the testcases, but only if I start from mbed-os folder.

Is this documented behaviour?
@OPpuolitaival
Might be a root cause for #8064

Issue request type

[ ] Question
[ ] Enhancement
[X] Bug

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0