Skip to content

Mention CI for java 8 and windows #15466

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

Merged
merged 1 commit into from
Jun 21, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions docs/_docs/contributing/testing.md
Original file line number Diff line number Diff line change
Expand Up @@ -173,6 +173,32 @@ original expect file, or if the user wants to globally replace all expect files
`scala3-compiler-bootstrapped/test:runMain dotty.tools.dotc.semanticdb.updateExpect`, and compare the changes via version
control.

### Test regimes

Continuous integration, managed by GitHub Actions, does not run all jobs when a pull request is created.
In particular, test jobs for testing under JDK 8 and Windows are not run. Those jobs are run only for the nightly build.

If a PR may fail differentially under either JDK 8 or Windows, the test jobs may be triggered by adding
a special command to the PR comment text:

```
[test_java8]
[test_windows_full]
```
Furthermore, CI tests are bootstrapped. A job to also run tests non-bootstrapped may be triggered manually:
```
[test_non_bootstrapped]
```
A trivial PR, such as a fix for a typo in a comment or when contributing other documentation, may benefit by skipping CI tests altogether:
```
[skip ci]
```
Other jobs which are normally run can also be selectively skipped:
```
[skip community_build]
[skip test_windows_fast]
```

## Troubleshooting

Some of the tests depend on temporary state stored in the `out` directory. In rare cases, that directory
Expand Down