Please update the Chrome pinning tool with instructions that would guide gardeners to interact with the chrome TPMs before they do a manual uprev of Chrome on the Chrome OS waterfall.
A master Chrome PFQ build id argument is required. It must satisfy the following requirements:
If you are a gardener trying to uprev Chrome please verify if the Chrome version you are trying to uprev to is stable and not crashy. Please communicate with the corresponding Chrome TPM to find out if that Chrome has any known issues or is particularly crashy. If yes, please work with them to find a stable Chrome that can be used to uprev.
The current Chrome PFQ run is a failed run;
No successful Chrome PFQ runs after this Chrome PFQ run;
Master build of this PFQ run must have passed BinhostTest stage;
All important slave builds of this PFQ run must have passed UploadPrebuiltsTest stage.
A bug id is required to track each manual uprev, describing the known source of flake that is responsible for this run’s failure.
Comment 1 by bugdroid1@chromium.org
, Jun 23 2017