[Fuego] Minnow board yocto build and Functional.reboot for minnow board

Pavan Arun Deshpande <[email protected]> Wed, 24 Mar 2021 11:46:34 +0530
Newsgroups dev.linux.lists.fuego
Message-ID <CAMQEYMcjn_zbvZjcEKKuO3UC5FhvhJXud4t9gHQ6u0b_9h7K6Q@mail.gmail.com>
Hi Tim,

We have tested Functional.reboot on minnow board locally as well as through
fserver.
The test case ran successfully.
please find a copy of the log result.

Running request: request-2021-03-23_13:48:18.22-pptlab:MINNOW
Trying to get request 'request-2021-03-23_13:48:18.22-pptlab:MINNOW' from server
Checking for (possibly newer) test Functional.reboot on server.
No matching tests found on the server
Executing test Functional.reboot on board MINNOW (using spec default)
Running test 'Functional.reboot' on board 'MINNOW' using spec 'default'
===== doing fuego phase: pre_test =====
===== doing fuego phase: build =====
The test is already built
Fuego test_build duration=0 seconds
===== doing fuego phase: deploy =====
===== doing fuego phase: snapshot =====
Firmware revision: 5.4.81-intel-pk-standard
===== doing fuego phase: run =====
-------------------------------------------------
TAP version 13
1..4
# fuego_test_tmp=/home/fuego/tmp/fuego.Functional.reboot
Calling target_reboot for board MINNOW...
ssh: connect to host 192.168.3.62 port 22: Connection timed out
# uptime of board=79 (seconds)
# duration of reboot=106 (seconds)
ok 1 - software reboot with target_reboot
# BOARD_CONTROL=ttc
ok 2 - does board have BOARD_CONTROL setting
Calling ov_board_control_reboot for board MINNOW...
comunicating with relay board

Serial<id=0x7f67e8d708d0, open=True>(port='/dev/ttyUSB1',
baudrate=9600, bytesize=8, parity='N', stopbits=1, timeout=3.0,
xonxoff=False, rtscts=False, dsrdtr=False)
Checking for ping..

('Data read is :', 'R')


<function ping at 0x7f67e8d8b938>
Sleeping for 3 secs
	
Resetting the MINNOW board

RELAY1_OFF_COMMAND: 0x32

usb device turned OFF successfully

Sleeping for 2 secs

RELAY1_ON_COMMAND: 0x77

usb device turned ON successfully

Closing Serial Port
# return code of 0 from ov_board_control_reboot
waiting for hardware reboot
# uptime of board=41 (seconds)
# duration of reboot=65 (seconds)
ok 3 - hardware reboot with ov_board_control_reboot
ok 4 - is Fuego tmp directory persistent
-------------------------------------------------
===== doing fuego phase: post_test =====
scp: /home/fuego/test/fuego.Functional.reboot/Functional.reboot.log:
No such file or directory
INFO: the test did not produce a test log on the target
===== doing fuego phase: processing =====
run/
run/machine-snapshot.txt
run/syslog.before.txt
run/devlog.txt
run/testlog.txt
run/run.json
run/syslog.after.txt
run/prolog.sh
run/spec.json
run/build.xml
run/consolelog.txt
chart config not found. Using default values.
Fuego: requested test phases complete!
Packaging run 'Functional.reboot-default-44-MINNOW'
Run packaged successfully, and is at:
/tmp/run-Functional.reboot-default-44-on-pptlab:MINNOW.frp
Run package run-Functional.reboot-default-44-on-pptlab:MINNOW.frp was
accepted by the server.
Run Functional.reboot-default-44-MINNOW put to server.


- The issue regarding yocto build for minnow is also resolved.
The job created to build Minnow board invokes python3 explicitly for
the yocto build.
 like  /usr/bin/python3 to point python 3 during the build process.

 Now the test cases for the minnow board are also running properly.
This has been verified with
 multiple tests and  iterations on both locally and through fserver.

Thanks and regards

Pavan Arun Deshpande

-- 






This
message contains confidential information and is intended only 
for the
individual(s) named. If you are not the intended
recipient, you are 
notified that disclosing, copying, distributing or taking any
action in 
reliance on the contents of this mail and attached file/s is strictly
prohibited. Please notify the
sender immediately and delete this e-mail 
from your system. E-mail transmission
cannot be guaranteed to be secured or 
error-free as information could be
intercepted, corrupted, lost, destroyed, 
arrive late or incomplete, or contain
viruses. The sender therefore does 
not accept liability for any errors or
omissions in the contents of this 
message, which arise as a result of e-mail
transmission.