Test FAILed.

Just for the record, the following URL revealed a number of other potential patches for SPRNG:
https://stat.ethz.ch/pipermail/r-sig-hpc/2010-January/000512.html
I will not be reacting on it now, but keep on eye on it because somebody one day will meet the need...

Test PASSed.

@fgeorgatos: those patches don't seem to help with the segfaults with checksprng or timesprng, and don't seem to be needed to make the build work either?

Test report by @boegel
FAILED
Build succeeded for 2 out of 5
Linux SL 6.5, Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz, Python 2.6.6
See https://gist.github.com/86e4512bf4a885680b1d for a full test report.

Test report by @fgeorgatos
FAILED
Build succeeded for 2 out of 5
Linux debian 6.0.9, Intel(R) Xeon(R) CPU X5670 @ 2.93GHz, Python 2.6.6
See https://gist.github.com/c0d032f1da1e112d89a3 for a full test report.

Test report by @fgeorgatos
SUCCESS
Build succeeded for 5 out of 5
Linux debian 6.0.9, Intel(R) Xeon(R) CPU X5670 @ 2.93GHz, Python 2.6.6
See https://gist.github.com/d9d3ca569bf49c3bf5be for a full test report.

Hi Ken,

the only reason our previous tries gave an error is a trivial issue, of a non-visible patch file; fixable with:
cp SPRNG-2.0_fix-metropolis-test.patch .local/easybuild/sources/s/SPRNG/

Now, status is SUCCESS on my side, just attempt something similar on your side.

@fgeorgatos: now #1138 is merged in, syncing this branch with develop is sufficient as well (EB looks for patch files next to the easyconfig file location as well)

@boegel: fully agreed with your proposition;

However, the branch was synced already and, AFAI understand, it is the fact that patchfiles searching occurs in different paths, during --from-pr usage that triggered the issue. It could be a bug or, it could be a feature, depending how you look at it?!

Test report by @boegel
FAILED
Build succeeded for 2 out of 5
Linux SL 6.5, Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz, Python 2.6.6
See https://gist.github.com/b48947796a9e34aaecea for a full test report.

@fgeorgatos: I'm running into the same issue now, but this must be a bug in the --from-pr functionality... EB is looking for the patch file in the right location, but not finding it there, which is definitely a bug. I'll look into it.

OK, I checked this, and the issue is that the patch is not available next to the downloaded easyconfigs (since it's not being touched in this PR), causing it not to be found by EasyBuild, since it only looks in certain locations (source path, next to easyconfig, robot path, etc.).

So, there's nothing wrong with this PR. If you would use --from-pr on top of the current develop version of the easyconfigs repo, then it will work too.

Test report by @boegel
SUCCESS
Build succeeded for 5 out of 5 (5 easyconfigs in this PR)
Linux SL 6.5, Intel(R) Xeon(R) CPU E5-2670 0 @ 2.60GHz, Python 2.6.6
See https://gist.github.com/95c5c71c56a841a1a44c for a full test report.

Green light by Jenkins when using --from-pr on top of current develop branches, so good to go in. Thanks @fgeorgatos!