Skip to content
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

[Not for merging] Repro of integration test failure #30147

Closed
wants to merge 1 commit into from

Conversation

Neme12
Copy link
Contributor

@Neme12 Neme12 commented Sep 26, 2018

For demonstration purposes only (do not merge)

This is a minimum repro to show the integration test failures encountered in #25875 (comment)

@sharwell Can you please take a quick look at this very small repro to see if there's anything I'm doing wrong? If I run both tests in the Example class this error dialog appears:
integrationtesterror

Test1 and Test2 are identical. Running only one of them does not reproduce this. Changing WellKnownProjectTemplates.CSharpNetCoreClassLibrary to WellKnownProjectTemplates.ClassLibrary fixes the error.

@Neme12
Copy link
Contributor Author

Neme12 commented Sep 26, 2018

@jasonmalinowski Can you please take a look?

@jasonmalinowski
Copy link
Member

@davkean or @Pilchie do you recognize this or would know where to route?

@Neme12
Copy link
Contributor Author

Neme12 commented Sep 27, 2018

It's possible that if this was fixed, a lot of other tests that are currently skipped could be enabled again. When I was browsing through the integration tests to find usages of CSharpNetCoreClassLibrary (to see if the problem is on my side), the majority of tests I found were disabled.

@Neme12 Neme12 changed the title [Not for review] Repro of integration test failure [Not for merging] Repro of integration test failure Oct 4, 2018
@Neme12
Copy link
Contributor Author

Neme12 commented Oct 4, 2018

@jinujoseph Could this please get a buddy? This PR is not for merging but I would appreciate if somebody could take a look at this or at least tell me what the best path forward is, because this is blocking my other PR (#25875). Should I just skip the tests and file an issue? Is it OK to merge skipped tests in a PR?

I don't think this should be hard to investigate (for the right person) because there's a really small repro and the issue repros consistently, even locally. And as I sad earlier it's also possible this issue is affecting other currently skipped tests (because the repro is very small), so it might be worthwhile trying to find where the issue is because it could potentially allow us to unskip other tests.

@jinujoseph jinujoseph added Area-Infrastructure Community The pull request was submitted by a contributor who is not a Microsoft employee. labels Oct 4, 2018
@jinujoseph jinujoseph added this to the 16.0 milestone Oct 4, 2018
@sharwell
Copy link
Member

sharwell commented Oct 7, 2018

@Pilchie @davkean Do you know what the original bug here is? It's the same bug I encountered in my work on the new test harness, resulting in a rather elaborate (and very expensive) workaround in 6c73dfa and 9ec79b4.

@Pilchie
Copy link
Member

Pilchie commented Oct 8, 2018

This is a core CPS issue. Can someone include the file mentioned in the dialog box? @lifengl can you help route?

@Neme12
Copy link
Contributor Author

Neme12 commented Oct 8, 2018

@Pilchie @lifengl Here is the file from two different runs (they do seem to be a little different)

VsProjectFault_25556e03-5a24-4658-a745-4f0ca14160a8.failure.txt
VsProjectFault_e752c0d1-4b75-4ed4-9400-5a45a019f510.failure.txt

@Neme12
Copy link
Contributor Author

Neme12 commented Oct 8, 2018

Note: This error would be harder to find in CI because both of these tests actually pass. The error dialog appears after the second test is started, and the second test finishes running successfully while the dialog is displayed. But then the dialog prevents the creation of a new project, so the failure would actually show up in a third (potentially completely unrelated) test.

@Neme12
Copy link
Contributor Author

Neme12 commented Oct 11, 2018

retest windows_release_vs-integration_prtest please

@Neme12
Copy link
Contributor Author

Neme12 commented Oct 12, 2018

retest windows_debug_vs-integration_prtest please

@Neme12
Copy link
Contributor Author

Neme12 commented Oct 12, 2018

Hm, the tests are passing in CI. It seems like I'm only getting the dialog locally. Should I close this then?

@lifengl
Copy link

lifengl commented Oct 12, 2018 via email

@Neme12
Copy link
Contributor Author

Neme12 commented Oct 12, 2018

@lifengl I'm using 15.9 Preview 3.

@Neme12
Copy link
Contributor Author

Neme12 commented Oct 12, 2018

This now passed but my original PR still keeps failing in CI, I don't know what's going on... 😕 maybe it's because there's more than 2 tests?

@Neme12
Copy link
Contributor Author

Neme12 commented Oct 12, 2018

Just to be clear, it's still failing for me locally, it's just that I that noticed CI passed here.

@Neme12
Copy link
Contributor Author

Neme12 commented Dec 8, 2018

@lifengl I'm still encountering this in 16.0 preview1. Is there an existing issue or something I can point to as a reason for skipping the tests? Thanks.

@jinujoseph jinujoseph added the PR For Personal Review Only The PR doesn’t require anyone other than the developer to review it. label Dec 10, 2018
@Neme12
Copy link
Contributor Author

Neme12 commented Jan 16, 2019

➡️ Workaround for this was added in 675adf0 (PR #32122)

@Neme12 Neme12 closed this Jan 16, 2019
@Neme12 Neme12 deleted the testFailure branch January 16, 2019 20:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Infrastructure Community The pull request was submitted by a contributor who is not a Microsoft employee. PR For Personal Review Only The PR doesn’t require anyone other than the developer to review it.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants