Disable richnav on PRs #54662
Disable richnav on PRs #54662
Conversation
|
@dibarbet I think it might be better to take this PR instead of #54660. RichNav team has indicated that our long run times are due to recently added features. As far as I can tell we never actually expect the task to be successful with the current timeout of 200 minutes until RichNav has the opportunity to address the perf issues. I think it would be best to just disable completely on PRs and perhaps keep an eye on it for rolling builds so that we can see if the regression gets fixed. |
I'm fine with disabling as well, can we file an issue assigned to richnav, and have them re-enable it on PRs once the regression is fixed? |
ghost
added this to the 
* upstream/main: (559 commits) Remove a few unused error codes (dotnet#54663) Use specific error message for wrong arity in async builder (dotnet#54632) Update azure-pipelines-richnav.yml (dotnet#54662) Capture file content on open instead of save (dotnet#54643) Add docs Further FAR simplifications Handle enhanced #line directive in DirectiveTriviaSyntax.DirectiveNameToken (dotnet#54636) move server name outside of loop Fix functionid Reduce telemetry output from find document in workspace Ensure we don't try and build an empty table when modifying entries with no values (dotnet#54639) Feedback Ensure we don't try and build an empty table when modifying entries with no values (dotnet#54639) No need to specialized logic for determining set of projects to search Defer group computation till reporting time Handle FAR for global suppressions in a consistent fashion Update status for enhanced `#line` directive (dotnet#54581) Split IOperationTests into one part per type [LSP] Revert semantic tokens change in main (dotnet#54570) Add exceptionutilities unreachable to catch blocks that should not be hit ...
No description provided.