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

NewlyCreatedProjectsFromDotNetNew.ValidateCSharpTemplateProjects is flakey #74157

Open
CyrusNajmabadi opened this issue Jun 25, 2024 · 2 comments
Labels
untriaged Issues and PRs which have not yet been triaged by a lead

Comments

@CyrusNajmabadi
Copy link
Member

Failed https://dev.azure.com/dnceng-public/public/_build/results?buildId=720157&view=ms.vss-test-web.build-test-results-tab&runId=18060982&resultId=100226&paneView=debug

Expected 0 items but found 17: The following compiler diagnostics are being reported for the template.
Items:
T:\RoslynTests\65921193-f413-4206-afc8-9657782aa1d4\obj\Debug\net9.0\65921193-f413-4206-afc8-9657782aa1d4.GlobalUsings.g.cs(2,32): error CS0234: The type or namespace name 'Playwright' does not exist in the namespace 'Microsoft' (are you missing an assembly reference?)
T:\RoslynTests\65921193-f413-4206-afc8-9657782aa1d4\obj\Debug\net9.0\65921193-f413-4206-afc8-9657782aa1d4.GlobalUsings.g.cs(3,22): error CS0400: The type or namespace name 'NUnit' could not be found in the global namespace (are you missing an assembly reference?)
T:\RoslynTests\65921193-f413-4206-afc8-9657782aa1d4\UnitTest1.cs(5,22): error CS0246: The type or namespace name 'PageTest' could not be found (are you missing a using directive or an assembly reference?)
T:\RoslynTests\65921193-f413-4206-afc8-9657782aa1d4\UnitTest1.cs(3,2): error CS0246: The type or namespace name 'ParallelizableAttribute' could not be found (are you missing a using directive or an assembly reference?)
T:\RoslynTests\65921193-f413-4206-afc8-9657782aa1d4\UnitTest1.cs(3,2): error CS0246: The type or namespace name 'Parallelizable' could not be found (are you missing a using directive or an assembly reference?)
T:\RoslynTests\65921193-f413-4206-afc8-9657782aa1d4\UnitTest1.cs(4,2): error CS0246: The type or namespace name 'TestFixtureAttribute' could not be found (are you missing a using directive or an assembly reference?)
T:\RoslynTests\65921193-f413-4206-afc8-9657782aa1d4\UnitTest1.cs(4,2): error CS0246: The type or namespace name 'TestFixture' could not be found (are you missing a using directive or an assembly reference?)
T:\RoslynTests\65921193-f413-4206-afc8-9657782aa1d4\UnitTest1.cs(3,17): error CS0103: The name 'ParallelScope' does not exist in the current context
T:\RoslynTests\65921193-f413-4206-afc8-9657782aa1d4\UnitTest1.cs(7,6): error CS0246: The type or namespace name 'TestAttribute' could not be found (are you missing a using directive or an assembly reference?)
T:\RoslynTests\65921193-f413-4206-afc8-9657782aa1d4\UnitTest1.cs(7,6): error CS0246: The type or namespace name 'Test' could not be found (are you missing a using directive or an assembly reference?)
T:\RoslynTests\65921193-f413-4206-afc8-9657782aa1d4\UnitTest1.cs(10,15): error CS0103: The name 'Page' does not exist in the current context
T:\RoslynTests\65921193-f413-4206-afc8-9657782aa1d4\UnitTest1.cs(13,15): error CS0103: The name 'Expect' does not exist in the current context
T:\RoslynTests\65921193-f413-4206-afc8-9657782aa1d4\UnitTest1.cs(13,22): error CS0103: The name 'Page' does not exist in the current context
T:\RoslynTests\65921193-f413-4206-afc8-9657782aa1d4\UnitTest1.cs(16,26): error CS0103: The name 'Page' does not exist in the current context
T:\RoslynTests\65921193-f413-4206-afc8-9657782aa1d4\UnitTest1.cs(19,15): error CS0103: The name 'Expect' does not exist in the current context
T:\RoslynTests\65921193-f413-4206-afc8-9657782aa1d4\UnitTest1.cs(25,15): error CS0103: The name 'Expect' does not exist in the current context
T:\RoslynTests\65921193-f413-4206-afc8-9657782aa1d4\UnitTest1.cs(25,22): error CS0103: The name 'Page' does not exist in the current context
@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged Issues and PRs which have not yet been triaged by a lead label Jun 25, 2024
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

1 similar comment
Copy link

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
untriaged Issues and PRs which have not yet been triaged by a lead
Projects
None yet
Development

No branches or pull requests

1 participant