make travis not waste its own and everyone’s time

[flying-sheep]

because failing after making that poor machine do all that stuff isn’t nice

[japaric]

As you may have notice all the test scripts run, even if some of them fail, so running the check-line.sh first doesn't change the outcome.

[flying-sheep]

didn’t notice that. is there a way to suppress that?

[japaric]

we could chain the commands with &&, but ... if you put the line-check first and it fails, the test ends and you won't see if cargo build/test passed because they didn't run.

[flying-sheep]

well, since the line check obviously is in place to prevent inadequately-styled code to be pulled, this is what you want, isn’t it?

if it isn’t, putting it first at least allows people to immediately see that checks fail, before even the build starts