You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For image_tests, to wait for some image to boot, I add a startup script to print the message "BOOTED" and I use Daisy WaitForInstancesSignal, but sles11 doesn't seem to send syslog outputs to the serial port and the test fails.
I tested on the latest sles11:
sles-11-sp4-v20180104 suse-cloud sles-11
The text was updated successfully, but these errors were encountered:
You can't assume startup script stdout will go to the serial console, it's
better to write to /dev/ttyS0 directly unless your specifically testing
syslog output to the serial console.
I don't think we should rely on syslog writing to the serial console at all
as it makes a lot of assumptions of the host OS (syslog redirection is
setup or that the OS even uses syslog) but that's a separate discussion
entirely.
On Fri, Mar 23, 2018, 8:53 PM Helen Koike ***@***.***> wrote:
For image_tests, to wait for some image to boot, I add a startup script to
print the message "BOOTED" and I use Daisy WaitForInstancesSignal, but
sles11 doesn't seem to send syslog outputs to the serial port and the test
fails.
I tested on the latest sles11:
sles-11-sp4-v20180104 suse-cloud sles-11
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#373>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQWyS6aZGaqrdmeBBhJfAcOPeChFdeaQks5thcMkgaJpZM4S5luc>
.
For image_tests, to wait for some image to boot, I add a startup script to print the message "BOOTED" and I use Daisy WaitForInstancesSignal, but sles11 doesn't seem to send syslog outputs to the serial port and the test fails.
I tested on the latest sles11:
sles-11-sp4-v20180104 suse-cloud sles-11
The text was updated successfully, but these errors were encountered: