Release tryjobs with --version writing build artifacts to overlapping directory. |
|||||
Issue descriptionThese two tryjobs: https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8947068711660284112 https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8947069934271423200 Wrote their build artifacts to: https://pantheon.corp.google.com/storage/browser/chromeos-image-archive/lars-release-tryjob/R68-10645.0.0 That is different from production builds, because the build config name is different, but all release tryjob builds will share the same directory. This means that the build artifacts have undefined contents, and that hwtests (which use those artifacts) against release-tryjob builds are meaningless as well.
,
May 9 2018
Hum... this might be specific to builds performed with --version. The two builds above were launched with: $ cros tryjob --version 10645.0.0 -g 1049109 lars-release-tryjob and $ cros tryjob --version 10645.0.0 lars-release-tryjob
,
May 9 2018
And here is a release tryjob without --version that seems to have a unique directory like we would expect. https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8947016310567076448
,
Jul 27
Over to Don to verify fix.
,
Jul 27
Running this tryjob: cros tryjob --version 10916.0.0 eve-release-tryjob https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8939814991650487776
,
Aug 1
,
Dec 12
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by gmx@chromium.org
, May 9 2018