-
Notifications
You must be signed in to change notification settings - Fork 565
treewide: streamline #[source] and Error (follow-up (1/2)) #7085
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
treewide: streamline #[source] and Error (follow-up (1/2)) #7085
Conversation
This streamlines the Error implementation in the Cloud Hypervisor code base to match the remaining parts so that everything follows the agreed conventions. These are leftovers missed in the previous commits. Signed-off-by: Philipp Schuster <[email protected]> On-behalf-of: SAP [email protected]
This streamlines the Error implementation in the Cloud Hypervisor code base to match the remaining parts so that everything follows the agreed conventions. These are leftovers missed in the previous commits. Signed-off-by: Philipp Schuster <[email protected]> On-behalf-of: SAP [email protected]
rbradford
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks - this has been on the TODO list for a long time!
This streamlines the Error implementation in the Cloud Hypervisor code base to match the remaining parts so that everything follows the agreed conventions. These are leftovers missed in the previous commits. Signed-off-by: Philipp Schuster <[email protected]> On-behalf-of: SAP [email protected]
Head branch was pushed to by a user without write access
f477d0f to
e60d5a9
Compare
|
@phip1611 I think this the failure on the CI test is genuine: |
This streamlines the Error implementation in the Cloud Hypervisor code base to match the remaining parts so that everything follows the agreed conventions. These are leftovers missed in the previous commits. Signed-off-by: Philipp Schuster <[email protected]> On-behalf-of: SAP [email protected]
This streamlines the Error implementation in the Cloud Hypervisor code base to match the remaining parts so that everything follows the agreed conventions. These are leftovers missed in the previous commits. Signed-off-by: Philipp Schuster <[email protected]> On-behalf-of: SAP [email protected]
This streamlines the Error implementation in the Cloud Hypervisor code base to match the remaining parts so that everything follows the agreed conventions. These are leftovers missed in the previous commits. Signed-off-by: Philipp Schuster <[email protected]> On-behalf-of: SAP [email protected]
This streamlines the Error implementation in the Cloud Hypervisor code base to match the remaining parts so that everything follows the agreed conventions. These are leftovers missed in the previous commits. Signed-off-by: Philipp Schuster <[email protected]> On-behalf-of: SAP [email protected]
This streamlines the Error implementation in the Cloud Hypervisor code base to match the remaining parts so that everything follows the agreed conventions. These are leftovers missed in the previous commits. Signed-off-by: Philipp Schuster <[email protected]> On-behalf-of: SAP [email protected]
e60d5a9 to
4b4531c
Compare
|
After three hours of debugging, I traced the problem down to the following commits:
I was not able to find anything useful; I could reduce the feedback cycle of running the integration test locally to around six minutes, which is still not very pleasant. I've ran the test locally using this command: TL;DR: I moved the problematic part to a new PR (#7089). I'm seeking help to debug this, I don't know how to continue. Guidance or collaboration is highly appreciated! |
ea6d5a0
While working on #7066, I've noticed that I've missed more Error types in the code that would benefit from streamlining them. So, this is a follow-up of #7069 basically doing the same.
I've used some tooling to analyze the code base, but it seems that I've finally caught all missing pieces!
I'd like to add that I think this is well invested time, as
thiserrorfor everything)std::error::Errortrait, Cloud Hypervisor will be preparedI was able to locate all missing pieces using this Python script (happily generated by ChatGPT):