Ingvar Stepanyan
Ingvar Stepanyan
Ok so the problem was that setup-msbuild takes VS version as in their internal version, not product name (12 instead of 2013 and so on). This fixes finding MSBuild, but,...
@Youw Basically what you said > I believe the limitation is that not all versions of Visual Studio are pre-installed on self-hosted runners. except it's not even a couple of...
> It is actually running for PRs as well. Yeah I figured some comments above. It's running on this PR now.
> Yes that is the way to go. Ok since we're keeping Appveyor anyway, I've removed version matrix and artifacts from this config then, so it provides only testing across...
Although now there's a lot less value in this Github Action... Not sure if it's still worth it if we're still running AppVeyor anyway. Unless AppVeyor is moved to only...
I know, thanks :)
In retrospect, I probably should have marked this PR as draft to make it clear it's not quite ready for review but rather just me playing with CI config, as...
> > Then lets not touch the AppVeyor build config and only introduce new GithubAction in addtion to what we already have. > > Yes, that is better. Hm I'm...
Reverted AppVeyor change altogether for now to keep things simple. > > What if we at least remove VS2019 & VS2022 debug (where we don't care about artifacts) from AppVeyor?...
@tormodvolden FWIW this won't reproduce on CI since it doesn't have cross-platform emulated devices yet, but this revealed that the new extra checks in `stress_mt` are actually failing for me...