Commit graph

8 commits

Author SHA1 Message Date
Matt Corallo
0ab7f90578 Use Debian experimental in CI to match LLVM between rustc and clang 2020-09-10 22:03:32 -04:00
Matt Corallo
9f0fa04f62 Add CI run for bindings generation (though we'll allow it to fail) 2020-09-10 22:03:32 -04:00
Valentine Wallace
0ac5697bb8
Bump MSRV to 1.30.0
We wanted to bump to 1.29 to continue to support mrustc bootstrapping, but on 1.29
there's a bug preventing us from compiling the lightning package only, thus parts
of lightning-net-tokio cause a compilation error.

The advantage of bumping the MSRV is an improved borrow checker which should
enable improved code quality, and not having jump through weird hoops sometimes
to get 1.22 working.
2020-08-19 15:39:03 -04:00
Matt Corallo
7b0483eba8 Set codecov upload token
Docs seem to indicate this should only be required for private
repos, but we have builds failing claiming this needs to be
specified, so just set it manually.
2020-08-03 17:09:27 -04:00
Matt Corallo
21a90245e4 Fix step naming in fuzz tests in GitHub Actions 2020-04-24 16:55:09 -04:00
Matt Corallo
de1e58e1cb Run Github Actions on PRs, too 2020-04-24 16:55:09 -04:00
Franck Royer
06419a2608
Add a pop of colour 2020-04-24 15:06:15 +10:00
Franck Royer
355dbbcde9
Add CI using GitHub Action
Same setup than Travis except for removing
`rm -f target/debug/lightning-*` as I do not believe
such file would exist on a fresh run.

I have not setup caching at this stage. The library is
small so I don't think it'd be that necessary/helpful.

I'd recommend to let both CI run for a bit to compare
performance and stability. The CI setup is straightforward
so I do not foresee any issue with GitHub actions.

Once happy, Travis file can be removed and branch
protection checks can be updated to block on the GitHub
actions.

You can also check the [Coverage report](752a58bc04/lightning/src/chain) to ensure it is as expected.
2020-04-24 14:49:22 +10:00