-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unpin EF dependencies then grab the latest #10682
Conversation
dougbu
commented
May 31, 2019
- partially reverts 58c6772
- temporarily moves CoreFx, core-setup and Extensions dependencies
- will update EF Core repo before finalizing this PR
@ajcvickers lots of MusicStore failures in https://dev.azure.com/dnceng/public/_build/results?buildId=206727 Any suggestions? |
Ah, man. I didn't realize we were still building MusicStore. I will take a look. |
From my perspective:
|
@dougbu Pushed MusicStore fixes |
@dougbu Note that @smitpatel merged a race condition fix that we may need to take here to get the tests passing reliably. |
Failures are now focused on 2 test templates:
I suspect the template itself needs to be updated to match the latest from EF. @ajcvickers could you please have a look? @ryanbrandenburg is the templates guy if you're not sure about the context. Separately, the following tests failed only on macOS. Is there a race in these tests?
|
@dougbu Will take a look |
6cf65d7
to
5179ef3
Compare
🆙📅 to rebase on 'master' and see if @smitpatel's fix cleans up the tests |
@dougbu It looks like all the changes I pushed here have been removed! |
bf4fa77
to
6c8d2bd
Compare
@ajcvickers yeah, that was my fault. Fortunately I still had 6cf65d7 on my machine (GitHub lost that commit) and have restored it. |
/azp run AspNetCore-ci |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
/azp run AspNetCore-ci |
Azure Pipelines successfully started running 1 pipeline(s). |
With the addition of a spurious Libuv test failure, looks like the two tests that failed consistently are still failing:
|
@dougbu @ryanbrandenburg I can't get the ProjectTemplates tests to run locally, even though everything else in AspNetCore is working. I keep seeing the following, even on master:
|
@ajcvickers is the information in the folder's README.md file helpful? |
In particular, run |
@dougbu Yes, read that and tried that already. Running |
Can you run the template tests after the successful The other possibility would be downloading the ProjectTemplates.E2ETests….binlog file from the Windows_Test_Templates_Logs artifacts of https://dev.azure.com/dnceng/public/_build/results?buildId=208469 (The cross-plat template tests don't seem to produce bin logs for this test group.) @ryanbrandenburg any ideas? |
@dougbu I found a way to reproduce the failures locally and I am investigating. @ryanbrandenburg @dougbu Summary of trying to get the tests to run locally: I found I could get tests to run with |
6c8d2bd
to
c938a1d
Compare
@ajcvickers I picked up the latest from 'master' as well as newer EF and AspNetCore packages in my force-push to this branch. Probably won't fix the template tests but avoids conflicts with #10736. |
That makes sense because without a new Shared Fx on your machine, the tests run using the old EF packages. @aspnet/build and @ryanbrandenburg, once the Shared Fx is built once, is it possible to point the template tests to what was built previously? |
- partially reverts 58c6772
c938a1d
to
a6d44df
Compare
🆙📅 to pull in the latest @rynowak @pranavkm @ajaybhargavb should I worry about breaking changes from Blazor or AspNetCore-Tooling ❔ |
@@ -49,7 +49,7 @@ | |||
<!-- Only listed explicitly to workaround https://github.com/dotnet/cli/issues/10528 --> | |||
<MicrosoftNETCorePlatformsPackageVersion>3.0.0-preview6.19279.8</MicrosoftNETCorePlatformsPackageVersion> | |||
<!-- Packages from aspnet/Blazor --> | |||
<MicrosoftAspNetCoreBlazorMonoPackageVersion>0.10.0-preview6.19273.9</MicrosoftAspNetCoreBlazorMonoPackageVersion> | |||
<MicrosoftAspNetCoreBlazorMonoPackageVersion>0.10.0-preview7.19303.2</MicrosoftAspNetCoreBlazorMonoPackageVersion> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is preview7 is correct here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@dougbu, by point it at what was built previously, you mean within a single machine build the SharedFx, then build/test templates without additional fiddling? If so yes, that should work. |
Getting this in because 2nd build attempt was started accidentally and first one showed only a Yarn registry failure and a known-flaky test |
Thanks for all your help on this @dougbu. Sorry it has been so painful. |
Well, we're not done yet 😈. I need to recreate this PR for preview 6 after Tooling and EF Core official builds get new bits into the right |
Okay, 🤞 then. |