Skip to content

Compiletest panics on custom lldb version #84131

Closed
@Manishearth

Description

@Manishearth

My system has a custom version of lldb on it, and the lldb version string does not match the expected format. I'm not sure if I can share the exact version string but the first line is somehting like lldb version foo5-bar (revision somehash)

Check compiletest suite=ui mode=ui (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-gnu)
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ParseIntError { kind: Empty }', src/tools/compiletest/src/main.rs:978:56
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

I feel like I should be able to run the uitests without needing the precise lldb version. I tried to override this by passing --lldb-version to ./x.py but it doesn't seem to accept that parameter.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions