tag:help.appveyor.com,2012-11-13:/discussions/problems/5083-same-commit-has-build-successfully-on-july-21-fails-nowAppVeyor: Discussion 2018-10-19T08:17:58Ztag:help.appveyor.com,2012-11-13:Comment/404433102016-07-31T10:36:11Z2016-07-31T10:36:11ZSame commit has build successfully on July 21, fails now<div><p>Hi Christian,</p>
<p>Thanks for reporting about the issue.</p>
<p>I've noticed you are building on <code>Previous Visual Studio
2015</code> image. Yesterday we updated the image (minor update
with VS license fixed) and current image became previous.</p>
<p>I rolled back previous image to previous-previous, so your
builds will be working again. In the meantime we will try to
understand what's breaking the build on current image.</p></div>Feodor Fitsnertag:help.appveyor.com,2012-11-13:Comment/404433102016-07-31T11:33:01Z2016-07-31T11:33:02ZSame commit has build successfully on July 21, fails now<div><p>Hi Feodor,</p>
<p>thanks for your quick answer and fix! I can maybe contribute the
understanding:</p>
<p>As you might by now know :-), we are developing a VS test
adapter which integrates tests written in the C++ Google Test
framework with the VS test explorer. As it seems, MS is working on
the unit testing stuff with the last updates - they have caused us
all kinds of trouble. For instance, the 2nd hotfix to update 3
broke the test explorer completely on German VS instances (should
not affect other languages, though, afaik). If you are interested,
I can post a couple of links to MS issues.</p>
<p>We are also seeing a VS regression where links to files in the
test explorer that we create do not work any more. We haven't
completely understood the issue yet due to time constraints, but it
seems to be related to some path not being absolute any more, and
that's what I'm seeing in our failing end-to-end tests (which rely
on the installed VS version) - they try to normalize away the
actual paths (golden file testing approach), and that's not working
any more. Note that checking if our links are actually working
could only happen with UI tests, so I don't know if the installed
VS version has this issue, but something has apparently
changed.</p>
<p>Thus, any minor update of VS might break our build at the
moment, and this is probably what happened. I'm in fact working on
making our end-to-end tests more stable against changed output of
the VSTest.Console.exe tool (which is why our build is currently
running on the previous VS 2015 instance), but this time it seems
to be a deeper regression...</p>
<p>Sorry for the long mail :-) - I hope that my comments are
helpful.</p>
<p>Best,<br>
Christian</p></div>Christian Soltenborntag:help.appveyor.com,2012-11-13:Comment/404433102016-07-31T11:48:30Z2016-07-31T11:48:31ZSame commit has build successfully on July 21, fails now<div><p>And just to confirm this: master is indeed green again...</p>
<p>Looks like our build is a proper (and rather picky) test for the
VS 2015 image :-)</p></div>Christian Soltenborntag:help.appveyor.com,2012-11-13:Comment/404433102016-08-01T18:00:47Z2016-08-01T18:00:48ZSame commit has build successfully on July 21, fails now<div><p>Final comment (unless you have any questions): I have finished
test stabilization and changed our builds to use the current VS
2015 image. From my point of view, you can roll out that little
update to the previous image if this is beneficial for your other
users...</p></div>Christian Soltenborn