Closed 9names closed 3 years ago
I ran this CI against my fork. If you want to verify what a pass looks like: https://github.com/9names/bl602-pac/pull/1/checks
Might be a good idea to also run SVDConv to check that the SVD is semantically correct. Running it with only the SVD file name will check the file for errors (return code 2), warnings (return code 1) or nothing (return code 0).
It also supports the (undocumented in --help
) option --strict
which turns some warnings into errors and adds 22 more warnings.
The return code would have to be ignored until the existing warnings/errors have been fixed.
This might also be better done at the new SVD repo at Pine64.
Manually checking that SVD changes don't break PAC svd2rust generation is painful. Automate it using Github Actions so we can run against several Rust versions and have some confidence that PRs are sane