Multiple machines

[Sparry, Icarus W]

Is there any documentation on running FAFT on multiple DUT’s in parallel?

 

For example the magic “:lab:” argument

 

Have people managed to connect and use more than 2 servo boards on a given host?

We can run tests using the –args=servo_port=9998 for a single DUT, but how do we specify the servo information for multiple DUTs.

 

[Icarus W Sparry]

Anyone?

Also it looks as if there are options for using beaglebone single board computers as "servo hosts". Any particular model of beaglebone?

[Danny Chan]

You will need to use a different port for each instance and pass the board serial number to servod and test_that.

example

sudo servod  --board=$BOARD --port 7777 -p 0x5002 --serial {servo serial#}

test_that -b $BOARD $DUT_IP --args "servo_host=localhost servo_port=7777" suite:faft_bios

The -p to servod might not be needed, you can try without it.

To unsubscribe from this group and stop receiving emails from it, send an email to faft-users+...@chromium.org.

[Danny Chan]

I would stay with servo v2 board.  However you can contact your google representative if you really want to use servo v3 (with beaglebone).

On Thu, Oct 15, 2015 at 9:27 AM, Icarus W Sparry <icarus....@intel.com> wrote:

To unsubscribe from this group and stop receiving emails from it, send an email to faft-users+...@chromium.org.

[Icarus W Sparry]

Thanks. Is running FAFT with more that one servo board connected at the same time a supported configuration?

I see conflicts due to the simplistic manner in which FAFT determines USB devices in particular (diff the output of "ls /dev/sd?" with the usb drive connected to the host and without).

From hints, it looks as if the setup I am looking for is something like

A single host running a set of tests, in this case the FAFT suite, but could be anything.

Multiple DUTs, each with a servo card and a single board computer acting as a "servo host".

The tests would then be run on the hosts on a first come first served basis, which would allow for reasonable (but not perfect) parallelism.

At the moment a run of suite:faft on a host with 2 servo boards passes on either, but fails if I run the two suites at the same time.