The list bounced my reply yesterday (Original Message, below). Trying again today.
Cheers, /Tony Instead of attachments, this time just copy-paste the shell commands from the demo Jenkins job. : git clone source git clone ssh://[email protected]/chapel-lang/chapel.git chapel : make Chapel cd chapel make make test-venv : add these bits to PATH, etc source util/setchplenv.bash : run some Chapel tests cd test start_test -no-recurse release/examples : end Jenkins build step -----Original Message----- From: Tony Wallace <[email protected]> Date: Wednesday, June 27, 2018 at 11:16 AM Hi Timothy, Not sure I understand this question, because there's nothing I can think of about Jenkins that would make Chapel or start_test work much differently than if you ran it directly from e.g. any shell window. It is true, stdin/stdout/stderr are not "interactive" in a Jenkins job- not connected to a terminal device- however, start_test does not expect a terminal device. It's OK for Jenkins to connect stdin to /dev/null, stdout/stderr to the console log. To demonstrate, here is a very simple Jenkins job that contains nothing but this one Execute Shell build step (att 1 "Screen Shot") and produces this console output (att 2 "consoleText", edited for length). Does this represent the question you were asking? HTH, /Tony -----Original Message----- From: Brad Chamberlain <[email protected]> Date: Tuesday, June 26, 2018 at 5:03 PM Hi Tony -- Do you have any experience here that would be helpful? -Brad ---------- Forwarded message ---------- Date: Tue, 26 Jun 2018 15:07:55 From: "Stavenger, Timothy J" <[email protected]> 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
