RE: AppVeyor issue

[Freddie Akeroyd - UKRI STFC via Core-talk <core-talk at aps.anl.gov>]

Hi,

The appveyor docs suggest "Visual Studio 2015" is supposed to be the default image if  APPVEYOR_BUILD_WORKER_IMAGE  is not specified in the yml, but given this doesn't seem to be the case you could specify this image explicitly for the 10.0 11.0 12.0 and 14.0 toolchains (as is done for mingw in the file)

Regards,

Freddie

-----Original Message-----
From: Core-talk <core-talk-bounces at aps.anl.gov> On Behalf Of Michael Davidsaver via Core-talk
Sent: 13 April 2020 19:27
To: Konrad, Martin <konrad at frib.msu.edu>
Cc: core-talk at aps.anl.gov
Subject: Re: AppVeyor issue

On 4/13/20 11:21 AM, Konrad, Martin wrote:
> Hi Michael,
>> What does the Export YAML give you?
>>
>> I see:
>>
>>> version: 1.0.{build}
>>>
>>> build:
>>>
>>> verbosity: minimal
> Thanks for sharing your settings. My exported YAML also had "Visual 
> Studio 2015". I deleted that resetting it to the default (which 
> appears to be "Visual Studio 2019"). After doing so I'm getting the 
> same output from "Export YAML" you posted. Still no luck running the build, though:
> https://ci.appveyor.com/project/MartinKonrad/epics-base-github
> 
> I compared your commit (d1dada33f49de16fedb9ddca9bedb666ea8daebb) with 
> mine (e6914f3b8089a417c9efc31940906854be182e6b) and I don't see any 
> changes in appveyor.yml. I'm wondering if AppVeyor has any caches I 
> could purge?

I does (I think) though the epics-base config have never used them.

The only thing I can think to try is building a different commit (fix a typo or something).