Closed janpio closed 5 years ago
Reason behind this is probably that VS17 does not support building for Windows 8.1 any more, so by fixing the VS detector to pick up the correct VS17 install, we broke the 8.1 builds that still are always tested.
Solution might be to separate the Win10 and Win8.1 tests and only run the matching ones?
Another solution might be to use pending
similar to https://github.com/apache/cordova-windows/blob/585dc2f4e4c0794b72af6f4b448bb42ffd213800/spec/e2e/endtoend.spec.js#L218-L220 in all the Windows 8.1 tests. Does that make sense @raphinesse?
Sure! Seems sensible, judging from what you wrote above. If a fair amount of tests are affected, you might even want to factor above snippet out into a function, so you only have a one-liner in the affected tests. Something like skipIfUsingVS2017()
.
Currently working on splitting the tests in Win8.1 and Win10 batches, then using pending
on them to get rid of the failures. Additionally I will add another build with explicit MSBUILDDIR
set to C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\MSBuild\15.0\Bin
- so future changes on the discovery logic will pop up earlier.
Build is green :D
CI started failing when https://github.com/apache/cordova-windows/pull/329 was merged:
https://github.com/apache/cordova-windows/commit/95401b36b20e5c4b37a3253ed0042b98380caf27 https://ci.appveyor.com/project/Humbedooh/cordova-windows/builds/24305931
Example:
(
CordovaError: No valid MSBuild was detected for the selected target:
is a known red herring here: https://github.com/apache/cordova-windows/issues/266)Difference between working and broken build is this:
Before:
After:
So improving the VS detector breaks on AppVeyor :/