test_push: Replace paygen test suite with a single paygen test. |
|||||||
Issue descriptionpaygen tests use provision flow in a weird way, so we want to keep some paygen testing in test_push. OTOH, it's the longest step in testing right now. Let's replace the suite with any one of the constituent tests to speed up testing without any loss of coverage. From original email discussion: pprabhu: Here are the times for the various suites in test_push tonight. I know that control.testbed_push has been misbehaving lately, but it finished OK tonight. The long tail was clearly paygen_au_beta. It feels like we're trying too hard with the paygen tests here: control.testbed_push: 15 minutes control.push_to_prod: 18 minutes control.dummy: 8 minutes control.paygen_au_beta: 52 minutes The paygen_au_beta suite creates 5 tests. Do we really need 5 different paygen au tests to gain confidence in the infra? Can we drop some here? These are distributed across the two squawks in the test bed right now. OTOH, there are 6 gandofs, sitting idle except for the first 7 minutes of the paygen_au_beta suite (in this one instance). Can we switch things around so that we run maybe some of these paygen tests on the gandof instead?
,
Nov 29 2016
,
Nov 29 2016
,
Nov 29 2016
Hmm, as I say, I can do the second part. As for the first part, I think a person who is more familiar with paygen suite could be a better owner. Decrease its priority to 3, since it is not urgent. Good candidate for fixit
,
Jan 13 2017
Possibly fixit bug for product people during our fixit week.
,
Jan 13 2017
This falls in infra proper. This bug is only about test_push, to speed it up by reducing the number of tests we run. This is now less important after shuqianz@'s work. We no longer start the test_push when we actually want to push, so latency in the test is less critical.
,
Feb 16 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
,
May 15 2018
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by shuqianz@chromium.org
, Nov 18 2016