Re: [OE-core] [RFC 1/5] valgrind: make ptest depend on all components

[Yash Shinde <Yash.Shinde@windriver.com>]

On 20-11-2023 21:57, Alex Kiernan wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> I've finally got this running in a way I can usefully inspect and try
> things and it's beginning to feel like we've headed into something
> which simply isn't supported.
>
> The failure is this:
>
>    thread 'main' panicked at src/tools/compiletest/src/common.rs:519:30:
>    no entry found for key
>
> Which is empty because the mapping list is collected by running rustc
> with -Z unstable-options --print=all-target-specs-json, but that fails
> because we're not running a nightly compiler:
>
>    error: the option `Z` is only accepted on the nightly compiler
>    help: consider switching to a nightly toolchain: `rustup default nightly`
>    note: selecting a toolchain with `+toolchain` arguments require a
> rustup proxy; see
> <https://rust-lang.github.io/rustup/concepts/index.html>
>    note: for more information about Rust's stability policy, see
> <https://doc.rust-lang.org/book/appendix-07-nightly-rust.html#unstable-features>
>
> Basically feels like running the test suite is only supported on the
> nightlies...
I saw the same error earlier.

Investigating further, we understood that the issue is not related to 
running on nightly channel. The '-Z unstable options' were also present 
in earlier rust versions and removing of the newly added -Z options 
after 1.70 also didn't solve the problem.

On doing further analysis, we found that the custom target config/specs 
were not fetched during the rust build.

The log for reference is as follows:

Building stage1 library artifacts (x86_64-unknown-linux-gnu -> 
x86_64-poky-linux-gnu)
error: failed to run `rustc` to learn about target-specific information

Caused by:
   process didn't exit successfully: ` 
build-st/tmp/work/core2-64-poky-linux/rust/1.72.0/rustc-1.72.0-src/build/bootstrap/debug/rustc 
- --crate-name ___ --print=file-names -Csymbol-mangling-version=legacy 
-Zunstable-options -Zunstable-options '--check-cfg=values(bootstrap)' 
'--check-cfg=values(stdarch_intel_sde)' 
'--check-cfg=values(no_fp_fmt_parse)' 
'--check-cfg=values(no_global_oom_handling)' '--check-cfg=values(no_rc)' 
'--check-cfg=values(no_sync)' '--check-cfg=values(freebsd12)' 
'--check-cfg=values(freebsd13)' 
'--check-cfg=values(backtrace_in_libstd)' 
'--check-cfg=values(target_env,"libnx")' 
'--check-cfg=values(target_arch,"asmjs","spirv","nvptx","xtensa")' 
-Zmacro-backtrace -Clink-args=-Wl,-z,origin 
'-Clink-args=-Wl,-rpath,$ORIGIN/../lib' -Csplit-debuginfo=off 
-Cprefer-dynamic -Zinline-mir -Cembed-bitcode=yes 
'-Zcrate-attr=doc(html_root_url="https://doc.rust-lang.org/1.72.0/")' 
--target x86_64-poky-linux-gnu --crate-type bin --crate-type rlib 
--crate-type dylib --crate-type cdylib --crate-type staticlib 
--crate-type proc-macro --print=sysroot --print=split-debuginfo 
--print=crate-name --print=cfg` (exit status: 1)
   --- stderr
   error: Error loading target specification: Could not find 
specification for target "x86_64-poky-linux-gnu". Run `rustc --print 
target-list` for a list of built-in targets

Build completed unsuccessfully in 0:04:38

Regards,
Yash.

> This is the full piece of useful logs for reference:
>
> Testing stage1 compiletest suite=run-coverage mode=run-coverage
> (aarch64-unknown-linux-gnu -> aarch64-poky-linux-gnu)
> thread 'main' panicked at src/tools/compiletest/src/common.rs:519:30:
> no entry found for key
> note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
> Note that not all variants of mir-opt tests are going to be blessed,
> as no mapping between
> a 32bit and a 64bit target was found for aarch64-poky-linux-gnu.
> You can add that mapping by changing MIR_OPT_BLESS_TARGET_MAPPING in
> src/bootstrap/test.rs
> Testing stage1 compiletest suite=mir-opt mode=mir-opt
> (aarch64-unknown-linux-gnu -> aarch64-poky-linux-gnu)
> thread 'main' panicked at src/tools/compiletest/src/common.rs:519:30:
> no entry found for key
> note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
> error: the option `Z` is only accepted on the nightly compiler
>
> help: consider switching to a nightly toolchain: `rustup default nightly`
>
> note: selecting a toolchain with `+toolchain` arguments require a
> rustup proxy; see
> <https://rust-lang.github.io/rustup/concepts/index.html>
>
> note: for more information about Rust's stability policy, see
> <https://doc.rust-lang.org/book/appendix-07-nightly-rust.html#unstable-features>
>
> error: 1 nightly option were parsed
>
> thread 'main' panicked at synthetic_targets.rs:66:9:
> failed to gather the target spec for aarch64-poky-linux-gnu
> note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
>
> --
> Alex Kiernan