But when I sent the email, the PR page on github stated:
This branch has no conflicts with the base branchMerging can be performed
automatically.
Which, in my understanding means there are no merge conflicts.
Stuff is flaky and that's ok. I just want to know how it's supposed to work
so I know w
Above that, though, in the acquisition of the *geode* resource, we see
/opt/resource/lib/commands/in.rb:23:in `output': *PR has merge conflicts*
(RuntimeError)
from /opt/resource/lib/commands/in.rb:110:in `'
That resource could not then be passed to the lower tasks *rsync_code_down *et
al, resul
Just in case, others hit this: The one I was asking about failed with
"missing inputs: geode, instance-data" which Dan said means that Concourse
barfed. When this happens, pushing an empty commit or anything else was
recommended to re-trigger.
https://concourse.apachegeode-ci.info/teams/main/pipel
Just to disseminate the knowledge...
Although we like it when everyone just works nicely, you can check the
consumption of your PR in the Concourse by looking at the *geode* resource
in the *apache-develop-pr* pipeline [1]. This resource passes the PR
number and associated SHA to test against, so
Nevermind. I pushed again and it seems to have triggered this time.
On Tue, Oct 30, 2018 at 2:51 PM, Kirk Lund wrote:
> I have a PR that I updated a while ago, but it's not automatically firing
> a precheckin.
>
> What's the expected behavior? Is it supposed to automatically trigger a
> precheck
I have a PR that I updated a while ago, but it's not automatically firing a
precheckin.
What's the expected behavior? Is it supposed to automatically trigger a
precheckin if I push more changes?
Here's my PR: https://github.com/apache/geode/pull/2730
PS: the PR isn't ready to actually merge, it'
