Lines Matching +refs:run +refs:many +refs:tests

14 When you run this, you may notice your CPU peg to 100% for a while, then taper
15 off to 1 or 2 active cores as the run finishes.  This is intentional.  DM is
17 still forced to run on a single thread.  You can use `--threads N` to limit DM to
26 492 srcs * 3 sinks + 382 tests == 1858 tasks
49 supports many test configurations, which are not all appropriate for all
50 machines.  These lines are a sort of FYI, mostly in case DM can't run some
51 configuration you might be expecting it to run.
59 492 srcs * 3 sinks + 382 tests == 1858 tasks
62 DM has found 382 unit tests (code linked in from tests/), and 492 other drawing
63 sources.  These drawing sources may be GM integration tests (code linked in
66 sources DM will use with `--src` (default, "tests gm image skp").
76 Sometimes DM calls these configs, sometimes sinks.  Sorry.  There are many
80 492 by 3.  The unit tests don't really fit into this source-sink model, so they
92   to track on our buildbots, some of which run perilously close to the system 
96   currently running or waiting to run.  We generally run one task per hardware
99   startup; it's harmless, and doesn't affect the correctness of the run.
101   3. Next, we see this task took 1.36 milliseconds to run.  Generally, the 
103   informational purposes, to make it easier for us to find slow tests.
134 like.  It contains a listing of each test run and a checksum of the image
135 generated for that run.
143 Unit tests don't generally output anything but a status update when they pass.
148 DM has a simple facility to compare against the results of a previous run:
161 same image as the `good` run.
181 That's the basics of DM.  DM supports many other modes and flags.  Here are a
187     out/Debug/dm --src tests   # Run only unit tests.