Lines Matching refs:Lab
19 launch jobs in the ChromeOS Hardware Lab (or against a local Autotest instance
58 ### Running jobs in the lab
60 `test_that` now allows you to run jobs in the test lab. The usage is similar to
61 running tests against a specified host. The keyword :lab: is used as
72 $ test_that -b lumpy -i lumpy-paladin/R38-6009.0.0-rc4 :lab: dummy_Pass
75 This will kick off a suite in the lab that consists of just 1 job, dummy\_Pass,
77 lumpy-paladin/R38-6009.0.0-rc4. The lab's scheduler will take responsibility
86 $ test_that -b lumpy -i ${latest_image} :lab: dummy_Pass dummy_Fail
87 $ test_that -b lumpy -i ${latest_image} :lab: e:login_.*
90 Kicking off a run in the lab should be useful whenever you need to run a
92 locally.For occasional runs of ad-hoc suites in the lab, this will also avoid
98 test_that -b peach_pit :lab: suite:pyauto_perf -i 'peach_pit-release/R32-4763.0.0'
104 Things to note about running in the lab:
121 MobLab instance. This usage is similar to running tests in the lab. The argument
127 $ test_that -b lumpy -i lumpy-paladin/R38-6009.0.0-rc4 --web 100.96.51.136 :lab:
