implement better control over test sharding and scheduling for typ |
|||
Issue descriptionCurrently the way typ manages scheduling tests is to get one big list of test cases and hand them out to N workers in a single banker-queue implementation. Some test suites (e.g., the GPU tests) want to control their own scheduling to provide profile-based schedules so that slower tests are scheduled first (I think this is supported today; if you pass the list of tests to run in, rather than letting typ do the test discovery, it'll just run the tests in order. But I should confirm this). Some test suites (e.g., the layout tests in non-random order mode) also want to control the ordering of tests. For example, all the tests in a directory go to a single worker, or tests in a single python class should all be scheduled together so setUpClass and tearDownClass can be called just once rather than per-test. typ needs to support better schedule control for the user to meet these two sets of needs.
,
Feb 27 2017
Actually, the GPU tests don't really care about which order the tests are run in per shard. The harness does however depend on the ability to determine which tests are run on which shard. I'm pretty sure this is already fully hooked up in Telemetry's browser_test_runner.
,
Mar 6 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 11 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by dpranke@chromium.org
, Feb 25 2017