firka/flutter
firka/flutter
5
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

update devicelab docs (#9274)

Browse Source
This commit is contained in:
Yegor 2017-04-06 16:27:29 -07:00 committed by GitHub
parent bb0adcb873
commit d538c11486
2 changed files with 17 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
dev/devicelab/README.md
View File

@ -57,7 +57,7 @@ To run tests from a specific stage, use option `-s` (`--stage`):
dart bin/run.dart -s {NAME_OF_STAGE} dart bin/run.dart -s {NAME_OF_STAGE}
``` ```
Currently there are only two stages defined, `devicelab` and `devicelab_ios`. Currently there are only three stages defined, `devicelab`, `devicelab_ios` and `devicelab_win`.
# Reproducing broken builds locally # Reproducing broken builds locally

33
dev/devicelab/manifest.yaml
View File

@ -10,25 +10,24 @@
# Each key in this dictionary is the unique name of a task, which also # Each key in this dictionary is the unique name of a task, which also
# corresponds to a file in the "bin/" directory that the task runner will run. # corresponds to a file in the "bin/" directory that the task runner will run.
# #
# Due to historic reasons that may go away at some point, the suffix of the task # Required properties:
# name is significant. It is used by the dashboard to pick the right HTML
# template to display the results in a card. If you use a known name suffix also
# make sure that your task outputs data in the expected format for that card.
# #
# Known suffixes: # * description: free form string
# describes what the task is about
# * stage: one of "devicelab", "devicelab_ios", "devicelab_win"
# tasks are grouped by stage so they appear next to each on the dashboard and have a distinct
# icon attached to them. Stages can be used to create dependencies, e.g. we may decide to not
# run device tests on red Travis.
# * required_agent_capabilities: a list of strings
# list of capabilities a devicelab agent must have to be able to run this task.
# #
# __analysis_time: # Optional properties:
# Analyzer performance benchmarks. #
# __refresh_time: # * flaky: boolean true or false
# Edit refresh cycle benchmarks. # whether the task is considered flaky; the result of running a flaky task does not affect
# __start_up: # the overall build status.
# Application startup speed benchmarks. # * timeout_in_minutes: integer
# __timeline_summary: # a custom task timeout, specified in minutes.
# Per-frame timings and missed/average/total counts.
# __transition_perf:
# Flutter Gallery app transitions benchmark.
# __size:
# Application size benchmarks.
tasks: tasks:
# Deviceless tests # Deviceless tests