Setup testing over all of tptp/smtlib libraries

[Gbury]

Still not clear on how an automated setup could work, the libs are definitely too big for the free CI on github.

[bobot]

In which sense are they too big? Are they too long to download or to typecheck with dolmen binary?

[c-cube]

I imagine they're too big to download and store on a normal CI machine, and if caching is done wrong it'd be a strain on smtlib/tptp infrastructure?

[Gbury]

Both: I doubt the free travis CI machines wouldn't fare very well trying to:

• download a few Go (the whole smtlib/tptp libraries) for each run, typically free CI infrastructures specify a reasonable maximum cache size of a few hundreds MB.
• run the generated dolmen binary on all these problems; considering each run is limited to about 30min / 1h of real time (iirc), setting up testing would probably require to split the runs into separate jobs.

All in all, even if it might be possible I think it would be an abuse of free CI in this situation. Instead I'll leave in the repo and check with CI the following:

• tests that try and test most syntax constructions in a few files
• tests for each error message
• tests for each reported bug

For testing on the whole smtlib, I'll first do it manually on my personal machines, and in the long term I might try and see if the new alt-ergo benchmarking machine can be used (either to test dolmen directly, or indirectly since it should be integrated into alt-ergo soon-ish).