Continuous integration for "compilable check" #37
Comments
I am also in favor of using TravisCI for this. I don't think makefiles are necessary, we can just run the existing script (maybe with some tweaks). |
@PhilippWendler Well I went ahead and made a Makefile build system anyway because it's more convenient to use and extend IMHO. |
@dan Could you please add a .travis.yml? I have added the repository on the TravisCI site and the web hook is there, too. |
@delcypher @PhilippWendler I added both of you as Collaborator such that you are able to help me set up TravisCI. Thanks! |
@dbeyer I will do but I'm still checking that things compile under GCC and Clang. I'm concerned that TravisCI won't actually be suitable here because of the huge number of benchmarks leading to large compile times. |
@delcypher I think it should be possible somehow to check only files that were changed by commit or pull request when we execute the check on Travis. So if the full check is too costly, we could try to do this. |
This is now done. We finally had a passing build as of eea2e11 |
@dbeyer @tautschnig
I was looking other some stuff in the repository and I notice you seem to be having some problems with benchmarks that don't compile properly with warnings enabled. I have a suggestion to try to prevent this from getting any worse.
I'm currently trying to see if I can get KLEE to symbolically execute some of the benchmarks some I going to be doing step 1 anyway and I have lots of experience using TravisCI so I'm happy to set that up as well if it is desired.
The text was updated successfully, but these errors were encountered: