New issue
Advanced search Search tips

Issue 917083 link

Starred by 2 users
Status: Assigned
Owner:
hidehiko@chromium.org
Cc:
derat@chromium.org
hidehiko@chromium.org
nya@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Introduce Tast stress test.

Project Member Reported by hidehiko@chromium.org, Dec 20 
Current our priority is to port autotests running in CQ into Tast.
login_LoginSuccess is one of the target, but it is used also for stress test, too.

It'd be nice if we could introduce Tast stress tests, then login_LoginSuccess.stress can also run as a part of Tast.
This is important because, otherwise, it is necessary to maintain both login_LoginSuccess.stress in autotest and ported login_LoginSuccess in tast in parallel. Keeping them in sync seems to be higher cost.

Comment 1 by derat@chromium.org, Dec 26 

Would it be possible to move the common logic into a subpackage so both the normal and "stress" versions of the test can call it?

I'd previously thought about adding an -iterations or similar flag to "tast run" that could be used to tell it to run the entire set of selected tests multiple times, but that sounds like it probably isn't what's needed here.

Comment 2 by hidehiko@chromium.org, Jan 2

Owner: hidehiko@chromium.org
Status: Assigned (was: Untriaged)
Re #1; Yes, using subpackage is what I was thinking, at least for the first step.
AFAIK, we only have several stress tests, so let's move forward with this simple approach now.
►

Sign in to add a comment