17f0b6df72
Share command flags between dm and unit tests. Also, allow dm's core to be included by itself and iOSShell. Command line flags that are the same (or nearly the same) in DM and in skia_tests have been moved to common_flags. Authors, please check to see that the shared common flag is correct for the tool. For iOS, the 'tool_main' entry point has a wrapper to allow multiple tools to be statically linked in the iOSShell. Since SkCommandLineFlags::Parse can only be called once, these calls are disabled in the IOS build. Since the iOS app directory is dynamically assigned a name, use '@' to select it. (This is the same convention chosen by the Mobile Harness iOS file system utilities.) Move the heart of dm.gyp into dm.gypi so that it can be included by itself and iOSShell.gyp. Add tools/flags/SkCommonFlags.* to define and declare common command line flags. Add support for dm to iOSShell. BUG=skia: R=scroggo@google.com, mtklein@google.com, jvanverth@google.com, bsalomon@google.com Author: caryclark@google.com Review URL: https://codereview.chromium.org/389653004 |
||
|---|---|---|
| .. | ||
| DM.cpp | ||
| DMCpuGMTask.cpp | ||
| DMCpuGMTask.h | ||
| DMExpectations.h | ||
| DMExpectationsTask.cpp | ||
| DMExpectationsTask.h | ||
| DMGpuGMTask.cpp | ||
| DMGpuGMTask.h | ||
| DMGpuSupport.h | ||
| DMPDFRasterizeTask.cpp | ||
| DMPDFRasterizeTask.h | ||
| DMPDFTask.cpp | ||
| DMPDFTask.h | ||
| DMPipeTask.cpp | ||
| DMPipeTask.h | ||
| DMQuiltTask.cpp | ||
| DMQuiltTask.h | ||
| DMReporter.cpp | ||
| DMReporter.h | ||
| DMSerializeTask.cpp | ||
| DMSerializeTask.h | ||
| DMSKPTask.cpp | ||
| DMSKPTask.h | ||
| DMTask.cpp | ||
| DMTask.h | ||
| DMTaskRunner.cpp | ||
| DMTaskRunner.h | ||
| DMTestTask.cpp | ||
| DMTestTask.h | ||
| DMUtil.cpp | ||
| DMUtil.h | ||
| DMWriteTask.cpp | ||
| DMWriteTask.h | ||
| README | ||
DM is like GM, but multithreaded. It doesn't do everything GM does.
DM's design is based around Tasks and a TaskRunner.
A Task represents an independent unit of work that might fail. We make a task
for each GM/configuration pair we want to run. Tasks can kick off new tasks
themselves. For example, a CpuTask can kick off a ReplayTask to make sure
recording and playing back an SkPicture gives the same result as direct
rendering.
The TaskRunner runs all tasks on one of two threadpools, whose sizes are
configurable by --cpuThreads and --gpuThreads. Ideally we'd run these on a
single threadpool but it can swamp the GPU if we shove too much work into it at
once. --cpuThreads defaults to the number of cores on the machine.
--gpuThreads defaults to 1, but you may find 2 or 4 runs a little faster.
So the main flow of DM is:
for each GM:
for each configuration:
kick off a new task
< tasks run, maybe fail, and maybe kick off new tasks >
wait for all tasks to finish
report failures