Skip to content

Create runnable test folder #281

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.

Sign up for GitHub

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

Jump to bottom
Closed
philberty opened this issue Mar 14, 2021 · 1 comment
Closed

Create runnable test folder #281

philberty opened this issue Mar 14, 2021 · 1 comment
Labels
automation enhancement GCC good-first-pr

Comments

@philberty
Copy link
Member

Dejagnu has support for runnable tests which will actually link and executable and run it.
@dkm
Copy link
Member

dkm commented Mar 15, 2021

I guess I can come up with something if the next few days

@tschwinge tschwinge mentioned this issue Mar 17, 2021
Open
dkm added a commit to dkm/gccrs that referenced this issue Mar 23, 2021
@dkm
Refactor DejaGNU testsuite
ac22a0f 
Use more standard layout for DejaGNU testsuite.

3 subdirectories are used for tests:
- compile/*: tests are build using default torture options.
- xfail_compile/*: tests are expected to fail early in the frontend and are only
build once.
- execute/*: tests are executed and exit status is checked.

The previous .exp files were copied from D tests and were expected to be used in
a different way not really applicable for the current Rust tests.

Fixes Rust-GCC#281
dkm added a commit to dkm/gccrs that referenced this issue Mar 23, 2021
@dkm
Refactor DejaGNU testsuite
26cbc3c 
Use more standard layout for DejaGNU testsuite.

3 subdirectories are used for tests:
- compile/*: tests are build using default torture options.
- xfail_compile/*: tests are expected to fail early in the frontend and are only
build once.
- execute/*: tests are executed and exit status is checked.

The previous .exp files were copied from D tests and were expected to be used in
a different way not really applicable for the current Rust tests.

Fixes Rust-GCC#281
dkm added a commit to dkm/gccrs that referenced this issue Mar 23, 2021
@dkm
Refactor DejaGNU testsuite
af026f9 
Use more standard layout for DejaGNU testsuite.

3 subdirectories are used for tests:
- compile/*: tests are build using default torture options.
- xfail_compile/*: tests are expected to fail early in the frontend and are only
build once.
- execute/*: tests are executed and exit status is checked.

The previous .exp files were copied from D tests and were expected to be used in
a different way not really applicable for the current Rust tests.

Fixes Rust-GCC#281
dkm added a commit to dkm/gccrs that referenced this issue Mar 24, 2021
@dkm
Refactor DejaGNU testsuite
464fe5a 
Use more standard layout for DejaGNU testsuite.

3 subdirectories are used for tests:
- compile/*: tests are build using default torture options.
- xfail_compile/*: tests are expected to fail early in the frontend and are only
build once.
- execute/*: tests are executed and exit status is checked.

The previous .exp files were copied from D tests and were expected to be used in
a different way not really applicable for the current Rust tests.

Fixes Rust-GCC#281
dkm added a commit to dkm/gccrs that referenced this issue Mar 26, 2021
@dkm
Refactor DejaGNU testsuite
f18fe67 
Use more standard layout for DejaGNU testsuite.

3 subdirectories are used for tests:
- compile/*: tests are build using default torture options.
- xfail_compile/*: tests are expected to fail early in the frontend and are only
build once.
- execute/*: tests are executed and exit status is checked.

The previous .exp files were copied from D tests and were expected to be used in
a different way not really applicable for the current Rust tests.

Fixes Rust-GCC#281
tschwinge added a commit that referenced this issue Apr 10, 2021
@tschwinge
[testsuite] Append to 'additional_prunes' [#281, #301]
548b8ee 
... to not overwrite what might already have been added elsewhere.
tschwinge added a commit that referenced this issue Apr 10, 2021
@tschwinge
[testsuite] In 'additional_prunes' look for explicit 'error: ' instea…
db28126 
…d of 'error' [#281, #301]

... so that if the filename contains 'error', this doesn't anymore trigger for
the current 'Attempting to parse file: [...]' diagnostic.
tschwinge added a commit that referenced this issue Apr 12, 2021
@tschwinge
[testsuite] Append to 'additional_prunes' [#281, #301]
ec12749 
... to not overwrite what might already have been added elsewhere.
tschwinge added a commit that referenced this issue Apr 12, 2021
@tschwinge
[testsuite] In 'additional_prunes' look for explicit 'error: ' instea…
be88283 
…d of 'error' [#281, #301]

... so that if the filename contains 'error', this doesn't anymore trigger for
the current 'Attempting to parse file: [...]' diagnostic.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
automation enhancement GCC good-first-pr
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@philberty @dkm