Skip to content

[PERF] Disable PerfBDN tests. #112886

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

Merged
merged 2 commits into from
Feb 25, 2025

Conversation

LoopedBard3
Copy link
Member

Disabled PerfBDN related code as it is currently causing our pipeline to fail. Reenabling tracked: dotnet/performance#4729. Test run: https://dev.azure.com/dnceng/internal/_build/results?buildId=2649692&view=logs&j=6216695f-bbcb-51b4-e9b9-a690f297b942.

To be merged at the same time as: dotnet/performance#4730

@LoopedBard3 LoopedBard3 added area-Infrastructure perf-pipeline Issues with dotnet-runtime-perf, or runtime-wasm-perf pipelines labels Feb 24, 2025
@LoopedBard3 LoopedBard3 self-assigned this Feb 24, 2025
@Copilot Copilot AI review requested due to automatic review settings February 24, 2025 23:51
Copy link
Contributor

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

Copy link
Contributor

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

@LoopedBard3
Copy link
Member Author

Manually triggered rerun of the runtime-wasm-perf pipelines was successful: https://dev.azure.com/dnceng-public/public/_build/results?buildId=961994&view=results. We had to revert a commit in the performance repo as the downloaded sdk was not new enough for the recently updated global.json in the perf repo: dotnet/performance#4719.

@LoopedBard3
Copy link
Member Author

/azp run

Copy link

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.

@LoopedBard3
Copy link
Member Author

/azp run runtime-wasm-perf

@LoopedBard3
Copy link
Member Author

Re-run is not triggering and the manual rerun referenced above had runtime-wasm-perf succeed so going to go ahead and merge.

@LoopedBard3 LoopedBard3 merged commit c7a2924 into dotnet:main Feb 25, 2025
18 of 23 checks passed
@LoopedBard3 LoopedBard3 deleted the PerfDisablePerfBDNTestingRuntime branch February 25, 2025 19:20
@github-actions github-actions bot locked and limited conversation to collaborators Mar 28, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-Infrastructure perf-pipeline Issues with dotnet-runtime-perf, or runtime-wasm-perf pipelines
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants