News for hackers. Stuff that matters.

A comment on Testing LLVM. Parent comment

Re:Testing LLVM by ezanmoto on Friday January 13, 2017 @04:40PM (#13394945)
Do you know of solutions that exist for pre-commit checks for GitHub at the moment?
[ Parent | on HN ]
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.
[ Parent | on HN ]
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.

[ Parent | on HN ]
Re:Testing LLVM by Joky on Friday January 13, 2017 @10:37PM (#13396711)
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

[ Parent | on HN ]
Re:Testing LLVM by wyldfire on Friday January 13, 2017 @05:22PM (#13395295)
In general? Yes, Travis CI seems to be a very popular one. Many folks use Appveyor for Windows support AFAICT.
[ Parent | on HN ]