repos in bad shape, can no longer emerge or deploy
189 views
Skip to first unread message
Joe Trovato
Mar 21, 2019, 12:51:43 AM3/21/19
to Chromium OS Development
Hi There,
I am pretty new to the forum and CrOS development so I apologize for any dumb questions while I'm getting my bearings.
I think there is something corrupt in my repos. I was working in a separate branch for a while pretty happily but recently did some repo uploads, rebases, and syncing and I can't seem to get back to a working point.
the output of repo status is:
(cr) parallels@ubuntu ~/trunk/src $ repo status
project chromium/tools/depot_tools/ branch master
project src/scripts/ branch master
project src/third_party/chromiumos-overlay/ branch new_brydge_keyboard_updatesWhen I try to emerge anything I get the following:
(cr) (master) parallels@ubuntu ~/trunk/src/third_party/brydge-updater $ emerge-$BOARD -av1 chromeos-base/weida_wdt_util
"/build/eve/etc/make.conf.board", line 18: /mnt/host/source/src/third_party/chromiumos-overlay/chromeos/binhost/target/amd64-generic-POSTSUBMIT_BINHOST.conf: No such file or directoryTo fix this I tried to ./build_packages but that failed, I then tried to ./setup_board --board-$BOARD and was told that that script is deprecated. so I ran setup_board --board-$BOARD and that failed to emerge protobuf with the following output:
=== Complete: job protobuf-c-1.1.1 (0m16.4s) ===
Failed dev-libs/protobuf-c-1.1.1 (in 0m16.4s). Your build has failed.
Pending 4/72, [Time 22:29:15 | Elapsed 12m22.9s | Load 4.73 6.13 3.79]
ERROR : Wed Mar 20 22:29:17 MDT 2019
ERROR : PGID PPID PID ELAPSED TIME %CPU COMMAND
ERROR : 8 4 8 34:42 00:00:00 0.0 -bash
ERROR : 7764 8 7764 17:33 00:00:00 0.0 \_ python2 /mnt/host/source/chromite/bin/setup_board --board=eve
ERROR : 7764 7764 7769 17:33 00:00:00 0.0 \_ /bin/bash /mnt/host/source/src/scripts/update_chroot --toolchain_boards eve --usepkg
ERROR : 7764 7769 6775 00:00 00:00:00 0.0 \_ /bin/bash /mnt/host/source/src/scripts/update_chroot --toolchain_boards eve --usepkg
ERROR : 7764 6775 6776 00:00 00:00:00 0.0 \_ ps f -o pgid,ppid,pid,etime,cputime,%cpu,command
ERROR : Arguments of 7769: '--toolchain_boards' 'eve' '--usepkg'
ERROR : Backtrace: (most recent call is last)
ERROR : update_chroot:128:main(), called: die_err_trap
ERROR :
ERROR : Command failed:
ERROR : Command 'sudo -E ${EMERGE_CMD} "${EMERGE_FLAGS[@]}" virtual/target-sdk world' exited with nonzero code: 1
setup_board: Unhandled exception:
Traceback (most recent call last):
File "/mnt/host/source/chromite/bin/setup_board", line 170, in <module>
DoMain()
File "/mnt/host/source/chromite/bin/setup_board", line 166, in DoMain
commandline.ScriptWrapperMain(FindTarget)
File "/mnt/host/source/chromite/lib/commandline.py", line 959, in ScriptWrapperMain
ret = target(argv[1:])
File "/mnt/host/source/chromite/scripts/setup_board.py", line 129, in main
setup_board.SetupBoard(opts.board_conf, opts.accept_licenses, opts.run_config)
File "/mnt/host/source/chromite/service/setup_board.py", line 162, in SetupBoard
cros_build_lib.RunCommand(update_chroot)
File "/mnt/host/source/chromite/lib/cros_build_lib.py", line 654, in RunCommand
raise RunCommandError(msg, cmd_result)
chromite.lib.cros_build_lib.RunCommandError: return code: 1; command: /mnt/host/source/src/scripts/update_chroot --toolchain_boards eve --usepkg
cmd=['/mnt/host/source/src/scripts/update_chroot', '--toolchain_boards', 'eve', '--usepkg']I am at a loss of what to try. I am pretty hesitate to blow everything away and start fresh with the developers guide as it took about 13 hours to by initial ./build_packages. Is there an easier way to "reset" and get back to a workable point? Let me know if this is enough info to go off of or how I can better solicit help.
Thanks!
Mike Frysinger
Mar 21, 2019, 12:56:46 AM3/21/19
to Joe Trovato, Chromium OS Development
that doesn't include the full error. you need to look above where you snipped.
you can run `./update_chroot` to focus on the failing part
-mike
--
--
Chromium OS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-dev
Message has been deleted
Mike Frysinger
Mar 21, 2019, 1:32:22 AM3/21/19
to Joe Trovato, Chromium OS Development
your build seems to be trying to downgrade protobuf which isn't going to work:
[ebuild UD ] dev-libs/protobuf-c-1.1.1:0/0::chromiumos [1.3.1:0/1.0.0::chromiumos] USE="-static-libs -test" ABI_X86="(64) -32 (-x32)" 0 KiB
that shouldn't even be possible because we don't have those versions around anymore. that implies your tree isn't actually synced to ToT, so you should double check `repo sync` and `repo status` before trying to build things.
-mike
On Wed, Mar 20, 2019 at 10:21 PM Joe Trovato <josephj...@gmail.com> wrote:
Sorry about that! Full output below. It seems metrics and protobuf are failing, but I can't quite figure out why... especially since I'm up-to-date with master...
Joe Trovato
Mar 21, 2019, 10:05:23 AM3/21/19
to Chromium OS Development, josephj...@gmail.com
Thanks Mike!
I think I did have some weird stuff going on with my repo sync. After running that, ./update_chroot succeeds now but I tried to build_pacakges again and errored out. I am now facing an error in what seem like goma. From what I can tell goma should be used on local builds so I am not sure why I am getting these error. The actual error might be farther up, but my terminal is clipping the output before I can find anything else that points to an error. Any debugging tips would be awesome! Thanks for the help
ERROR : Wed Mar 20 23:59:27 MDT 2019ERROR : PGID PPID PID ELAPSED TIME %CPU COMMANDERROR : 8 4 8 54:25 00:00:00 0.0 -bashERROR : 2586 8 2586 18:40 00:00:00 0.0 \_ /bin/bash ./build_packages --board=eveERROR : 2586 2586 4736 00:00 00:00:00 0.0 \_ /bin/bash ./build_packages --board=eveERROR : 2586 4736 4737 00:00 00:00:00 0.0 \_ ps f -o pgid,ppid,pid,etime,cputime,%cpu,commandERROR : Arguments of 2586: ./build_packages '--board=eve'ERROR : Backtrace: (most recent call is last)ERROR : build_packages:365:main(), called: die_err_trap ERROR : ERROR : Command failed:ERROR : Command '( if [[ "${FLAGS_run_goma}" -eq "${FLAGS_TRUE}" ]]; thenERROR : info "Starting goma compiler_proxy."; goma_ctl="${GOMA_DIR:-${HOME}/goma}/goma_ctl.py"; "${goma_ctl}" restart; trap "'${goma_ctl}' stop" EXIT;ERROR : fi; GOMA_WRAPPER=(); if [[ "${FLAGS_build_all_with_goma}" -eq "${FLAGS_TRUE}" ]]; thenERROR : warn "The build_all_with_goma feature is still under development."; warn "This feature is experimental and may potentially break your build."; GOMA_WRAPPER=("${GOMA_DIR:-${HOME}/goma}/goma-wrapper" -j600 -l100);ERROR : fi; sudo -E "${GOMA_WRAPPER[@]}" "${EMERGE_CMD[@]}" "${EMERGE_FLAGS[@]}" "${PACKAGES[@]}" )' exited with nonzero code: 1
...
Alex Klein
Mar 21, 2019, 11:54:04 AM3/21/19
to Chromium OS Development, josephj...@gmail.com
I'm guessing it's above. Try just redirecting the output to a file -- `./build_packages --board=eve > output 2>&1` -- then you can look through it after it's done.
Mike Frysinger
Mar 21, 2019, 11:54:49 AM3/21/19
to Joe Trovato, chromium-os-dev
yes, the error is higher up
-mike
--
Mike Frysinger
Mar 21, 2019, 11:36:41 PM3/21/19
to Joe Trovato, Chromium OS Development
(chromeos-base/libbrillo-9999:0/9999.0::chromiumos, ebuild scheduled for merge to '/build/eve/') pulled in by
chromeos-base/libbrillo:0/9999.0= required by (chromeos-base/policy_utils-0.0.1-r23:0/0::chromiumos, installed in '/build/eve/')
^^^^^^^^^^
(chromeos-base/libbrillo-0.0.1-r1450:0/0.0.1.0::chromiumos, binary scheduled for merge to '/build/eve/') pulled in by
chromeos-base/libbrillo:0/0.0.1.0= required by (chromeos-base/authpolicy-0.0.1-r1283:0/0::chromiumos, binary scheduled for merge to '/build/eve/')
^^^^^^^^^^^
it looks like you've cros workon started libbrillo. you prob don't want to be doing that, so use `cros_workon-eve stop libbrillo`.
-mike
--
Joe Trovato
Mar 22, 2019, 12:12:59 AM3/22/19
to Chromium OS Development, josephj...@gmail.com
yup! I got that far and got the following. Now might be a good time to note that I am editing this file to actually point at local code to do development. It must be conflicting with the real weida_wdt_util. I've attached my modified ebuild. I could not figure out how to create my own package and get it to emerge and deploy. Help on any of these issues would be awesome. Thank you for the timely, helpful responses.
(cr) (master) parallels@ubuntu ~/trunk/src/scripts $ cros_workon-eve stop librillo21:37:39: WARNING: Filtering out malformed line: # required by chromeos-base/weida_wdt_util (argument)
21:37:39: WARNING: Filtering out malformed line: # /build/eve/etc/portage/package.mask/cros-workon:
21:37:39: WARNING: Filtering out malformed line: =chromeos-base/weida_wdt_util-0.9.6
21:37:39: WARNING: Filtering out malformed line: # required by chromeos-base/weida_wdt_util (argument)
21:37:39: WARNING: Filtering out malformed line: # /build/eve/etc/portage/package.mask/cros-workon:
21:37:39: WARNING: Filtering out malformed line: =chromeos-base/weida_wdt_util-0.9.6
21:37:39: WARNING: Could not find canonical package for "librillo"
21:37:39: ERROR: Error parsing package list...
Mike Frysinger
Mar 22, 2019, 12:32:36 AM3/22/19
to Joe Trovato, Chromium OS Development
please do not edit the cros-workon files. that is managed by our tools. delete it and restart things.
-mike
--
Joe Trovato
Mar 22, 2019, 12:44:19 AM3/22/19
to Mike Frysinger, Chromium OS Development
What do you mean? Delete the ebuild file, repo sync, and build_packages? That will probably get me back to a clean build, but now I am a bit stuck on how to develop a custom package. I had to add a src_unpack() call to that ebuild to point to a local folder so I could emerge and deploy my code to my device. I was looking for a better work flow but this is what I was told to do by a googler I have been working with.
Joe
Mike Frysinger
Mar 22, 2019, 12:49:56 AM3/22/19
to Joe Trovato, Chromium OS Development
your error message listed a file with errors in it. it's a symlink to a different file. i'm suggesting you clear the contents of it and not mess with masking internals like you've been doing. it's not a supported flow.
/build/eve/etc/portage/package.mask/cros-workon
-mike
Joe Trovato
Mar 24, 2019, 1:17:49 PM3/24/19
to Chromium OS Development, josephj...@gmail.com
Hello,
I think I am back to a clean checkout! What is the supported workflow if I want to create a new package? I want to write some code, probably on my host computer inside my chroot, emerge it for my dev board (eve), and deploy it to test.
Would really appreciate some help getting into a sustainable workflow.
Thanks!
...
Carlo Caione
Mar 25, 2019, 6:33:06 AM3/25/19
to Joe Trovato, Chromium OS Development
On 24/03/2019 17:17, Joe Trovato wrote:
> Hello,
>
> I think I am back to a clean checkout! What is the supported workflow if
> I want to create a new package? I want to write some code, probably on
> my host computer inside my chroot, emerge it for my dev board (eve), and
> deploy it to test.
>
> Would really appreciate some help getting into a sustainable workflow.
What I usually do is to create a new board overlay and work adding a
> Hello,
>
> I think I am back to a clean checkout! What is the supported workflow if
> I want to create a new package? I want to write some code, probably on
> my host computer inside my chroot, emerge it for my dev board (eve), and
> deploy it to test.
>
> Would really appreciate some help getting into a sustainable workflow.
dependency for the new package on the BSP package.
See
https://www.chromium.org/chromium-os/how-tos-and-troubleshooting/chromiumos-board-porting-guide
--
Carlo Caione
Tom Hughes
Mar 25, 2019, 11:34:26 AM3/25/19
to Carlo Caione, Joe Trovato, Chromium OS Development
Hmm, I guess the Developer Guide doesn't describe this (only mentions modifying existing packages): https://chromium.googlesource.com/chromiumos/docs/+/master/developer_guide.md
You'll want to create a new ebuild for your project. ebuilds can get set to fetch the source code as a tarball as well as other sources like a git repo. You probably do want to version your code as you develop (even if it's only a local git repo). Here's an example of a package that fetches the source from github:
More info on ebuilds:
Tom
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages