From: Alyssa Ross <hi@alyssa.is>
To: 7c6f434c@mail.ru, cole.e.helbling@outlook.com
Cc: devel@spectrum-os.org
Subject: Re: [PATCH v2 2/2] chromiumOSPackages: 81.12871.0.0-rc1 -> 83.13020.0.0-rc1
Date: Mon, 01 Jun 2020 23:55:05 +0000 [thread overview]
Message-ID: <87367e9w9y.fsf@alyssa.is> (raw)
In-Reply-To: <E1jfttc-0000YO-0R.7c6f434c-mail-ru@smtp40.i.mail.ru>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
Michael Raskin <7c6f434c@mail.ru> writes:
>>>> In file included from gen/include/vm_protos/proto_bindings/fuzzer.grpc.pb.cc:5:
>>>> gen/include/vm_protos/proto_bindings/fuzzer.pb.h:38:10: fatal error: vm_crash.pb.h: No such file or directory
>>>> 38 | #include "vm_crash.pb.h"
>>>> | ^~~~~~~~~~~~~~~
>>>> compilation terminated.
>>>> ninja: build stopped: subcommand failed.
>>>> builder for '/nix/store/8asskz117p1nhirxaa4pwa0caayxg6c5-vm_protos-83.13020.0.0-rc1.drv' failed with exit code 1
>
> The first thing I would check if the same derivation builds elsewhere
> is the job count. Next step is checking the checksums of build
> inputs???
I job count is unlikely. On one computer I built with 4 cores, on the
other I built with 48. But Cole, it might be worth trying with a single
core.
Is there an easy way to get checksums of built inputs, or do I need to
do that manually?
Michael, does it build for you?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2020-06-01 23:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-30 19:00 [PATCH 1/2] chromiumOSPackages: improve update.py repo compat Alyssa Ross
2020-05-30 19:00 ` [PATCH 2/2] chromiumOSPackages: 81.12871.0.0-rc1 -> 83.13020.0.0-rc1 Alyssa Ross
2020-05-31 3:01 ` [PATCH v2 " Alyssa Ross
2020-05-31 23:49 ` Cole Helbling
2020-06-01 22:44 ` Alyssa Ross
2020-06-01 23:00 ` Alyssa Ross
2020-06-01 23:38 ` Michael Raskin
2020-06-01 23:55 ` Alyssa Ross [this message]
2020-06-02 0:37 ` [PATCH platform2] vm_tools: proto: fix parallel build Alyssa Ross
2020-06-02 0:39 ` Cole Helbling
2020-06-02 0:56 ` [PATCH v3 2/2] chromiumOSPackages: 81.12871.0.0-rc1 -> 83.13020.0.0-rc1 Alyssa Ross
2020-06-02 2:27 ` Cole Helbling
2020-06-02 3:19 ` Alyssa Ross
2020-06-02 8:39 ` [PATCH v3 2/2] chromiumOSPackages: 81.12871.0.0-rc1 ->83.13020.0.0-rc1 Michael Raskin
2020-05-30 23:47 ` [PATCH 1/2] chromiumOSPackages: improve update.py repo compat Cole Helbling
2020-06-02 3:30 ` Alyssa Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87367e9w9y.fsf@alyssa.is \
--to=hi@alyssa.is \
--cc=7c6f434c@mail.ru \
--cc=cole.e.helbling@outlook.com \
--cc=devel@spectrum-os.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).