I just push an empty commit 15 minutes ago to my PR branch and it did not trigger a precheckin. Should I just keep pushing empty commits until something happens? Is there another way to trigger a precheckin? Sorry for all the questions but I seem to be blocked.
https://github.com/apache/geode/pull/2768 Thanks, Kirk On Fri, Nov 2, 2018 at 10:56 AM, Kirk Lund <kl...@apache.org> wrote: > That's unfortunate, half of the precheckin jobs for my PR started > correctly and half of them failed with: > > /usr/lib/ruby/gems/2.4.0/gems/octokit-4.8.0/lib/octokit/response/raise_error.rb:16:in > `on_complete': GET https://api.github.com/repos/apache/geode/pulls/2768: > 404 - Not Found // See: https://developer.github.com/ > v3/pulls/#get-a-single-pull-request (Octokit::NotFound) > from /usr/lib/ruby/gems/2.4.0/gems/faraday-0.14.0/lib/faraday/response.rb:9:in > `block in call' > from > /usr/lib/ruby/gems/2.4.0/gems/faraday-0.14.0/lib/faraday/response.rb:61:in > `on_complete' > from /usr/lib/ruby/gems/2.4.0/gems/faraday-0.14.0/lib/faraday/response.rb:8:in > `call' > from > /usr/lib/ruby/gems/2.4.0/gems/faraday-http-cache-2.0.0/lib/faraday/http_cache.rb:290:in > `fetch' > from > /usr/lib/ruby/gems/2.4.0/gems/faraday-http-cache-2.0.0/lib/faraday/http_cache.rb:195:in > `process' > from > /usr/lib/ruby/gems/2.4.0/gems/faraday-http-cache-2.0.0/lib/faraday/http_cache.rb:142:in > `call!' > from > /usr/lib/ruby/gems/2.4.0/gems/faraday-http-cache-2.0.0/lib/faraday/http_cache.rb:115:in > `call' > from > /usr/lib/ruby/gems/2.4.0/gems/faraday-0.14.0/lib/faraday/rack_builder.rb:143:in > `build_response' > from > /usr/lib/ruby/gems/2.4.0/gems/faraday-0.14.0/lib/faraday/connection.rb:387:in > `run_request' > from > /usr/lib/ruby/gems/2.4.0/gems/faraday-0.14.0/lib/faraday/connection.rb:138:in > `get' > from /usr/lib/ruby/gems/2.4.0/gems/sawyer-0.8.1/lib/sawyer/agent.rb:94:in > `call' > from > /usr/lib/ruby/gems/2.4.0/gems/octokit-4.8.0/lib/octokit/connection.rb:156:in > `request' > from > /usr/lib/ruby/gems/2.4.0/gems/octokit-4.8.0/lib/octokit/connection.rb:19:in > `get' > from > /usr/lib/ruby/gems/2.4.0/gems/octokit-4.8.0/lib/octokit/client/pull_requests.rb:31:in > `pull_request' > from /usr/lib/ruby/gems/2.4.0/gems/octokit-4.8.0/lib/octokit.rb:46:in > `method_missing' > from /opt/resource/lib/commands/in.rb:78:in `pr' > from /opt/resource/lib/commands/in.rb:20:in `output' > from /opt/resource/lib/commands/in.rb:110:in `<main>' > > These are the ones that failed with the Octokit not found error: > > https://concourse.apachegeode-ci.info/teams/main/pipelines/ > apache-develop-pr/jobs/UnitTest/builds/347 > https://concourse.apachegeode-ci.info/teams/main/pipelines/ > apache-develop-pr/jobs/IntegrationTest/builds/347 > https://concourse.apachegeode-ci.info/teams/main/pipelines/ > apache-develop-pr/jobs/AcceptanceTest/builds/346 > > UpgradeTest, DistributedTest and StressNewTest all started up fine > (StressNewTest already finished green). > > Is there a way to kill the above jobs to avoid wasting Pivotal's money? > > I'll go ahead start a new precheckin from scratch. Thanks! > > On Fri, Nov 2, 2018 at 10:44 AM, Jacob Barrett <jbarr...@pivotal.io> > wrote: > >> You can’t restart PR jobs even with access. Concourse will only restart >> the latest PR, which may not be yours. To restart a PR check you push and >> empty commit to your branch. >> >> -Jake >> >> >> > On Nov 2, 2018, at 10:38 AM, Kirk Lund <kl...@apache.org> wrote: >> > >> > I want to be able to restart my precheckin jobs. Specifically, I'd like >> to >> > restart the UnitTest job on my latest PR precheckin: >> > >> > https://concourse.apachegeode-ci.info/teams/main/pipelines/a >> pache-develop-pr/jobs/UnitTest/builds/347 >> > >> > It seems to have hit a snag that's unrelated to my PR: >> > >> > /usr/lib/ruby/gems/2.4.0/gems/octokit-4.8.0/lib/octokit/resp >> onse/raise_error.rb:16:in >> > `on_complete': GET https://api.github.com/repos/apache/geode/pulls/2768 >> : >> > 404 - Not Found // See: >> > https://developer.github.com/v3/pulls/#get-a-single-pull-request >> > (Octokit::NotFound) >> > from >> > /usr/lib/ruby/gems/2.4.0/gems/faraday-0.14.0/lib/faraday/res >> ponse.rb:9:in >> > `block in call' >> > from >> > /usr/lib/ruby/gems/2.4.0/gems/faraday-0.14.0/lib/faraday/res >> ponse.rb:61:in >> > `on_complete' >> > from >> > /usr/lib/ruby/gems/2.4.0/gems/faraday-0.14.0/lib/faraday/res >> ponse.rb:8:in >> > `call' >> > from >> > /usr/lib/ruby/gems/2.4.0/gems/faraday-http-cache-2.0.0/lib/f >> araday/http_cache.rb:290:in >> > `fetch' >> > from >> > /usr/lib/ruby/gems/2.4.0/gems/faraday-http-cache-2.0.0/lib/f >> araday/http_cache.rb:195:in >> > `process' >> > from >> > /usr/lib/ruby/gems/2.4.0/gems/faraday-http-cache-2.0.0/lib/f >> araday/http_cache.rb:142:in >> > `call!' >> > from >> > /usr/lib/ruby/gems/2.4.0/gems/faraday-http-cache-2.0.0/lib/f >> araday/http_cache.rb:115:in >> > `call' >> > from >> > /usr/lib/ruby/gems/2.4.0/gems/faraday-0.14.0/lib/faraday/rac >> k_builder.rb:143:in >> > `build_response' >> > from >> > /usr/lib/ruby/gems/2.4.0/gems/faraday-0.14.0/lib/faraday/con >> nection.rb:387:in >> > `run_request' >> > from >> > /usr/lib/ruby/gems/2.4.0/gems/faraday-0.14.0/lib/faraday/con >> nection.rb:138:in >> > `get' >> > from /usr/lib/ruby/gems/2.4.0/gems/sawyer-0.8.1/lib/sawyer/agent. >> rb:94:in >> > `call' >> > from >> > /usr/lib/ruby/gems/2.4.0/gems/octokit-4.8.0/lib/octokit/conn >> ection.rb:156:in >> > `request' >> > from >> > /usr/lib/ruby/gems/2.4.0/gems/octokit-4.8.0/lib/octokit/conn >> ection.rb:19:in >> > `get' >> > from >> > /usr/lib/ruby/gems/2.4.0/gems/octokit-4.8.0/lib/octokit/clie >> nt/pull_requests.rb:31:in >> > `pull_request' >> > from /usr/lib/ruby/gems/2.4.0/gems/octokit-4.8.0/lib/octokit.rb:46:in >> > `method_missing' >> > from /opt/resource/lib/commands/in.rb:78:in `pr' >> > from /opt/resource/lib/commands/in.rb:20:in `output' >> > from /opt/resource/lib/commands/in.rb:110:in `<main>' >> > >
