Github user brennonyork commented on the pull request:
https://github.com/apache/spark/pull/5443#issuecomment-92518053
@shaneknapp can you help me understand how Jenkins is doing the checkouts?
I'm seeing the PR builder outputting:
```
Building remotely on amp-jenkins-worker-06 (centos) in workspace
/home/jenkins/workspace/SparkPullRequestBuilder
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url https://github.com/apache/spark.git #
timeout=10
Fetching upstream changes from https://github.com/apache/spark.git
> git --version # timeout=10
> git fetch --tags --progress https://github.com/apache/spark.git
+refs/pull/5443/*:refs/remotes/origin/pr/5443/* # timeout=15
> git rev-parse origin/pr/5443/merge^{commit} # timeout=10
> git branch -a --contains c5916336e6aff94dd3abfc9a0a41a2528c765fce #
timeout=10
> git rev-parse remotes/origin/pr/5443/merge^{commit} # timeout=10
Checking out Revision c5916336e6aff94dd3abfc9a0a41a2528c765fce
(origin/pr/5443/merge)
> git config core.sparsecheckout # timeout=10
> git checkout -f c5916336e6aff94dd3abfc9a0a41a2528c765fce
```
although I'm a bit confused what checkout I should switch between if, say,
I want to, from a PR, checkout the `master` branch, then switch back to the
given PR branch, then possibly back to `master`, and finally back to the PR
again.
I'm currently doing what I believe is correct
[here](https://github.com/apache/spark/blob/master/dev/tests/pr_new_dependencies.sh#L42)
although there are times when the checkout from `master` back to the current
PR fails, producing odd dependency reports. I've noticed that Jenkins is using
the `-f` flag which I've added, but wanted to see if you had any thoughts into
the matter.
Further, I've added `echo` statements to dump the `ghprbActualCommit`, the
`sha1`, and the output of `git rev-parse HEAD`. Each are different commit
hashes which makes me further think this is the cause for all the errors.
Again, any advice?
---
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]
