On Wed, 5 Sep 2018 at 04:56 Paul Moore wrote:
> On Wed, 5 Sep 2018 at 12:24, Antoine Pitrou wrote:
> > For some reason it seems to be located in a hidden directory
> > (".github/appveyor.yml"). Not the most intuitive decision IMHO.
> > Travis' own config file ".travis.yml" is still at
On Wed, Sep 5, 2018 at 4:32 PM Paul Moore wrote:
>
> On Wed, 5 Sep 2018 at 14:47, Zachary Ware
> wrote:
> >
> > On Wed, Sep 5, 2018 at 6:23 AM Antoine Pitrou wrote:
> > > On Wed, 5 Sep 2018 11:03:48 +0100
> > > Paul Moore wrote:
> > > > On Wed, 5 Sep 2018 at 10:55, Victor Stinner wrote:
> >
On Wed, Sep 5, 2018 at 9:30 AM Paul Moore wrote:
> I presume you're suggesting keeping 2017 is so that we don't have
> stray 2015-built artifacts in the cache, which makes sense to me, and
> I have a mild preference for keeping the latest compiler, as that's
> likely the one that people will find
On Wed, 5 Sep 2018 at 14:47, Zachary Ware wrote:
>
> On Wed, Sep 5, 2018 at 6:23 AM Antoine Pitrou wrote:
> > On Wed, 5 Sep 2018 11:03:48 +0100
> > Paul Moore wrote:
> > > On Wed, 5 Sep 2018 at 10:55, Victor Stinner wrote:
> > > > Who ows the "python" AppVeyor project?
>
> That seems to have
Le mer. 5 sept. 2018 à 15:47, Zachary Ware
a écrit :
> For the actual issue at hand, the problem arises from doing builds on
> 3.6 with both the VS2015 and VS2017 images. Apparently something
> built in `/externals` by the VS2015 build gets cached, which then
> breaks the VS2017 build; I haven't
On Wed, Sep 5, 2018 at 6:23 AM Antoine Pitrou wrote:
> On Wed, 5 Sep 2018 11:03:48 +0100
> Paul Moore wrote:
> > On Wed, 5 Sep 2018 at 10:55, Victor Stinner wrote:
> > > Who ows the "python" AppVeyor project?
That seems to have fallen to me for the most part.
> > > Can someone please give me
On Wed, Sep 5, 2018 at 12:55 PM Victor Stinner wrote:
>
> Hi,
>
> It's no longer possible to merge any change in the 3.6 branch of
> CPython, because the AppVeyor job fails:
> https://bugs.python.org/issue34575
>
> It seems like AppVeyor has a build cache and this cache is outdated. I
> tried to
I wrote some notes about our CIs. Link to AppVeyor notes:
https://pythondev.readthedocs.io/ci.html#appveyor
Victor
Le mer. 5 sept. 2018 à 12:04, Paul Moore a écrit :
>
> On Wed, 5 Sep 2018 at 10:55, Victor Stinner wrote:
> >
> > Hi,
> >
> > It's no longer possible to merge any change in the 3.6
On Wed, 5 Sep 2018 at 12:24, Antoine Pitrou wrote:
> For some reason it seems to be located in a hidden directory
> (".github/appveyor.yml"). Not the most intuitive decision IMHO.
> Travis' own config file ".travis.yml" is still at repository root, which
> makes things more confusing.
Thanks,
On Wed, 5 Sep 2018 11:03:48 +0100
Paul Moore wrote:
> On Wed, 5 Sep 2018 at 10:55, Victor Stinner wrote:
> >
> > Hi,
> >
> > It's no longer possible to merge any change in the 3.6 branch of
> > CPython, because the AppVeyor job fails:
> > https://bugs.python.org/issue34575
> >
> > It seems like
On Wed, 5 Sep 2018 at 10:55, Victor Stinner wrote:
>
> Hi,
>
> It's no longer possible to merge any change in the 3.6 branch of
> CPython, because the AppVeyor job fails:
> https://bugs.python.org/issue34575
>
> It seems like AppVeyor has a build cache and this cache is outdated. I
> tried to use
Hi,
It's no longer possible to merge any change in the 3.6 branch of
CPython, because the AppVeyor job fails:
https://bugs.python.org/issue34575
It seems like AppVeyor has a build cache and this cache is outdated. I
tried to use the REST API but I'm not allowed to invalidate the cache:
even the
12 matches
Mail list logo
