Integration Tests unified over all repositories
In particular, tests:
- sPyNNaker
- SpiNNaker Graph Front End
- sPyNNaker New Model Template
- PyNN Examples
- Introductory Lab Scripts
- Cortical microcircuit
- SpiNNGym
- Markov Chain Monte Carlo
- SpiNNaker_PDP2
- Visualiser
- Whole Machine Tests (overnight only)
The SpiNNaker software stack uses branch name matching to coordinate between repositories. To trigger an integration test for a branch, simply create a branch in this repository with same name, and a PR (can be Draft) for that branch. Typically such branches just use a trivial whitespace edit of this file and are tagged jenkins trigger so that the team knows not to merge them in this repo. You're strongly encouraged to link to the PRs for the other branches in your branch here (or at least to the lead PR). Once the tests pass, we generally close the PR in this repo and delete the branch without merging it.
This method of working means that this repo seems to have a strange commit pattern.