asuka factory image failed to build |
||||||||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of dianwa@google.com asuka-release:2108 failed Log: https://luci-logdog.appspot.com/v/?s=chromeos%2Fbb%2Fchromeos%2Fasuka-release%2F2108%2F%2B%2Frecipes%2Fsteps%2FArchive%2F0%2Fstdout Builders failed on: - asuka-release: http://cros-goldeneye/chromeos/healthmonitoring/buildDetails?buildbucketId=8949368559273426896
,
Apr 13 2018
The problem is that the factory image failed to build:
Traceback (most recent call last):
File "/b/c/cbuild/repository/chromite/lib/parallel.py", line 442, in _Run
self._task(*self._task_args, **self._task_kwargs)
File "/b/c/cbuild/repository/chromite/cbuildbot/stages/artifact_stages.py", line 211, in BuildAndArchiveFactoryImages
alias = commands.BuildFactoryInstallImage(buildroot, board, extra_env)
File "/b/c/cbuild/repository/chromite/cbuildbot/commands.py", line 1994, in BuildFactoryInstallImage
enter_chroot=True)
File "/b/c/cbuild/repository/chromite/cbuildbot/commands.py", line 136, in RunBuildScript
raise failures_lib.BuildScriptFailure(ex, cmd[0])
File "/b/c/cbuild/repository/chromite/cbuildbot/commands.py", line 136, in RunBuildScript
raise failures_lib.BuildScriptFailure(ex, cmd[0])
BuildScriptFailure: ./build_image failed (code=1)
Check the blamelist for changes that might have broken factory images,
and then pass the buck.
,
Apr 13 2018
the blamelist: https://crosland.corp.google.com/log/10569.1.0..10575.0.0 I believe that only two commits related to this error: 1. commands.py, CL: https://chromium-review.googlesource.com/998981 2. artifact_stages.py, CL: https://chromium-review.googlesource.com/996564 Probably the second one triggered the issue. cc-ed the first one author.
,
Apr 13 2018
This isn't related to CL:998981. It doesn't look related to CL:996564 either. It looks to me like another instance of crbug.com/796254.
,
Apr 13 2018
Yeah, this isn't caused by a chromite change. The blamelist has four changes to src/platform/factory, and one more to src/platform/factory-private. Any one of those might conceivably cause a problem, but it looks far more likely that this is a duplicate of bug 796254. If it's actually a duplicate, I think the problem should show itself as flake; that is, it will succeed with the next build.
,
Apr 13 2018
,
Apr 13 2018
Might be similar to the issue with setzer as well. That looked like a one-time occurrence, so I didn't create a bug for that yet. Failed to mount all partitions in /mnt/host/source/src/build/images/setzer/R67-10575.0.0-a3/factory_install_shim.bin I agree with Hungte, probably a dup of bug 796254.
,
Apr 13 2018
I meant, agree with Richard...
,
Apr 13 2018
Removing myself as owner; my change had nothing to do with this.
,
Apr 14 2018
factory_install_shim is built by 'build_image factory_install', which uses resources mainly from initramfs, src/platform/factory_installer. All the changes to src/platform/factory listed there are not related to building factory_install. Also, factory-private is a repo not used by any ebuilds yet (that's why we're cleaning it up). So unless this keeps happening, I think it's not related to those changes.
,
May 9 2018
Not an infra problem
,
Nov 6
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by dianwa@chromium.org
, Apr 13 2018Components: Infra>Client>ChromeOS