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

The process '[...]\guardian.cmd' failed with exit code 1 #24

Closed
fepegar opened this issue Jul 8, 2022 · 2 comments
Closed

The process '[...]\guardian.cmd' failed with exit code 1 #24

fepegar opened this issue Jul 8, 2022 · 2 comments

Comments

@fepegar
Copy link

fepegar commented Jul 8, 2022

Hello,

We are getting the error below in this CI run:

Error:    Error downloading 'Microsoft.Security.CodeAnalysis.Policy.Names.1.0.2' from 'https://pkgs.dev.azure.com/secdevtools/fbe8430b-c7d4-4187-8c71-a0083ead3d4b/_packaging/a2fd5474-7706-4971-8654-fd0403cf8e6a/nuget/v3/flat2/microsoft.security.codeanalysis.policy.names/1.0.2/microsoft.security.codeanalysis.policy.names.1.0.2.nupkg'.
Error:      An error occurred while sending the request.
Error:      Unable to connect to the remote server
Error:      A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 13.107.6.175:443
  ------------------------------------------------------------------------------
Error:    PackageInstallerException: Failed to install NuGet package: Microsoft.Security.CodeAnalysis.Policy.Names vundefined
Error: Error: The process 'D:\a\_msdo\versions\microsoft.security.devops.cli\0.122.0\tools\guardian.cmd' failed with exit code 1

We recently reported #23, which we patched with microsoft/hi-ml#490. These issues might be related.

@sukhans
Copy link
Contributor

sukhans commented Mar 27, 2023

Can you please confirm if this is still an issue? There were temporary reliability concerns.

@sukhans sukhans closed this as not planned Won't fix, can't repro, duplicate, stale Mar 27, 2023
@fepegar
Copy link
Author

fepegar commented Mar 28, 2023

I haven't seen it since, I think. Thanks, @sukhans.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants