Serial (UART) output is captured in two phases, small window to lose messages

[thp-canonical]

For situations where images output log messages right after the device connector has determined that provisioning is successful, there might be a very short time window where the "provision-serial.log" capture stops and the "test-serial.log" capture hasn't started yet, dropping certain log messages. For test cases that depend on Serial/UART output, it might be good if the serial capture starts when/right before the DUT is power-cycled and continues running between the provisioning and testing phase.

Right now, provision logs are captured here (muxpi used as an example here, other device connectors capture the serial log in a similar way):

testflinger/device-connectors/src/testflinger_device_connectors/devices/muxpi/__init__.py

Lines 45 to 54 in 4c6007f

	serial_proc = SerialLogger(
	serial_host, serial_port, "provision-serial.log"
	)
	serial_proc.start()
	try:
	device.provision()
	except Exception as e:
	raise e
	finally:
	serial_proc.stop()

And test logs are captured here:

testflinger/device-connectors/src/testflinger_device_connectors/devices/__init__.py

Lines 196 to 205 in 4c6007f

	serial_proc = SerialLogger(serial_host, serial_port, "test-serial.log")
	serial_proc.start()
	try:
	exitcode = testflinger_device_connectors.run_test_cmds(
	test_cmds, config
	)
	except Exception as e:
	raise e
	finally:
	serial_proc.stop()

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/CERTTF-397.

This message was autogenerated