betty-arcnext-paladin VMTests take too long, sometimes time out |
|
Issue descriptionSuccessful run, it took 80 minutes: https://ci.chromium.org/p/chromeos/builders/luci.chromeos.general/CQ/b8931602729375295472 check the timestamps in the log of that stage: https://luci-logdog.appspot.com/logs/chromeos/buildbucket/cr-buildbucket.appspot.com/8931602729375295472/+/steps/VMTest__attempt_1_/0/stdout Here, first attempt timed out after 90 minutes: https://ci.chromium.org/p/chromeos/builders/luci.chromeos.general/CQ/b8931574423642871680 Check the logs, it actually failed: https://logs.chromium.org/logs/chromeos/buildbucket/cr-buildbucket.appspot.com/8931574423642871680/+/steps/VMTest__attempt_1_/0/stdout VMTests apparently take < 60 minutes on betty-paladin, maybe something specific ARC++ P makes the tests take longer? Assigning to sheriffs for triage.
,
Oct 27
Ben, do you know who this should be assigned to? |
|
►
Sign in to add a comment |
|
Comment 1 by furquan@google.com
, Oct 27Owner: benzh@chromium.org