|Re: [hatari-devel] Recent Hatari change problems|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] Recent Hatari change problems
- From: Thomas Huth <th.huth@xxxxxxxxx>
- Date: Mon, 30 Apr 2018 08:59:42 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.de; s=2017; t=1525071593; bh=+CcP3PywfPK27N43iHjSpAYJjQ4QMv567PnHA4BvoHA=; h=Date:From:To:Subject:From; b=L5k5UfyuXMxsyhm1fGkT7ZwcW8nHl5AWGm9qEG6RNGb/VixypUppIReW5pb6bZ80l KJwfYE2pTlsB2CbARzpLR3I5DtVvT8sfwE45nFwUiXy4xCDs7roQScUqyyOg2/4h48 YIEr08CzdXdYiC/8nZNfC+zTwyPcLsu9wGIzGzpoxBbppJGkDVLsaY/SbwJx/2lrFp YahiZ5LcFiiFuf1J3iA6tz2Z+L8f3zsDYQ9HEtkmc3ZPhHatjFKxBSpxMwO7TTS/xr sYxLxQIoF+oKNfq5JvyVld3v0UfGUXSaFH4mhjuLrw/dBKREbxiMdQfgdg6y+UqWsD jmqgHLExjz5Ug==
Am Sun, 29 Apr 2018 20:16:28 +0300
schrieb Eero Tamminen <oak@xxxxxxxxxxxxxx>:
> >> As all the shell files are now fine, I think best would be
> >> to have *one* test (script) that checks all shell scripts
> > Yes, makes sense. I was also not very happy about having to
> > encode the file name as test name, so I've put the stuff now
> > into a separate script as you suggested.
> It's a bit slow, compared to other tests.
Oh, c'mon, it's just 2 seconds. Sure, it's slower than the other tests,
but this test certainly does not run forever.
> Does CTest support multiple test targets, so that one could
> split tests e.g. to sets that are run before release (all),
> and things that should be run before commits?
Not that I'm aware of. Looks like you can run tests based on applying a
regex on the test name, but apart from that I haven't seen such a
> IMHO checkbashism is more of a release check than commit check.
The point of having regression tests is that you check it regularly,
not just right before a release. Otherwise, you could also say that
e.g. XBIOS interception hardly changes, so it should also be tested
right before the release only etc.
> Alternatively, is there some nice way to run checks in parallel
Yes, simply run: ctest -j4
By the way, ctest also has a nice man page in case you haven't found it