"Failed to connect" errors

[johnousterhout]

Describe the bug
When I run bear it generates an infinite stream of messages like the following:

I0320 12:55:00.580703774 878247 subchannel.cc:1033] Connect failed: {"created":"@1742496900.580635111","description":"Failed to connect to remote host: Connection refused","errno":111,"file":"src/core/lib/iomgr/tcp_client_posix.cc","file_line":199,"os_error":"Connection refused","syscall":"connect","target_address":"ipv6:[::1]:37385"}
I0320 12:55:00.581049948 878247 subchannel.cc:1085] New connected subchannel at 0x555832c4e960 for subchannel 0x555832c4c290

To Reproduce
Invoke 'bear -- make LLVM=1' on the Homa kernel module.

Strangely, if I invoke bear with --verbose it succeeds but produces an

Expected behavior
I had hoped it would create file compile_commands.json.

Strangely, if I invoke 'bear --verbose -- make LLVM=1' it succeeds but produces an empty compile_commands.json file.

Environment:

• OS name: Linus
• OS version: Ubuntu 22
• OS architecture: x86_64
• Bear version: 3.0.18
• Bear install method: sudo apt-get install bear

Additional context

• Can you give us a reference to the project that you are running against this tool? https://github.com/PlatformLab/HomaModule
• What build tools this project is using? GNU make with no configure script (it's a Linux kernel module)
• Could you attach build logs? I'm attaching a log from the --verbose run, which succeeded but produced an empty ompile_commands.json file

Before you send...

• Have you read the README.md file or man bear? yes
• Have you looked what other open issues Bear has? yes
• Are you sure that the build works without Bear? yes

bear.txt

[rizsotto]

Thanks @johnousterhout for the report.

This is probably one of the gRPC issues. Can't reproduce it. The CI builds running against latest Ubuntu and passes.