Searched refs:minutes (Results 1 – 10 of 10) sorted by relevance
| /test/vti/test_serving/gae/webapp/src/testing/ |
| D | unittest_base.py | 310 def PassTime(self, hours=0, minutes=0, seconds=0): argument
321 if not hours and not minutes and not seconds:
329 hours=hours, minutes=minutes, seconds=seconds)
332 hours=hours, minutes=minutes, seconds=seconds)
|
| /test/vti/test_serving/gae/webapp/src/scheduler/ |
| D | schedule_worker_test.py | 166 self.PassTime(minutes=schedule_period_minute + 1)
180 self.PassTime(minutes=schedule_period_minute + 1)
185 self.PassTime(minutes=schedule_period_minute + 1)
272 self.PassTime(minutes=schedule_period_minute + 1)
287 self.PassTime(minutes=schedule_period_minute + 1)
328 minutes=schedule_worker.BOOTUP_ERROR_RETRY_INTERVAL_IN_MINS + 1)
343 minutes=schedule_worker.BOOTUP_ERROR_RETRY_INTERVAL_IN_MINS - 1)
358 self.PassTime(minutes=long_period - 1 - (
368 self.PassTime(minutes=2)
|
| D | schedule_worker.py | 432 minutes=self.GetCorrectedPeriod(schedule))):
|
| /test/vti/test_serving/gae/webapp/src/utils/ |
| D | model_util_test.py | 91 minutes=(period + 10))
149 minutes=(period + 10))
|
| /test/vti/dashboard/src/main/webapp/js/ |
| D | time.js | 59 } else if (duration.minutes() > 0) {
|
| /test/vts/doc/developer_testing/kernel/ |
| D | run_all_ltp_testcases.md | 11 This will take from 30 minutes to 2 hours to run.
|
| /test/vti/dashboard/ |
| D | README.md | 254 This procedure can take up to fifteen minutes.
257 You'll have to wait up to five minutes for the next uptime check to fail. The alert and notificatio…
|
| /test/vts/runners/target/vts_hal_hidl_target/ |
| D | VtsHalHidlTargetCallbackBase.h | 33 constexpr milliseconds DEFAULT_CALLBACK_WAIT_TIMEOUT_INITIAL = minutes(1);
|
| /test/vti/test_serving/proto/ |
| D | TestScheduleConfigMessage.proto | 63 // Scheduling period in minutes
|
| /test/mlts/benchmark/results/ |
| D | Chart.bundle.min.js | 10 …minutes(),e)})}function ee(t,e){return e._meridiemParse}j("H",["HH",2],0,"hour"),j("h",["hh",2],0,…
|