enable travis

[NobbZ]

This PR aims to enable travis for the track and has the following subgoals:

• install a local trackler and x-api
• install a local client
• check if config is valid
• fetch every single exercise from local X-API
• solve every single exercise by copying example-file over stub-file and run the tests
• collect status of tests and have a proper exit code at the end

FIXES #3

[yurrriq]

Any interest in using Nix (language: nix and nix-build)?

[NobbZ]

I have no experience in using nix. Would it speed up installation of idris drastically? If not I do not see much improvement compared to the current cacheing solution. Eric Bailey <notifications@github.com> schrieb am Sa., 10. Juni 2017, 03:46:

…

Any interest in using Nix (language: nix and nix-build)? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#22 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADmR4nJ_tCz6yDiZptYTWVgx1bxKZgGks5sCfV6gaJpZM4N1-Mz> .

[yurrriq]

It would probably slow it down tbh. I'm just a Nix fanboy, basically. I'm totally cool with a Stack-based solution. Thanks for doing this!

[NobbZ]

Hehe, fanboy-ism ;)

Problem there is, that we will hit a massive wall with everything that eats our precious time. With a cold cache there is already half an hour taken away by compiling idris, also we know that idris isn't very fast when it comes to compiling idris programs.

I really wan't to avoid failing builds because of hitting the 90 minute limit.

[yurrriq]

Ah, so if we're a little clever, we can hit a Hydra binary cache with Nix too. FWIW the Idris infrastructure is a little broken atm, though that would affect us here.

[NobbZ]

Okay, its done!

Collecting the exit-code does work, but currently it only shows us when compilation failed, not failed tests. Since the testsuite still exits with 0 on fail.

So to have this work properly we will need to tinker around with the test suite, which I will tackle in a separate PR. Perhaps I will simply switch to idris-testing while doing this.

[yurrriq]

Nice! Yeah, you can use idris-testing's Reporting namespace (can't remember which module just now) and check for any not or similar and use the exit functions from System.

[yurrriq]

Thanks. I've never resolved conflicts in the GitHub UI before. I won't be doing that again :)