[Bug]: Support for Qemu testing broke real system reboot timing #94
Labels
state:needs-triage
Needs to triaged to determine next steps
type:bug
Something isn't working
urgency:high
Significant with a critical impact
Comments
mikeytdisco
added
state:needs-triage
4 tasks
Flickdm
added a commit
that referenced
this issue
May 17, 2023
Pinging a QEMU virtual system doesn't work for detecting the system going offline, so the ping was removed from both the offline and online path of the test cases. However, this broke testing with real system. Allow all exceptions to signal system not available when waiting for online or offline. Fixes #94 - [x] Impacts functionality? - [ ] Impacts security? - [x] Includes tests? - [ ] Includes documentation? ## How This Was Tested Tested on the QEMU path and a physical system. ## Integration Instructions N/A Co-authored-by: Doug Flick <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is there an existing issue for this?
Current Behavior
When running a the UnitTest testcases, after the system restarts, the remote framework isn't connected correctly.
Expected Behavior
The testcase should reboot the system successfully.
Steps To Reproduce
Run one of the Dfci test cases.
Build Environment
Version Information
Urgency
High
Are you going to fix this?
I will fix it
Do you need maintainer feedback?
No maintainer feedback needed
Anything else?
No response
The text was updated successfully, but these errors were encountered: