Github user shaneknapp commented on the pull request:
https://github.com/apache/spark/pull/5784#issuecomment-97894913
so, believe it or not, the jenkins bash environment is actually atomic (all
machines are identical hardware, same kernel, system updates, package versions,
ssh bash environment, etc). you can see the bash environment for the worker
this job executed on here
(https://amplab.cs.berkeley.edu/jenkins/computer/amp-jenkins-worker-08/log),
and it's identical to all of the other ones.
regarding sha1, derp. i totally knew that. :p
anyways, i'll poke around those shell scripts some more and see if there's
anything i can tweak to better report/fail on errors. i'm also going to redir
a lot of the git error output to /dev/null as it's been cluttering up the test
logs. i know there's a PR to move this stuff to python, but for the time being
i'll see if i can't make things better. once the PR is done i'll add you
(@brennonyork) as a reviewer.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
