We're running 'start_test' from Jenkins jobs for both unit & performance tests
(can't wait for https://github.com/chapel-lang/chapel/issues/9730!)
The 'start_test' python script works by comparing stdout to a .good file. This
runs into a problem were stdout is already redirected elsewhere - like in
Jenkins CI environments. In our case, we ssh into a separate machine for
running Chapel code in a known environment and execute start_test from there.
Our tests are failing because the stdout never gets written to the .out.tmp
files to be compared to our .good. Instead the stdout is redirected for
Jenkins' logs.
Anyone in the Chapel users group experience this before & have a workaround /
solution? I've tried starting new bash sessions without success.
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
