rust-analyzer: not found error, while cargo check & build works fine

I’m having the same issue, rust analyzer breaks when using an esp-idf project

2024-02-15T21:41:26.933826Z ERROR rust_analyzer::main_loop: FetchBuildDataError:
error[E0531]: cannot find unit struct, unit variant or constant `SIGABRT` in crate `libc`
   --> /home/[...]/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/test/src/test_result.rs:102:24
    |
102 |             Some(libc::SIGABRT) => TestResult::TrFailed,
    |                        ^^^^^^^ not found in `libc`


error: aborting due to 1 previous error


For more information about this error, try `rustc --explain E0531`.

error: could not compile `test` (lib) due to 2 previous errors

@mrchantey I confirmed it: rust-analyzer works perfectly in esp-idf projects if you use rustc 1.77.0-nightly (2a3e63551 2023-12-30). The issue is rustc 1.78.0-nightly (ee9c7c940 2024-02-14).

Yes same got the error on an esp-idf project after updating rust nightly to

rustc 1.78.0-nightly (ee9c7c940 2024-02-14)

Same problem here, temporarily I’m commenting out that offending line and it works:

None => match status.signal() {
    // Some(libc::SIGABRT) => TestResult::TrFailed,
    Some(signal) => {
        TestResult::TrFailedMsg(format!("child process exited with signal {signal}"))
    }
    None => unreachable!("status.code() returned None but status.signal() was None"),
},

seems plausible cause the line was added here, if I’m correct https://github.com/rust-lang/rust/commit/f622e832d41171578b6987d0b25b3a84d6d1c81c#diff-c91a894be23c4fb9ac51642c91c20500cdd48f7f0114b4b3c6a8a1cb47afa674

When I set the option cargo.allTargets to false, this makes it work without patching the source. Indeed, passing --all-targets implies --tests.

Doing this in my neovim+lazy.nvim setup works (for example) like this:

{
  "mrcjkb/rustaceanvim",
  opts = function(_, opts)
    opts.server.default_settings["rust-analyzer"].cargo.allTargets = false
  end,
}

But note that this is only a workaround.

Enabling that setting does not resolve the issue.

Try setting "rust-analyzer.cargo.allTargets": false, (needs latest nightly r-a, from 01.04.2024) if you are working on a no-std target. If you still run into that with that setting we’ll need more info.

I have similar problem on amd64

@mrchantey Which rust nightly version doesn’t have this error?

Pretty sure I was on the previous version 1.77.0-nightly