Home
last modified time | relevance | path

Searched refs:execution (Results 1 – 7 of 7) sorted by relevance

/test/vts/proto/
DVtsReportMessage.proto23 // To specify test case execution result.
123 // To specify a test case execution report.
131 // execution start and end time stamp.
276 // To specify a test execution report.
326 // To specify a test execution report.
343 // Detailed information about the execution environment (e.g., branch,
/test/vts/testcases/vts_selftest/test_framework/python_virtualenv_preparer_test/
DREADME.md12 The naming of `Part0`, `Part1` and `Part2` is to ensure the order of execution.
/test/mlts/benchmark/jni/
Drandom_graph_test_jni.cpp264 Execution execution(&compilation); in runRandomModel() local
266 createRequest(*testModel, &execution, &outputs); in runRandomModel()
269 Result executeReturn = execution.compute(); in runRandomModel()
/test/vts/harnesses/tradefed/tests/res/testtype/
Dvts_multi_device_test_parser_output_error.txt32 07-08 11:56:25 I/CompatibilityTest: Running system status checker after module execution: SampleCam…
34 07-08 11:56:26 I/CompatibilityTest: Running system status checker before module execution: SampleCa…
/test/vti/test_serving/proto/
DTestLabConfigMessage.proto19 // To specify the whole test execution schedule of a manifest branch.
DTestScheduleConfigMessage.proto28 // To specify the whole test execution schedule of a manifest branch.
/test/vti/dashboard/
DREADME.md192 The execution order of the commands is very important, otherwise you can't find some of the data in…