Zachary Ware zachary.ware+pydev at gmail.com
Mon May 29 14:46:49 EDT 2017

• Previous message (by thread): [python-committers] Appveyor tests failing for CPython?
• Next message (by thread): [python-committers] Appveyor tests failing for CPython?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

On Mon, May 29, 2017 at 9:19 AM, Zachary Ware
<zachary.ware+pydev at gmail.com> wrote:
> On Mon, May 29, 2017 at 9:09 AM, Alex Gaynor <alex.gaynor at gmail.com> wrote:
>> Hi all,
>>
>> It looks like appveyor tests are currently failing on all builds (something
>> about UNC paths + imports). Was appveyor enabled recently, or did the test
>> regress?
>
> AppVeyor has been enabled for some time, but is not (yet) required.
> It's possible that something has regressed, but it looks kind of like
> AppVeyor changed something in the environment, particularly since all
> of our Windows buildbots are fine.

AppVeyor is investigating, see
https://appveyor.tenderapp.com/discussions/problems/6765-environmental-change-blocking-unc-path-access
for updates.

-- 
Zach

---

• Previous message (by thread): [python-committers] Appveyor tests failing for CPython?
• Next message (by thread): [python-committers] Appveyor tests failing for CPython?
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the python-committers mailing list