ci: spurious output / errors in IWYU job #35361

issue fanquake opened this issue on May 22, 2026

fanquake commented at 2:15 PM on May 22, 2026: member

https://github.com/bitcoin/bitcoin/actions/runs/26292243180/job/77395542650: Looks like IWYU is trying to run on libmultiprocess related code, and failing, but we shouldn't be trying to lint a subtree in the first place:

 /home/admin/actions-runner/_work/_temp/src/ipc/libmultiprocess/test/mp/test/test.cpp:5:10: fatal error: 'mp/test/foo.capnp.h' file not found
    5 | #include <mp/test/foo.capnp.h>
      |          ^~~~~~~~~~~~~~~~~~~~~

Along with other sporadic error output:

[1](https://github.com/bitcoin/bitcoin/actions/runs/26292243180/job/77395542650#step:11:11661)
error: no such file or directory: '/home/admin/actions-runner/_work/_temp/build/src/ipc/capnp/common.capnp.c++'
error: no input files
error: unable to handle compilation, expected exactly one compiler job in ''
error: no such file or directory: '/home/admin/actions-runner/_work/_temp/build/src/ipc/capnp/common.capnp.proxy-client.c++'
error: no input files
error: unable to handle compilation, expected exactly one compiler job in ''
error: no such file or directory: '/home/admin/actions-runner/_work/_temp/build/src/ipc/capnp/common.capnp.proxy-server.c++'
error: no input files
error: unable to handle compilation, expected exactly one compiler job in ''
error: no such file or directory: '/home/admin/actions-runner/_work/_temp/build/src/ipc/capnp/common.capnp.proxy-types.c++'
error: no input files

Ideally we'd have no sporadic errors / output, and wouldn't be trying to run linters/tools over subtrees at all.

I think that any errors in CI output/tooling should also be getting turned into real errors, so that they aren't missed/ignored?

fanquake commented at 2:15 PM on May 22, 2026: member

cc @hebasto @ryanofsky
ryanofsky commented at 11:22 AM on May 28, 2026: contributor

https://github.com/bitcoin/bitcoin/actions/runs/26292243180/job/77395542650 seems to point to a successful CI run, so wondering if something might have fixed this, or if it succeeded because the errors are sporadic.

It's also not clear to me why these errors would be sporadic, unless maybe they happen due to build jobs running in parallel and a dependency not being specified. Would be curious for an update.
maflcko commented at 11:44 AM on May 28, 2026: member

I think the link should have been https://github.com/bitcoin/bitcoin/actions/runs/26292243180/job/77395542650#step:11:7602 or https://github.com/bitcoin/bitcoin/actions/runs/26292243180/job/77395542650#step:11:11354 (with the line number in it)? (grep for fatal error)
maflcko added the label Tests on May 28, 2026
hebasto commented at 9:23 PM on May 29, 2026: member

Related: https://github.com/bitcoin-core/libmultiprocess/issues/284.

Contributors

Labels

Linked (view graph)

#28722 Multiprocess tracking issue #35401 build: exclude libmultiprocess test target from compile commands #35418 build: exclude mptest target from compile commands