I opened https://issues.apache.org/jira/browse/INFRA-15219 to ask INFRA to look into the Appveyor issue.
In the meantime, builds are still running on https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/history so we can look there to make sure we haven't broken Windows with a patch On Wed, Oct 4, 2017 at 11:02 AM, Wes McKinney <wesmck...@gmail.com> wrote: > I just merged ARROW-1640 which should fix this issue for now: > > https://github.com/apache/arrow/pull/1160 > > Please rebase your PRs to pick up the fix to get passing builds > > The Appveyor notifications issue is still ongoing, I opened > https://github.com/appveyor/ci/issues/1842 and will get ASF Infra to > help if need be > > - Wes > > On Wed, Oct 4, 2017 at 8:56 AM, Wes McKinney <wesmck...@gmail.com> wrote: >> Sometime in the last 48 hours we've started having HTTPS problems >> downloading third party tarballs from GitHub in some of our builds. >> Here's a build 2 days ago that passed: >> >> https://travis-ci.org/apache/arrow/builds/282102028 >> >> Here's an example of a failing build: >> >> https://travis-ci.org/wesm/arrow/jobs/282719318 >> >> CMake Error at googletest_ep-stamp/download-googletest_ep.cmake:21 (message): >> error: downloading >> 'https://github.com/google/googletest/archive/release-1.8.0.tar.gz' failed >> status_code: 1 >> status_string: "Unsupported protocol" >> log: Protocol "https" not supported or disabled in libcurl >> Closing connection -1 >> >> It does not seem that any of the likely culprits of this failure have >> changed (cmake, libcurl, openssl) >> >> Also, Appveyor is not notifying our PRs in GitHub anymore, but the >> builds are triggering and passing: >> >> https://ci.appveyor.com/project/ApacheSoftwareFoundation/arrow/history >> >> I'm not sure what's going on yet, but I am going to investigate this >> morning and see if I can figure it out. If anyone has ideas please >> pass them on >> >> - Wes
