Re:Testing LLVM
by wyldfire on Friday January 13, 2017 @04:19PM
(#13394793)
I get the feeling that there's parts of the community that feel the same way. I'm hoping that the planned move to github will naturally cascade into pre-commit checks.
[ Parent
| on HN ]
A big big problem is having enough hardware to have a CI throughput one or two order of magnitude what it is now. Unfortunately that's not an easy thing considering how "heavy" it is to build and test the full toolchain.
Do you know of solutions that exist for pre-commit checks for GitHub at the moment?
Re:Testing LLVM
by dikaiosune on Friday January 13, 2017 @05:26PM
(#13395326)
Rust uses https://github.com/rust-community/bors which maintains a linear queue of PRs which can only land after being rebased onto the commits before the PR and subsequently passing tests.
Re:Testing LLVM
by WalterBright on Saturday January 14, 2017 @12:03AM
(#13396990)
dlang uses several. One notable one is the "autotester" written by Brad Roberts. It's built to ensure that breaking the D compiler (as tested by the test suite) does not result in commits.
It's incredibly useful.
Swift also has a lot of pre-commit CI:
- here is the Jenkins bots page: https://ci.swift.org/view/Pull%20Request/ - example of PR test reporting: https://github.com/apple/swift/pull/6802