how to see the compile logs when executing from the spwaned process? #628

woss · 2022-02-07T15:54:42Z

woss
Feb 7, 2022

I'm using nodejs spawn with the spwanedProcess.stdout and I am only getting the cargo make output, not the compile. As you can see this time it failed, and I have not idea telling what happened.

Any idea how to pipe the output?

sagiegurari · 2022-02-07T19:07:39Z

sagiegurari
Feb 7, 2022
Maintainer

can you share the relevant part of your makefile.toml?

1 reply

woss Feb 7, 2022
Author

here is the full Makefile.toml https://gitlab.com/anagolay/old-op-file/-/blob/main/Makefile.toml

sagiegurari · 2022-02-08T10:32:08Z

sagiegurari
Feb 8, 2022
Maintainer

I created a gitpod workspace for your repo.
i installed cargo-make + wasm (using cargo make install-wasm-pack)
i ran cargo make build-operation-flow and it works ok

gitpod /workspace/old-op-file (main) $ cargo make build-operation-flow
[cargo-make] INFO - cargo make 0.35.8
[cargo-make] INFO - Project: op-file
[cargo-make] INFO - Build File: Makefile.toml
[cargo-make] INFO - Task: build-operation-flow
[cargo-make] INFO - Profile: development
[cargo-make] INFO - Running Task: legacy-migration
[cargo-make] INFO - Execute Command: "cargo" "build" "--release" "--all-features"
[cargo-make] INFO - Execute Command: "wasm-pack" "build" "--target" "bundler" "--out-name" "index" "--out-dir" "pkg/release/esm" "--release"
[cargo-make] INFO - Execute Command: "wasm-pack" "build" "--target" "nodejs" "--out-name" "index" "--out-dir" "pkg/release/nodejs" "--release"
[cargo-make] INFO - Execute Command: "wasm-pack" "build" "--target" "web" "--out-name" "index" "--out-dir" "pkg/release/web" "--release"
[cargo-make] INFO - Execute Command: "wasm-pack" "build" "--target" "no-modules" "--out-name" "index" "--out-dir" "pkg/release/no-modules" "--release"
    Blocking waiting for file lock on package cache
    Finished release [optimized] target(s) in 0.03s
[INFO]: Checking for the Wasm target...
[INFO]: Checking for the Wasm target...
[INFO]: Checking for the Wasm target...
[INFO]: Checking for the Wasm target...
[INFO]: Compiling to Wasm...
[INFO]: Compiling to Wasm...
[INFO]: Compiling to Wasm...
[INFO]: Compiling to Wasm...
    Finished release [optimized] target(s) in 0.02s
[INFO]: origin crate has no LICENSE
[INFO]: Installing wasm-bindgen...
    Blocking waiting for file lock on package cache
    Finished release [optimized] target(s) in 0.02s
[INFO]: origin crate has no LICENSE
[INFO]: Installing wasm-bindgen...
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on package cache
[INFO]: Optimizing wasm binaries with `wasm-opt`...
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on build directory
    Finished release [optimized] target(s) in 0.04s
[INFO]: origin crate has no LICENSE
[INFO]: Installing wasm-bindgen...
    Finished release [optimized] target(s) in 0.05s
[INFO]: origin crate has no LICENSE
[INFO]: Optimizing wasm binaries with `wasm-opt`...[INFO]: Installing wasm-bindgen...

[INFO]: Optimizing wasm binaries with `wasm-opt`...
[INFO]: Optimizing wasm binaries with `wasm-opt`...
[INFO]: :-) Done in 4.44s
[INFO]: :-) Your wasm pkg is ready to publish at /workspace/old-op-file/pkg/release/esm.
[INFO]: :-) Done in 4.53s
[INFO]: :-) Your wasm pkg is ready to publish at /workspace/old-op-file/pkg/release/nodejs.
[INFO]: :-) Done in 4.72s
[INFO]: :-) Your wasm pkg is ready to publish at /workspace/old-op-file/pkg/release/no-modules.
[INFO]: :-) Done in 4.76s
[INFO]: :-) Your wasm pkg is ready to publish at /workspace/old-op-file/pkg/release/web.
[cargo-make] INFO - Build Done in 5.15 seconds.

there are no errors, so might not be able to see what you see, but the wasm output does show up in the console.
maybe its something in the way you are running cargo-make? because your output seems a bit strange to me. it looks like something is running it and prints its own stuff as a prefix, so maybe its not printing everything. maybe just the stdout and not err?

also you could run with verbose but be aware it dumps a LOT of stuff, but maybe it would give you a lead.

1 reply

woss Feb 8, 2022
Author

oh, I also use gitpod :)

Check the install-deps.sh and see how I am installing the makers. It's much faster than compiling it. ( on the other note, makers freshly installed like that have a long cold-start for some reason. )

Thing is that I build a build-service for the libraries we are using in the Anagolay project and I execute the makers in few ways:

via async exec like this await exec('makers --makefile Makefile.toml fmt', { cwd: localRepoPath, shell: '/bin/bash' });

and via async spawn like this

async function executeMakers(commands: string[], cwd: string, log: Logger): Promise<ISpawnProcessReturn> {
  return await asyncSpawn(
    'makers',
    ['--disable-check-for-updates', ...commands],
    {
      cwd
    },
    log
  );
}

THis is the cold start ( makers was installed via binary and neve used)

Here is the full output with the cold-start and using the code above:

[1644317620920] INFO (publishOperation/12132 on e0a2de2a3d9f): Repo cloned /tmp/anagolay/operation_publish/_anagolay_old-op-file-6cfe30b9260e0585a790d7e4b1224370d9bbdf1e
# cold start
[1644317620920] INFO (publishOperation/12132 on e0a2de2a3d9f): Format the code to see will we get the dirty repository ...
# cold start 
[1644317675063] INFO (git/12132 on e0a2de2a3d9f): gitCloneBare got options
[1644317675064] INFO (git/12132 on e0a2de2a3d9f): Cloning the bare repo
[1644317676795] INFO (ipfs/12132 on e0a2de2a3d9f): Upload to IPFS started ...
[1644317676730] INFO (git/12132 on e0a2de2a3d9f): Reseting to the revision 6cfe30b9260e0585a790d7e4b1224370d9bbdf1e
[1644317676734] INFO (git/12132 on e0a2de2a3d9f): Unpacking ...
[1644317676782] INFO (git/12132 on e0a2de2a3d9f): Done unpacking.
[1644317677939] INFO (ipfs/12132 on e0a2de2a3d9f): Done 🎉

[1644317677947] INFO (publishOperation/12132 on e0a2de2a3d9f): Building the operation ...
[1644317677948] INFO (publishOperation/12132 on e0a2de2a3d9f): Executing: makers --disable-check-for-updates --makefile Makefile.toml build-operation-flow
[1644317677952] INFO (publishOperation/12132 on e0a2de2a3d9f): [cargo-make] INFO - makers 0.35.8

[1644317678624] INFO (publishOperation/12132 on e0a2de2a3d9f): [cargo-make] INFO - Project: op-file
[cargo-make] INFO - Build File: Makefile.toml
[cargo-make] INFO - Task: build-operation-flow
[cargo-make] INFO - Profile: development

[1644317678625] INFO (publishOperation/12132 on e0a2de2a3d9f): [cargo-make] INFO - Running Task: legacy-migration

[1644317678628] INFO (publishOperation/12132 on e0a2de2a3d9f): [cargo-make] INFO - Execute Command: "cargo" "build" "--release" "--all-features"

[1644317678629] INFO (publishOperation/12132 on e0a2de2a3d9f): [cargo-make] INFO - Execute Command: "wasm-pack" "build" "--target" "bundler" "--out-name" "index" "--out-dir" "pkg/release/esm" "--release"

[1644317678630] INFO (publishOperation/12132 on e0a2de2a3d9f): [cargo-make] INFO - Execute Command: "wasm-pack" "build" "--target" "nodejs" "--out-name" "index" "--out-dir" "pkg/release/nodejs" "--release"

[1644317678631] INFO (publishOperation/12132 on e0a2de2a3d9f): [cargo-make] INFO - Execute Command: "wasm-pack" "build" "--target" "web" "--out-name" "index" "--out-dir" "pkg/release/web" "--release"

[1644317678632] INFO (publishOperation/12132 on e0a2de2a3d9f): [cargo-make] INFO - Execute Command: "wasm-pack" "build" "--target" "no-modules" "--out-name" "index" "--out-dir" "pkg/release/no-modules" "--release"

[1644317683367] INFO (publishOperation/12132 on e0a2de2a3d9f): [cargo-make] ERROR - Error while executing command, exit code: 1
[cargo-make] WARN - Build Failed.

caught the error in the job Process exited with code 1
10:55:17 Job <publishOperation> succeeded
[1644317717539] ERROR (publishOperation/12132 on e0a2de2a3d9f): Process exited with code 1

This output above is coming mostly from here

As you can see, we both are running the same thing, and under the same logging level of INFO. Some parts are missing from the stdout.

For example this:

[INFO]: Installing wasm-bindgen...
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on package cache
    Blocking waiting for file lock on package cache

Then I try again ( not a cold start ) the makers ran before and failed:


[1644318247658] INFO (publishOperation/12132 on e0a2de2a3d9f): [cargo-make] INFO - Project: op-file
[cargo-make] INFO - Build File: Makefile.toml
[cargo-make] INFO - Task: build-operation-flow
[cargo-make] INFO - Profile: development

[1644318247658] INFO (publishOperation/12132 on e0a2de2a3d9f): [cargo-make] INFO - Running Task: legacy-migration

[1644318247662] INFO (publishOperation/12132 on e0a2de2a3d9f): [cargo-make] INFO - Execute Command: "cargo" "build" "--release" "--all-features"

[1644318247664] INFO (publishOperation/12132 on e0a2de2a3d9f): [cargo-make] INFO - Execute Command: "wasm-pack" "build" "--target" "bundler" "--out-name" "index" "--out-dir" "pkg/release/esm" "--release"

[1644318247665] INFO (publishOperation/12132 on e0a2de2a3d9f): [cargo-make] INFO - Execute Command: "wasm-pack" "build" "--target" "nodejs" "--out-name" "index" "--out-dir" "pkg/release/nodejs" "--release"

[1644318247666] INFO (publishOperation/12132 on e0a2de2a3d9f): [cargo-make] INFO - Execute Command: "wasm-pack" "build" "--target" "web" "--out-name" "index" "--out-dir" "pkg/release/web" "--release"

[1644318247667] INFO (publishOperation/12132 on e0a2de2a3d9f): [cargo-make] INFO - Execute Command: "wasm-pack" "build" "--target" "no-modules" "--out-name" "index" "--out-dir" "pkg/release/no-modules" "--release"

[1644318273933] INFO (publishOperation/12132 on e0a2de2a3d9f): [cargo-make] INFO - Build Done in 26.98 seconds.

now it succeeds. And it's like this every time. Also, you can see that the output is not passed as well. I wonder what can be the issue?

sagiegurari · 2022-02-08T14:46:41Z

sagiegurari
Feb 8, 2022
Maintainer

your js code only prints the stdout, but not the stderr. some sub processes will print to stderr. thats why you are missing output.
why things work/don't work every now and than is probably related to your code/build. its possible some things are not cleaned up or something. i ran the command multiple times and it worked each time.
if you really want to understand the issue, try to reduce layers. try to call cargo make (or makers) directly first. see that you can see the output as you want and that it runs multiple times ok. than add the js on top (which based on item 1 we already know is a bit lacking).

3 replies

woss Feb 8, 2022
Author

oh, I think i misunderstood the .on('error and .stderr. that they should return the same thing.

[1644332801899] INFO (publishOperation/12522 on e0a2de2a3d9f): [cargo-make] INFO - Execute Command: "wasm-pack" "build" "--target" "no-modules" "--out-name" "index" "--out-dir" "pkg/release/no-modules" "--release"

[1644332802238] ERROR (publishOperation/12522 on e0a2de2a3d9f): stderr:     Blocking waiting for file lock on package cache

[1644332802246] ERROR (publishOperation/12522 on e0a2de2a3d9f): stderr:     Blocking waiting for file lock on package cache

[1644332802258] ERROR (publishOperation/12522 on e0a2de2a3d9f): stderr:     Blocking waiting for file lock on package cache

[1644332802355] ERROR (publishOperation/12522 on e0a2de2a3d9f): stderr: [INFO]: Checking for the Wasm target...

[1644332802362] ERROR (publishOperation/12522 on e0a2de2a3d9f): stderr:    Compiling proc-macro2 v1.0.36

[1644332802362] ERROR (publishOperation/12522 on e0a2de2a3d9f): stderr:    Compiling unicode-xid v0.2.2
   Compiling syn v1.0.86
   Compiling log v0.4.14

why this ends up in the stderr?? it shouldn't be there

sagiegurari Feb 8, 2022
Maintainer

ya, but whoever wrote that executable decided INFO should be in the err :)
no idea why, but its out of my control.

woss Feb 8, 2022
Author

ha! that's some future engineering :)

Thanks for your time and effort!

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

how to see the compile logs when executing from the spwaned process? #628

{{title}}

Replies: 3 comments 5 replies

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

{{title}}

{{title}}

Select a reply

how to see the compile logs when executing from the spwaned process? #628

woss Feb 7, 2022

Replies: 3 comments · 5 replies

sagiegurari Feb 7, 2022 Maintainer

woss Feb 7, 2022 Author

sagiegurari Feb 8, 2022 Maintainer

woss Feb 8, 2022 Author

sagiegurari Feb 8, 2022 Maintainer

woss Feb 8, 2022 Author

sagiegurari Feb 8, 2022 Maintainer

woss Feb 8, 2022 Author

woss
Feb 7, 2022

Replies: 3 comments 5 replies

sagiegurari
Feb 7, 2022
Maintainer

woss Feb 7, 2022
Author

sagiegurari
Feb 8, 2022
Maintainer

woss Feb 8, 2022
Author

sagiegurari
Feb 8, 2022
Maintainer

woss Feb 8, 2022
Author

sagiegurari Feb 8, 2022
Maintainer

woss Feb 8, 2022
Author