Open ronawho opened 5 years ago
I know some users have used Chapel docker images in order to test chapel code -- I'll see if I can find an example of that.
https://github.com/LouisJenkinsCS/Chapel-Data-Structures/blob/master/.travis.yml
Can probably do that and something to install fftw, and then check multi-locale gasnet for small problem sizes.
Basic travis testing is now on, including a fancy little badge on our front page!
Nice!
I wasn't sure what else we wanted to test. I was originally thinking we could just use start_test and run everything in the example dir, but start_test is just what I'm familiar with and not really meant for end-users.
I haven't followed it as well as I should, but there has been some recent work with mason and unit testing. @ben-albrecht likely knows more.
I like start_test and have used it a bunch, but most of the example directory isn't really designed for that. In fact, the example directory is largely a bunch of my musings, plus the NPB benchmark and a few tests.
The two other tests that we could probably run are
Unfortunately, those "tests" really currently just print things to the screen and I look at them and decide whether they've passed. I should put in logic there to print something, but it's not risen to the top of my stack.
Would be nice to add some Travis-CI (or whatever CI you prefer) testing
(Occured to me while looking at https://github.com/npadmana/DistributedFFT/pull/29 and thinking, "oh, I should probably run some of those correctness checks when I'm making changes")