Skip to content

Test failure: Microsoft.Extensions.SecretManager.Tools.Tests.SecretManagerTests.SetSecrets #21413

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.

Sign up for GitHub

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

Jump to bottom
Closed
ajaybhargavb opened this issue May 1, 2020 · 2 comments
Closed

Test failure: Microsoft.Extensions.SecretManager.Tools.Tests.SecretManagerTests.SetSecrets #21413

ajaybhargavb opened this issue May 1, 2020 · 2 comments
Labels
affected-very-few This issue impacts very few customers area-commandlinetools Includes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPI feature-user-secrets severity-minor This label is used by an internal tool task test-failure
Milestone
7.0-preview1

Comments

@ajaybhargavb
Copy link
Contributor

https://dev.azure.com/dnceng/internal/_build/results?buildId=626845&view=ms.vss-test-web.build-test-results-tab&runId=19576184&resultId=108990&paneView=debug

Error 
Assert.Contains() Failure

Not found: No secrets configured for this application.

In value: Project file path /tmp/usersecretstest/5895c797-3631-4f05-91b9-2f2cd1566b31/TestProject.csproj.

Secrets file path /home/helixbot/.microsoft/usersecrets/53478d69-97a8-440a-8ce2-a8b0ebef4b74/secrets.json.

key1 = 1ec036ea-1f7d-42cb-9269-6265679a1afb
Stacktrace 
at Microsoft.Extensions.SecretManager.Tools.Tests.SecretManagerTests.SetSecrets(Boolean fromCurrentDirectory) in /_/src/Tools/dotnet-user-secrets/test/SecretManagerTests.cs:line 87
@ajaybhargavb ajaybhargavb added area-commandlinetools Includes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPI test-failure labels May 1, 2020
@ajaybhargavb ajaybhargavb mentioned this issue May 1, 2020
Merged
@BrennanConroy
Copy link
Member

I believe this is the same failure as #20219 which is being worked on/investigated by the runtime team

@mkArtakMSFT mkArtakMSFT added this to the Next sprint planning milestone Jul 14, 2020
@jkotalik jkotalik added affected-very-few This issue impacts very few customers severity-minor This label is used by an internal tool task labels Nov 9, 2020 — with ASP.NET Core Issue Ranking
BrennanConroy added a commit that referenced this issue Sep 29, 2021
@BrennanConroy
Un-skip SetSecrets
719a99d 
Test was skipped due to a bug in Runtime, should have been unskipped a year ago 😆 #25109
Also one of the oldest `test-failure` issues is pointing at this test #21413, I think we should close it, add the test to the normal runs again and see if it fails anymore.
@BrennanConroy BrennanConroy mentioned this issue Sep 29, 2021
Merged
@BrennanConroy
Copy link
Member

Test was skipped for non-flaky reasons and just unskipped. Letting it go to non-quarantined runs and we'll see if it's still flaky.

@ghost ghost locked as resolved and limited conversation to collaborators Nov 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
affected-very-few This issue impacts very few customers area-commandlinetools Includes: Command line tools, dotnet-dev-certs, dotnet-user-jwts, and OpenAPI feature-user-secrets severity-minor This label is used by an internal tool task test-failure
Projects
None yet
Milestone
7.0-preview1
Development

No branches or pull requests
4 participants
@ajaybhargavb @BrennanConroy @jkotalik @mkArtakMSFT