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
Currently when debugging tests where the system is rebooted and it fails to come back after a reboot, we receive no information about the text execution like we would if the execute section had failed, etc. See for example this failure:
The only information we get is the "is taking too long Current Output" message which is not enough information, and additionally the debug section is not executed.
The text was updated successfully, but these errors were encountered:
anonymouse64
changed the title
task failure due to reboot request should print off all available logs up to that point
task failure due to reboot request time out should print off all available logs up to that point
Oct 5, 2020
Currently when debugging tests where the system is rebooted and it fails to come back after a reboot, we receive no information about the text execution like we would if the
execute
section had failed, etc. See for example this failure:The only information we get is the "is taking too long Current Output" message which is not enough information, and additionally the debug section is not executed.
The text was updated successfully, but these errors were encountered: