73210c7f40
Bug: chromium:788113 Change-Id: I205c57869caa24957d63a139f6ba0c6e8cf45749 Reviewed-on: https://chromium-review.googlesource.com/800151 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Cr-Commit-Position: refs/heads/master@{#49783} |
||
---|---|---|
.. | ||
client.v8.pyl | ||
OWNERS | ||
README.md | ||
tryserver.v8.pyl |
Src-side test specifications
The infra/testing folder in V8 contains test specifications, consumed and
executed by the continuous infrastructure. Every master has an optional file
named <mastername>.pyl
. E.g. tryserver.v8.pyl
.
The structure of each file is:
{
<buildername>: [
{
'name': <test-spec name>,
'variant': <variant name>,
'shards': <number of shards>,
},
...
],
...
}
The <buildername>
is a string name of the builder to execute the tests.
<test-spec name>
is a label defining a test specification matching the
infra-side.
The <variant name>
is a testing variant as specified in
v8/tools/testrunner/local/variants.py
. <number of shards>
is optional
(default 1), but can be provided to increase the swarming shards for
long-running tests.
Example:
{
'v8_linux64_rel_ng_triggered': [
{'name': 'v8testing', 'variant': 'nooptimization', 'shards': 2},
],
}
Guidelines
Please keep trybots and continuous bots in sync. E.g. add the same configuration for the release and debug CI bots and the corresponding trybot (where applicable). E.g.
tryserver.v8:
v8_linux64_rel_ng_triggered
client.v8:
V8 Linux64
V8 Linux64 - debug