pub enum DebugDataProcessorRequest {
SetDirectory {
directory: ClientEnd<DirectoryMarker>,
control_handle: DebugDataProcessorControlHandle,
},
AddDebugVmos {
vmos: Vec<DebugVmo>,
responder: DebugDataProcessorAddDebugVmosResponder,
},
Finish {
responder: DebugDataProcessorFinishResponder,
},
}
Expand description
A test-manager internal protocol used for communicating between the debug data
component, which implements fuchsia.debugdata.Publisher
, and the component that
actually processes the VMOs passed to fuchsia.debugdata.Publisher
.
In the future, this protocol may be moved to the SDK, to enable “pluggable” VMO
processing, or removed entirely if VMO processing is moved to the host.
Variants§
SetDirectory
Set the directory to store results in. This must be called first. Note that we currently provide a directory as coverage tools pull profile information off the device using a specific, topology dependent location in the /tmp filesystem. Once these tools are updated, we can update this protocol free of this constraint.
AddDebugVmos
Add more VMOs to process. The VMOs are expected to be ready to process.
Finish
Indicates all VMOs have been sent. This method returns when all processing is complete, after which the client may observe the results in the directory passed via NewProcessor.
Fields
responder: DebugDataProcessorFinishResponder
Implementations§
Source§impl DebugDataProcessorRequest
impl DebugDataProcessorRequest
pub fn into_set_directory( self, ) -> Option<(ClientEnd<DirectoryMarker>, DebugDataProcessorControlHandle)>
pub fn into_add_debug_vmos( self, ) -> Option<(Vec<DebugVmo>, DebugDataProcessorAddDebugVmosResponder)>
pub fn into_finish(self) -> Option<DebugDataProcessorFinishResponder>
Sourcepub fn method_name(&self) -> &'static str
pub fn method_name(&self) -> &'static str
Name of the method defined in FIDL