Automation: Main Next Integrate

[github-actions]

Main-next integrate PR

The aim of this pull request is to sync main and next branch. The expectation from the assignee is as follows:

• Acknowledge the pull request by adding a comment -- "Actively working on it".
• Resolve any merge conflicts between this branch and next (and push the resolution to this branch). Merge next into this branch if needed. Do NOT rebase or squash this branch: its history must be preserved.
• Ensure CI is passing for this PR, fixing any issues. Please don't look into resolving Real service e2e test and Stress test failures as they are non-required CI failures.
• Once the PR is ready for merge, please add a comment @mentioning the reviewers to get this PR merged in. Thank you!!

For more information about how to resolve merge conflicts and CI failures, visit [this wiki page]
(https://github.com/microsoft/FluidFramework/wiki/Main-next-Automation).

[msfluid-bot]

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

Metric Name	Baseline Size	Compare Size	Size Diff
aqueduct.js	392.45 KB	394.09 KB	⯅ +1.64 KB
connectionState.js	680 Bytes	680 Bytes	■ No change
containerRuntime.js	191.92 KB	197.48 KB	⯅ +5.55 KB
loader.js	151.12 KB	151.06 KB	⯆ -57 Bytes
map.js	42.63 KB	47.38 KB	⯅ +4.75 KB
matrix.js	131.63 KB	134.3 KB	⯅ +2.67 KB
odspDriver.js	150.23 KB	150.11 KB	⯆ -127 Bytes
odspPrefetchSnapshot.js	38.39 KB	38.35 KB	⯆ -41 Bytes
sharedString.js	152.42 KB	153.54 KB	⯅ +1.12 KB
Total Size	1.25 MB	1.27 MB	⯅ +15.52 KB

---

Baseline commit: 99e4847

Generated by 🚫 dangerJS against 792e826

[alexvy86]

/azp run Build - client packages

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[alexvy86]

I suspect the pipeline failures are transient, or related to issues that should have been addressed now, so waiting to see if the manual run of Build - client packages (and the tests that trigger from that) passes.

[sonalivdeshpande]

thanks @alexvy86!!

[alexvy86]

@sonalivdeshpande quick follow up, the pipeline runs for the main branch seem a bit flaky right now, I again got an error, and the root problem seems to be some issue when running the real service tests targeting t9s, during the step to produce a code-coverage report:

lerna info Executing command in 2 packages: "npm run test:realsvc:report"
@***framework/test-end-to-end-tests: npm ERR! code ELIFECYCLE
@***framework/test-end-to-end-tests: npm ERR! errno 2
@***framework/test-end-to-end-tests: npm ERR! @***framework/test-end-to-end-tests@2.0.0-internal.1.1.0.87393 test:realsvc:run: `mocha dist/test --config src/test/.mocharc.js "--driver=t9s" "--timeout=5s"`
@***framework/test-end-to-end-tests: npm ERR! Exit status 2
@***framework/test-end-to-end-tests: npm ERR! 
@***framework/test-end-to-end-tests: npm ERR! Failed at the @***framework/test-end-to-end-tests@2.0.0-internal.1.1.0.87393 test:realsvc:run script.
@***framework/test-end-to-end-tests: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
@***framework/test-end-to-end-tests: npm ERR! A complete log of this run can be found in:
@***framework/test-end-to-end-tests: npm ERR!     /home/cloudtest/.npm/_logs/2022-08-23T17_15_27_770Z-debug.log
@***framework/test-end-to-end-tests: npm ERR! code ELIFECYCLE
@***framework/test-end-to-end-tests: npm ERR! errno 2
@***framework/test-end-to-end-tests: npm ERR! @***framework/test-end-to-end-tests@2.0.0-internal.1.1.0.87393 test:realsvc:tinylicious:run: `npm run test:realsvc:run -- --driver=t9s --timeout=5s`
@***framework/test-end-to-end-tests: npm ERR! Exit status 2
@***framework/test-end-to-end-tests: npm ERR! 
@***framework/test-end-to-end-tests: npm ERR! Failed at the @***framework/test-end-to-end-tests@2.0.0-internal.1.1.0.87393 test:realsvc:tinylicious:run script.
@***framework/test-end-to-end-tests: npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
@***framework/test-end-to-end-tests: npm ERR! A complete log of this run can be found in:
@***framework/test-end-to-end-tests: npm ERR!     /home/cloudtest/.npm/_logs/2022-08-23T17_15_27_815Z-debug.log
@***framework/test-end-to-end-tests: Error: Command failed with exit code 2: npm run test:realsvc:tinylicious:run
@***framework/test-end-to-end-tests:     at makeError (/mnt/vss/_work/1/s/node_modules/start-server-and-test/node_modules/execa/lib/error.js:60:11)
@***framework/test-end-to-end-tests:     at handlePromise (/mnt/vss/_work/1/s/node_modules/start-server-and-test/node_modules/execa/index.js:118:26)
@***framework/test-end-to-end-tests:     at processTicksAndRejections (internal/process/task_queues.js:95:5) {
@***framework/test-end-to-end-tests:   shortMessage: 'Command failed with exit code 2: npm run test:realsvc:tinylicious:run',
@***framework/test-end-to-end-tests:   command: 'npm run test:realsvc:tinylicious:run',
@***framework/test-end-to-end-tests:   escapedCommand: '"npm run test:realsvc:tinylicious:run"',
@***framework/test-end-to-end-tests:   exitCode: 2,
@***framework/test-end-to-end-tests:   signal: undefined,
@***framework/test-end-to-end-tests:   signalDescription: undefined,
@***framework/test-end-to-end-tests:   stdout: undefined,

Let's see what the CI build for next does now that this is merged.