patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: 7c6f434c@mail.ru, cole.e.helbling@outlook.com
Cc: devel@spectrum-os.org
Subject: [PATCH platform2] vm_tools: proto: fix parallel build
Date: Tue,  2 Jun 2020 00:37:09 +0000	[thread overview]
Message-ID: <20200602003709.20514-1-hi@alyssa.is> (raw)
In-Reply-To: <87367e9w9y.fsf@alyssa.is>

fuzzer-protos depends on vm-crash-rpcs, but this dependency wasn't
declared, causing build failures like the following:

[26/52] CXX obj/out/Release/gen/include/vm_protos/proto_bindings/libfuzzer-protos.fuzzer.grpc.pb.o
FAILED: obj/out/Release/gen/include/vm_protos/proto_bindings/libfuzzer-protos.fuzzer.grpc.pb.o
c++ -MMD -MF obj/out/Release/gen/include/vm_protos/proto_bindings/libfuzzer-protos.fuzzer.grpc.pb.o.d -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -Igen/include -I../../common-mk -I/usr/include -Igen -Igen -Igen -Igen -Wall -Wunused -Wno-unused-parameter -Wunreachable-code -ggdb3 -fstack-protector-strong -Wformat=2 -fvisibility=internal -Wa,--noexecstack -Wimplicit-fallthrough -Werror --sysroot= -fPIE -fvisibility=default -pthread -I/nix/store/pjl2q3lny3c18ypqjcv0q3akyq89hg2i-grpc-1.28.1/include -I/nix/store/hya0y6slws66h99njc2yiz02irfv4n62-openssl-1.1.1g-dev/include -I/nix/store/mfpg3sk5vk9rm99hbpmd3dgvxqybd391-protobuf-3.8.0/include -pthread -I/nix/store/pjl2q3lny3c18ypqjcv0q3akyq89hg2i-grpc-1.28.1/include -I/nix/store/hya0y6slws66h99njc2yiz02irfv4n62-openssl-1.1.1g-dev/include -I/nix/store/mfpg3sk5vk9rm99hbpmd3dgvxqybd391-protobuf-3.8.0/include -Wno-unreachable-code -std=gnu++14 -fno-exceptions -fno-unwind-tables -fno-asynchronous-unwind-tables -Wno-psabi -c gen/include/vm_protos/proto_bindings/fuzzer.grpc.pb.cc -o obj/out/Release/gen/include/vm_protos/proto_bindings/libfuzzer-protos.fuzzer.grpc.pb.o
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.

Reported-by: Cole Helbling <cole.e.helbling@outlook.com>
---

> 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?

Looks like it was a parallelism bug after all.  Interesting that Cole 
saw it and I didn't, even with my -j48 build.

Cole, could you please test this patch?

The easiest way is probably to save the email, and then add 
platform2Patches = [ /path/to/email ]; to the vm_protos expression.

 vm_tools/proto/BUILD.gn | 1 +
 1 file changed, 1 insertion(+)

diff --git a/vm_tools/proto/BUILD.gn b/vm_tools/proto/BUILD.gn
index 713b81853..a25265cab 100644
--- a/vm_tools/proto/BUILD.gn
+++ b/vm_tools/proto/BUILD.gn
@@ -70,6 +70,7 @@ proto_library("fuzzer-protos") {
   deps = [
     ":container-rpcs",
     ":tremplin-rpcs",
+    ":vm-crash-rpcs",
   ]
   sources = [
     "${proto_in_dir}/fuzzer.proto",
-- 
2.26.2

  reply	other threads:[~2020-06-02  0:37 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
2020-06-02  0:37             ` Alyssa Ross [this message]
2020-06-02  0:39               ` [PATCH platform2] vm_tools: proto: fix parallel build 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=20200602003709.20514-1-hi@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).