Rework in-docker tests so they handle comments in scripts

[kgugala]

fixes #65

[mithro]

@kgugala - I'm okay with this temporary fix, however the tuttest tool should understand how comments work?

[mgielda]

Well, the original idea for tuttest was not to be language specific and not really provide some of the functionality that you had since requested (which are bash-specific). It's the --single-command option which introduced the bug, but to fix it properly we'd need to make tuttest understand comments in various languages. Bash as such is of course easy to fix, so I think we'll just make this fix in single-command since it's kinda bash-specific anyhow.

[mithro]

@mgielda -- Well, shouldn't bash understand that # is a comment and just execute nothing?

[mithro]

I have forgotten why we needed --single-command? I wonder if --single-command should actually be generating a script file which it then executes?

[pgielda]

I actually think this is not acceptable to merge and we have to fix the underlying issue.

[pgielda]

@kgugala can you apply the approach #68 here instead?

[kgugala]

@kgugala can you apply the approach #68 here instead?

done

[pgielda]

Ok, now we have a real CI feedback. It seems we have two problems:

1. on old OSes seems that LiteX fails
2. we hit 50min timeout of Travis

I would suggest merging this and open separate issue for (1) -- probably in LiteX using ubuntu:trusty fail as an example.
As for (2) I would suggest temporarily not test the longest test in tuttest (LiteX? Linux/LiteX?). Long term we would have to migrate from Travis, but I know its not trivial because of storage limitations of Github Actions and we need a short term solution.