Travis-CI builds cannot connect to Test Platform on OS X

[jmudavid]

Hello,
I noticed that the Travis CI builds are failing after the last set of updates made automatically to dependencies.props. I saw this issue in JsonPatch which I am using, but also saw it within the CORS project. There may be others impacted as well. I don't know where the CI process is managed or who has access. Is there anybody with experience in CI who could help out.
Thanks!

[Tratcher]

Please link to Travis runs you're concerned about. We know about some issues and have bugs filed to track them.

[jmudavid]

@Tratcher,

Thanks. Here is the latest from JsonPatch.
https://travis-ci.org/aspnet/JsonPatch/builds/352066224

It seems like they started with this build:
https://travis-ci.org/aspnet/JsonPatch/builds/351024194

I was poking around to see if an other projects had the issue and found the same error in CORS: https://travis-ci.org/aspnet/CORS/builds/351019817

I didn't look any further than that.
Thanks!

[Tratcher]

FYI: I saw similar issues in ServerTests on runtime 2.1.0-preview2-26225-03 but they went away when I updated to 2.1.0-preview2-26308-01.

https://travis-ci.org/aspnet/ServerTests/jobs/351602085
https://travis-ci.org/aspnet/ServerTests/jobs/351608917

RE: aspnet/ServerTests#104

[Tratcher]

@ryanbrandenburg

[jmudavid]

I pulled the latest code for JsonPatch and I am now seeing the same errors locally, so it may be something related to the way that module is configured. I will try and get help from somebody on that side unless you guys have other thoughts.

[ryanbrandenburg]

If you're running into this problem it's because that repo hasn't gotten new dependencies. Run .\run.ps1 -update upgrade deps and it should resolve your issues. If you happen to be making a PR take the changes to korebuild-lock.txt and build/dependencies.props along with it.

Normally we have a script that does this automatically once a week, but it hasn't passed in a while because we've had a lot of stuff changing.

[jmudavid]

@ryanbrandenburg I reset my local branch and ran the script from the package manager console (is that ok), but now the code doesn't compile with a bunch of missing references. Is there a specific package source I need to add to Visual Studio?

[ryanbrandenburg]

@jmudavid your problem didn't replicated for me on either dev or release/2.1 our automated system updated dev to the latest version of everything 18 hours ago, do you still experience this issue on a clean copy of dev? If see please let us know the text of the error messages you're getting and a branch on your fork of the project containing all your local changes.

[jmudavid]

@ryanbrandenburg, I realized I wasn't updated from the aspnet repo, only my local branch. After getting the changes pulled in properly, I am getting the following error when trying to run my tests:
[3/26/2018 1:30:29 PM Error] Microsoft.VisualStudio.TestPlatform.ObjectModel.TestPlatformException: Testhost process exited with error: It was not possible to find any compatible framework version The specified framework 'Microsoft.NETCore.App', version '2.1.0-preview2-26130-04' was not found.

It says I have up to 2.1.0-preview1-26216-03 installed. I see that updated available in nuget, although it says "Not available in this source." I am guessing I need an additional feed, is that right? Thanks!

[ryanbrandenburg]

My best guess is you need to run "./build.cmd" once from the command-line in order to ensure you have the proper framework installed.

[jmudavid]

@ryanbrandenburg, Is there some docs that I am missing that goes through the steps (initial or periodic) that we need to go through?

I tried running "./build.cmd" which gave the following error:
`C:\Users\xxx.dotnet\buildtools\korebuild\2.1.0-preview3-17001\KoreBuild.Verify.targets(42,5): error KRB5002: - C:\Users\dhumphreys\Documents\Code\JsonPatch\artifacts\manifest.xml [C:\Users\xxx.dotnet\buildtools\korebuild\2.1.0-preview3-17001\KoreBuild.proj]
0 Warning(s)
1 Error(s)

Time Elapsed 00:00:47.59
/build.cmd : dotnet.exe failed with exit code: 1
At line:1 char:1
/build.cmd
CategoryInfo : NotSpecified: (dotnet.exe failed with exit code: 1:String) [], RemoteException
FullyQualifiedErrorId : NativeCommandError

At C:\Users\xxx.dotnet\buildtools\korebuild\2.1.0-preview3-17001\scripts\common.psm1:11 char:9
throw "$cmdName failed with exit code: $exitCode"
CategoryInfo : OperationStopped: (dotnet.exe failed with exit code: 1:String) [],
RuntimeException`

I ran your original update dependency script, but no luck there either. I looked on line and found the nuget for the preview release being asked for nuget.exe install Microsoft.NETCore.App -Version 2.1.0-preview2-26130-04 -Source https://dotnet.myget.org/F/dotnet-core/api/v3/index.json but when I try to run that I get the following error Install-Package : NU1202: Package Microsoft.NETCore.App 2.1.0-preview2-26325-03 is not compatible with netstandard2.0

JsonPatch is set to target netstandard2.0, and I am not entirely sure why it has the dependency on Microsoft.NETCore.App. Maybe the new version of Microsoft.NETCore.App has an additional check that wasn't here before, is that possible?

Thanks for your help trying to understand all the moving parts going on right now.

[ryanbrandenburg]

@jmudavid it looks like you truncated some of the error message there, the full thing should look something like this. As that message makes a bit clearer, you have things which the build does not expect in your artifacts directory. You can either run ./build.cmd /t:Clean or git clean -xdf to get rid of them. The steps to get a repo running are generally (with some exceptions for more complicated repos like IISIntegration)

1. Run build.cmd once to install run-times and whatnot that VS won't let us.
2. Develop however you want.

You just seem to have gotten into a bad state (probably while switching between branches) with your artifacts directory that our build script doesn't fix automatically.