Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Launching the testsuite generation produces no test #54

Open
P-E-P opened this issue Oct 3, 2023 · 2 comments · May be fixed by #56
Open

Launching the testsuite generation produces no test #54

P-E-P opened this issue Oct 3, 2023 · 2 comments · May be fixed by #56

Comments

@P-E-P
Copy link
Member

P-E-P commented Oct 3, 2023

Launching the testsuite using the readme instructions produces no test, the resulting testsuite.yml has the following content:

tests:
@tamaroning
Copy link
Contributor

tamaroning commented Nov 4, 2023

I encountered the same issue

tamaron@PC:~/work/testing$ cargo run -- --gccrs '../gccrs-build/gcc
/crab1' --rustc rustc --gccrs-path ../gccrs/ --rust-path ../rust/ -
-output-dir sources/ --yaml testsuite.yml --pass gccrs-parsing
    Finished dev [unoptimized + debuginfo] target(s) in 0.02s
     Running `target/debug/testsuite-adaptor --gccrs ../gccrs-build/gcc/crab1 --rustc rustc --gccrs-path ../gccrs/ --rust-path ../rust/ --output-dir sources/ --yaml testsuite.yml --pass gccrs-parsing`
[info] running pass `gccrs-parsing`...
[info] fetching test files for `gccrs-parsing`...
[info] generating test cases for `gccrs-parsing`... this might take a while
[info] `gccrs-parsing` pass complete!
tamaron@PC:~/work/testing$ cat testsuite.yml 
tests:
tamaron@PC:~/work/testing$

rustc 1.74.0-nightly (20999de3a 2023-09-15)

@tamaroning
Copy link
Contributor

rust/src/test has been moved to rust/tests
rust-lang/rust@cf2dff2

@tamaroning tamaroning linked a pull request Nov 4, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants