Automation: main-next integrate

[msfluid-bot]

main-next integrate PR

The aim of this pull request is to sync main and next branch. If this PR is assigned to you, you need to do the following:

1. Acknowledge the pull request by adding a comment -- "Actively working on it".
2. If there are no CI failures, add the "msftbot: merge-next" label to the PR and one of the people with merge permissions will merge it in.
3. If there are CI failures, check out the main-next-0425aa1 branch and make code changes to fix the failures.

• You can ignore any failures in the Real service e2e test and Stress test pipelines. These pipelines are not required to pass to merge changes.

4. Do NOT rebase or squash the main-next-0425aa1 branch: its history must be preserved. Always amend the HEAD commit using the following git commands:

• git commit --amend -m "Automation: main-next integrate"
• git push --force-with-lease

[msfluid-bot]

⯅ @fluid-example/bundle-size-tests: +9.34 KB

Metric Name	Baseline Size	Compare Size	Size Diff
aqueduct.js	443.71 KB	443.96 KB	⯅ +261 Bytes
connectionState.js	680 Bytes	680 Bytes	■ No change
containerRuntime.js	237.04 KB	237.29 KB	⯅ +261 Bytes
loader.js	148.13 KB	148.39 KB	⯅ +261 Bytes
map.js	46.46 KB	48.43 KB	⯅ +1.98 KB
matrix.js	140.24 KB	142.21 KB	⯅ +1.98 KB
odspDriver.js	90.2 KB	90.46 KB	⯅ +261 Bytes
odspPrefetchSnapshot.js	41.87 KB	42.13 KB	⯅ +261 Bytes
sharedString.js	160.89 KB	162.86 KB	⯅ +1.98 KB
sharedTree2.js	255.73 KB	257.88 KB	⯅ +2.14 KB
Total Size	1.67 MB	1.68 MB	⯅ +9.34 KB

---

Baseline commit: 2163145

Generated by 🚫 dangerJS against 0425aa1

[andre4i]

@NicholasCouri @alexvy86 about the Perf benchmark test

[andre4i]

Performance benchmarks (Perf unit tests - runtime Run tests

The failure seems transient? However, hitting 're-run' doesn't re-run it. Closing -> Opening the PR scheduled all other test runs, except for this one. Anyone have any ideas? @tylerbutler @sonalideshpandemsft

This was assigned to me as I did the last commit, which seems unrelated to this test failure.

[github-actions]

🔗 Found some broken links! 💔

Run a link check locally to find them. See
https://github.com/microsoft/FluidFramework/wiki/Checking-for-broken-links-in-the-documentation for more information.

linkcheck output

> fluidframework-docs@0.25.0 ci:linkcheck /home/runner/work/FluidFramework/FluidFramework/docs
> start-server-and-test ci:start http://localhost:1313 linkcheck:full

1: starting server using command "npm run ci:start"
and when url "[ 'http://localhost:1313' ]" is responding with HTTP status code 200
running tests using command "npm run linkcheck:full"


> fluidframework-docs@0.25.0 ci:start
> http-server ./public --port 1313 --silent


> fluidframework-docs@0.25.0 linkcheck:full
> npm run linkcheck:fast -- --external


> fluidframework-docs@0.25.0 linkcheck:fast
> linkcheck http://localhost:1313 --skip-file skipped-urls.txt --external

Crawling...

http://localhost:1313/docs/apis/runtime-definitions/
- (1703:37) 'https://..' => https://datatracker.ietf.org/doc/html/rfc4122%29 (HTTP 404)
- (1703:37) 'https://..' => https://datatracker.ietf.org/doc/html/rfc4122%29 (HTTP 404)

http://localhost:1313/docs/apis/tree/
- (4170:210) 'https://..' => https://github.com/microsoft/FluidFramework/blob/main/packages/loader/container-utils/src/error.ts (HTTP 404)
- (4170:210) 'https://..' => https://github.com/microsoft/FluidFramework/blob/main/packages/loader/container-utils/src/error.ts (HTTP 404)

http://localhost:1313/docs/build/bundlers/
- (843:233) 'here' => https://github.com/microsoft/FluidFramework/blob/a4c38234a920abe9b54b1c26a14c0a8e430cd3fa/packages/tools/webpack-fluid-loader/webpack.config.js#L37 (HTTP 200 but missing anchor)

http://localhost:1313/docs/deployment/service-options/
- (848:72) 'Routerli..' => https://github.com/microsoft/FluidFramework/tree/main/server#readme (HTTP 200 but missing anchor)
- (850:168) 'Routerli..' => https://github.com/microsoft/FluidFramework/tree/main/server#readme (HTTP 200 but missing anchor)

http://localhost:1313/docs/faq/
- (927:87) 'Routerli..' => https://github.com/microsoft/FluidFramework/tree/main/server#readme (HTTP 200 but missing anchor)

http://localhost:1313/docs/testing/telemetry/
- (848:3) 'ILoaderP..' => https://github.com/microsoft/FluidFramework/blob/main/packages/loader/container-loader/src/loader.ts#L313 (HTTP 200 but missing anchor)


Summary of most serious issues:

http://localhost:1313/docs/apis/runtime-definitions/
- (1703:37) 'https://..' => https://datatracker.ietf.org/doc/html/rfc4122%29 (HTTP 404)
- (1703:37) 'https://..' => https://datatracker.ietf.org/doc/html/rfc4122%29 (HTTP 404)

http://localhost:1313/docs/apis/tree/
- (4170:210) 'https://..' => https://github.com/microsoft/FluidFramework/blob/main/packages/loader/container-utils/src/error.ts (HTTP 404)
- (4170:210) 'https://..' => https://github.com/microsoft/FluidFramework/blob/main/packages/loader/container-utils/src/error.ts (HTTP 404)


Stats:
  207480 links
    2021 destination URLs
       2 URLs ignored
       5 warnings
       2 errors

 ELIFECYCLE  Command failed with exit code 1.

[alexvy86]

One stage of perf benchmarks has been broken for a while, we discovered recently. It shouldn't run for PRs though. Not sure if for main-next automation, since the commit in main did get perf benchmarks run as part of its internal CI, that's why we see it here? But I would've expected many more main-next integrations to have the same symptom and I don't think they have... or we've been ignoring it? IMO it's safe to ignore that pipeline failure if it's the only one.

[sonalideshpandemsft]

closing and opening a new PR. I don't see the merge commit with the name Automation: main-next integrate on this one. weird

thanks @andre4i, @alexvy86!! not sure why the merge commit is not included in this PR.

I opened a new PR: #17549. This PR has the merge commit: 128dedd8a428372b453f2ccbcb64ce175895fb2c which was missing in this PR.