runtime: Failed to Install microsoft.dotnet.xharness.cli on Ubuntu.1804.Amd64.Open

2021-02-04T23:33:27.6778889Z   Using Timeout: 00:30:00
2021-02-04T23:33:27.7099543Z   Done building Helix work items for scenario wasmtestonbrowser. Work item count: 214
2021-02-04T23:33:32.6833318Z   You can invoke the tool using the following command: xharness
2021-02-04T23:33:32.6834851Z   Tool 'microsoft.dotnet.xharness.cli' (version '1.0.0-prerelease.21103.1') was successfully installed.
2021-02-04T23:33:33.1576352Z   Sending Job to Ubuntu.1804.Amd64.Open...
2021-02-04T23:33:34.0405009Z   Tool 'microsoft.dotnet.xharness.cli' (version '1.0.0-prerelease.21103.1') is already installed.
2021-02-04T23:33:34.0406291Z   Tool 'microsoft.dotnet.xharness.cli' failed to install. This failure may have been caused by:
2021-02-04T23:33:34.0406944Z   
2021-02-04T23:33:34.0407664Z   * You are attempting to install a preview release and did not use the --version option to specify the version.
2021-02-04T23:33:34.0408283Z   * A package by this name was found, but it was not a .NET tool.
2021-02-04T23:33:34.0408865Z   * The required NuGet feed cannot be accessed, perhaps because of an Internet connection problem.
2021-02-04T23:33:34.0409386Z   * You mistyped the name of the tool.
2021-02-04T23:33:34.0409752Z   
2021-02-04T23:33:34.0410455Z   For more reasons, including package naming enforcement, visit https://aka.ms/failure-installing-tool
2021-02-04T23:33:34.1189953Z   Sending Job to Ubuntu.1804.Amd64.Open...

log https://dev.azure.com/dnceng/9ee6d478-d288-47f7-aacc-f6e6d082ae6d/_apis/build/builds/979753/logs/1920 build https://dev.azure.com/dnceng/public/_build/results?buildId=979753&view=results

This has failed a couple of times now

cc @dotnet/runtime-infrastructure @dotnet/dnceng

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 15 (14 by maintainers)

Most upvoted comments

Maybe the improvement here is for the Helix.SDK to check if the tool (with the version it needs) is already installed just package it up as part of the payload and don’t try to install it again.

Agreed, I’ll open up an Arcade issue. I think this was just a simple oversight because when being developed we weren’t sending multiple parallel Xharness runs with the same effective flavor.