tag:help.appveyor.com,2012-11-13:/discussions/problems/18543-detection-of-clexe-just-started-failing-in-default-build-imageAppVeyor: Discussion 2019-01-15T19:49:36Ztag:help.appveyor.com,2012-11-13:Comment/466529092018-12-12T00:36:27Z2018-12-12T00:36:27ZDetection of `cl.exe` just started failing in default build image<div><p>We are rolling out the update to <code>Visual Studio 2017</code> image with the latest VS 2017 15.9.4 which was already applied to <code>GCE</code> environment. You may get back to previous <code>Previous Visual Studio 2017</code> image.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/466529092018-12-12T01:12:38Z2018-12-12T01:12:38ZDetection of `cl.exe` just started failing in default build image<div><p>Ok thanks!</p>
<p>Is there an expected timescale for when the image rotation happens again? (when the current "previous" is overwritten with the current non-previous presumably).</p>
<p>Additionally, do y'all have a list of changes between the last image and this one? (to help us dig into what's wrong with our code)</p></div>acrichtontag:help.appveyor.com,2012-11-13:Comment/466529092018-12-12T01:18:35Z2018-12-12T01:18:35ZDetection of `cl.exe` just started failing in default build image<div><p>This is the list of changes: <a href="https://github.com/appveyor/ci/milestone/141">https://github.com/appveyor/ci/milestone/141</a></p>
<p>My best guess it is VS 2017 15.9.4 that broke your build thought that’s weird the location of cl.exe has changed.</p>
<p>We try to update images in 2-3 weeks but keeping previous image, especially for VS 2017, depends on the number of issues VS 2017 upgrade brings to people. Despite it’s supposed to be “minor” VS update it’s usually quite disruptive.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/466529092018-12-12T01:25:54Z2018-12-12T01:25:54ZDetection of `cl.exe` just started failing in default build image<div><p>Hm we <a href="https://ci.appveyor.com/project/rust-lang/rust/builds/20944280/job/of3yab4revjyuuc6">tried out <code>Previous</code></a> but it's still getting the same error, did we configure that incorrectly though?</p></div>acrichtontag:help.appveyor.com,2012-11-13:Comment/466529092018-12-12T01:35:34Z2018-12-12T01:35:34ZDetection of `cl.exe` just started failing in default build image<div><p>Well, “Preview” image hasn’t been changed. I forgot you are on Preview. Will take a look - maybe it’s new jobs scheduling thought could it be some change on your side?</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/466529092018-12-12T01:42:20Z2018-12-12T01:42:20ZDetection of `cl.exe` just started failing in default build image<div><p>Ah right I forgot about that too! Our <a href="https://ci.appveyor.com/project/rust-lang/rust/builds/20936147">last successful build</a> was a few hours ago with <a href="https://ci.appveyor.com/project/rust-lang/rust/builds/20942865/job/0729qrtm06qg6t92">our next failing build</a> just recently having no substantive changes between the two. Doesn't mean that it's not our bug by any means, but I <em>think</em> at least it's unlikely that it was a change on our end.</p>
<p>If the preview image didn't change though then... that's a bit of an oddity!</p></div>acrichtontag:help.appveyor.com,2012-11-13:Comment/466529092018-12-12T01:49:43Z2018-12-12T01:49:43ZDetection of `cl.exe` just started failing in default build image<div><p>OK, let me double check and get back to you.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/466529092018-12-12T04:06:53Z2018-12-12T04:06:53ZDetection of `cl.exe` just started failing in default build image<div><p>Alex, it must be a new job scheduling algorithm that routed that build to a wrong image (<code>Visual Studio 2017</code> instead of <code>Preview</code>), sorry for that.</p>
<p>I've put your account back to previous algo while investigating. And, yes, please ensure your infrastructure code supports <code>starting</code> state.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/466529092018-12-12T04:23:15Z2018-12-12T04:23:15ZDetection of `cl.exe` just started failing in default build image<div><p>Thanks for taking a look! A <a href="https://ci.appveyor.com/project/rust-lang/rust/builds/20946448">newly scheduled build</a> looks like it's making progress, past the point of failure before, so I believe that fix has worked!</p>
<p>Definitely a bug on our end for not handling <code>starting</code>, and should be fixed now!</p>
<p>Our builds <em>should</em> work as-is in the <code>Visual Studio 2017</code> images anyway, so I'll start investigating why they aren't working and fix that bug independently too.</p>
<p>Thanks again so much for the fast response here!</p></div>acrichtontag:help.appveyor.com,2012-11-13:Comment/466529092018-12-12T04:24:14Z2018-12-12T04:24:14ZDetection of `cl.exe` just started failing in default build image<div><p>Great, thanks for the update!</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/466529092018-12-16T23:28:36Z2018-12-16T23:28:36ZDetection of `cl.exe` just started failing in default build image<div><p>Hi Alex,</p>
<p>Are you guys ready to be moved to a new job scheduling algorithm (remember that new <code>Starting</code> status)? Other than that new status the scheduling works as expected now.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/466529092018-12-17T02:54:10Z2018-12-17T02:54:10ZDetection of `cl.exe` just started failing in default build image<div><p>Oh sorry that wasn't clear earlier, but yes we fixed the <code>starting</code> status showing up as soon as we saw it, it just happened to happen at the same time as the other part of the issue! It sounds like we're still scheduled with the same image we're using today, so if that's the case we can be switched over at any time!</p></div>acrichton