New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 909972 link

Starred by 1 user
Status: Assigned
Owner:
yshaul@chromium.org
Cc:
dgarrett@google.com
█ leecy@chromium.org
dchan@chromium.org
ahass...@chromium.org
dhadd...@chromium.org
chromeos-continuous-integration-fire-hose@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Unibuild: Restrict paygen_au_stable FSI tests to the model that they belong to

Project Member Reported by dhaddock@google.com, Nov 29 
b/120164701 lists the work to be done to edit paygen.json to include FSIs by model

During the PaygenBuildStable phase, the builder will 
1. use the paygen.json file to generate the right payloads for the current build. 
2. generate the control files to run AU tests for each payload.
3. zip the control files and puts them on google storage.
e.g gs://chromeos-image-archive/veyron_minnie-release/R71-11151.46.0/paygen_au_stable_control.tar.bz2

During the PaygenTestStable phase, the builder will
1. kick off the paygen_au_stable [1] test suite. The control file will stage the zip file created in the PaygenBuildStable stage and kick off each of the AU tests.

For coral we are running all of the tests (e.g gs://chromeos-image-archive/coral-release/R70-11021.93.0/paygen_au_stable_control.tar.bz2) on all of the models in the lab. 

We instead need to run each FSI AU test only on the model(s) that it belongs to. 


[1]https://cs.corp.google.com/chromeos_public/src/third_party/autotest/files/test_suites/control.paygen_au_stable

Comment 1 by dhaddock@google.com, Nov 29 

A bit more information to think about

Each paygen_au_stable run will be doing three different update types 
1. N to N 
2. Build-Serving-on-Omaha to N
3. FSI to N

I think it is OK to continue having every coral model run AU tests for the first two types. Then just run the FSI tests on the associated coral model(s)

Comment 2 by dhadd...@chromium.org, Jan 10

Status: Assigned (was: Untriaged)
►

Sign in to add a comment