I'm using the Chapel language's start_test to run unit & performance tests on
my project's code (as we anxiously wait for the official Chapel test
framework). The unit tests appear to be working fine. The performance tests
run, but fail at
https://github.com/chapel-lang/chapel/blob/release/1.16/util/start_test#L936-L943.
I'm running this in Jenkins in a chapel/chapel:1.16.0 Docker container.
In my Jenkinsfile I export the 'CHPL_TEST_PERF_DIR' env variable, 'cd' into the
test folder, and then run:
start_test --performance
The thought was I'd start about as simple as possible, but I get the error:
[Error: Failed to save current sha to
/var/lib/jenkins/jenkins-home/workspace/HPDA/AHM/chgl/test/performance/dat/perfSha.dat]
The file exists in Jenkins' workspace - at least after the build finishes. It
looks like the start_test script is trying to execute the 'computePerfStats'
util, but is failing without logging what the problem is.
Granted this is rather vague, but do you have an idea of what may be going
wrong? Or at least some direction as to where to look? Is there a way to turn
on verbose logging for start_test to get a better idea of what is happening?
Thanks!
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Chapel-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/chapel-users
