🤖 User test baselines have changed for fix37163

tests/baselines/reference/docker/azure-sdk.log

@@ -20,19 +20,19 @@ XX of XX: [@azure/event-hubs] completed successfully in ? seconds
 XX of XX: [@azure/event-processor-host] completed successfully in ? seconds
 npm ERR! code ELIFECYCLE
 npm ERR! errno 2
-npm ERR! @azure/keyvault-keys@X.X.X extract-api: `tsc -p . && api-extractor run --local`
+npm ERR! @azure/keyvault-keys@X.X.X-preview.1 extract-api: `tsc -p . && api-extractor run --local`
 npm ERR! Exit status 2
 npm ERR! 
-npm ERR! Failed at the @azure/keyvault-keys@X.X.X extract-api script.
+npm ERR! Failed at the @azure/keyvault-keys@X.X.X-preview.1 extract-api script.
 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
 npm ERR! A complete log of this run can be found in:
 npm ERR!     /root/.npm/_logs/XXXX-XX-XXXXXXXXX-debug.log
 npm ERR! code ELIFECYCLE
 npm ERR! errno 2
-npm ERR! @azure/keyvault-secrets@X.X.X extract-api: `tsc -p . && api-extractor run --local`
+npm ERR! @azure/keyvault-secrets@X.X.X-preview.1 extract-api: `tsc -p . && api-extractor run --local`
 npm ERR! Exit status 2
 npm ERR! 
-npm ERR! Failed at the @azure/keyvault-secrets@X.X.X extract-api script.
+npm ERR! Failed at the @azure/keyvault-secrets@X.X.X-preview.1 extract-api script.
 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
 npm ERR! A complete log of this run can be found in:
 npm ERR!     /root/.npm/_logs/XXXX-XX-XXXXXXXXX-debug.log
@@ -50,13 +50,14 @@ Use output.globals to specify browser global variable names corresponding to ext
 os-name (guessing 'osName')
 created dist/index.js in ?s
 XX of XX: [@azure/eventhubs-checkpointstore-blob] completed successfully in ? seconds
+XX of XX: [@azure/search] completed successfully in ? seconds
 XX of XX: [@azure/service-bus] completed successfully in ? seconds
 XX of XX: [@azure/storage-file-datalake] completed successfully in ? seconds
 XX of XX: [@azure/storage-file-share] completed successfully in ? seconds
 XX of XX: [@azure/storage-queue] completed successfully in ? seconds
 XX of XX: [@azure/template] completed successfully in ? seconds
 XX of XX: [testhub] completed successfully in ? seconds
-SUCCESS (25)
+SUCCESS (26)
 ================================
 @azure/abort-controller (? seconds)
 @azure/core-auth (? seconds)
@@ -77,6 +78,7 @@ SUCCESS (25)
 @azure/core-arm (? seconds)
 @azure/core-tracing (? seconds)
 @azure/eventhubs-checkpointstore-blob (? seconds)
+@azure/search (? seconds)
 @azure/service-bus (? seconds)
 @azure/storage-file-datalake (? seconds)
 @azure/storage-file-share (? seconds)
@@ -105,20 +107,20 @@ FAILURE (2)
 @azure/keyvault-keys ( ? seconds)
 npm ERR! code ELIFECYCLE
 npm ERR! errno 2
-npm ERR! @azure/keyvault-keys@X.X.X extract-api: `tsc -p . && api-extractor run --local`
+npm ERR! @azure/keyvault-keys@X.X.X-preview.1 extract-api: `tsc -p . && api-extractor run --local`
 npm ERR! Exit status 2
 npm ERR!
-npm ERR! Failed at the @azure/keyvault-keys@X.X.X extract-api script.
+npm ERR! Failed at the @azure/keyvault-keys@X.X.X-preview.1 extract-api script.
 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
 npm ERR! A complete log of this run can be found in:
 npm ERR!     /root/.npm/_logs/XXXX-XX-XXXXXXXXX-debug.log
 @azure/keyvault-secrets ( ? seconds)
 npm ERR! code ELIFECYCLE
 npm ERR! errno 2
-npm ERR! @azure/keyvault-secrets@X.X.X extract-api: `tsc -p . && api-extractor run --local`
+npm ERR! @azure/keyvault-secrets@X.X.X-preview.1 extract-api: `tsc -p . && api-extractor run --local`
 npm ERR! Exit status 2
 npm ERR!
-npm ERR! Failed at the @azure/keyvault-secrets@X.X.X extract-api script.
+npm ERR! Failed at the @azure/keyvault-secrets@X.X.X-preview.1 extract-api script.
 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
 npm ERR! A complete log of this run can be found in:
 npm ERR!     /root/.npm/_logs/XXXX-XX-XXXXXXXXX-debug.log

tests/baselines/reference/docker/office-ui-fabric.log

@@ -101,10 +101,10 @@ Standard output:
 @fluentui/docs: ERROR in /office-ui-fabric-react/packages/fluentui/docs/src/examples/components/Toolbar/Content/ToolbarExampleMenuRadioGroup.shorthand.tsx(35,25):
 @fluentui/docs: TS2345: Argument of type 'boolean' is not assignable to parameter of type '(prevState: undefined) => undefined'.
 @fluentui/docs: ERROR in /office-ui-fabric-react/packages/fluentui/docs/src/prototypes/VirtualizedTree/VirtualizedTree.tsx
-@fluentui/docs: ERROR in /office-ui-fabric-react/packages/fluentui/docs/src/prototypes/VirtualizedTree/VirtualizedTree.tsx(34,22):
+@fluentui/docs: ERROR in /office-ui-fabric-react/packages/fluentui/docs/src/prototypes/VirtualizedTree/VirtualizedTree.tsx(32,22):
 @fluentui/docs: TS2345: Argument of type 'number' is not assignable to parameter of type '(prevState: undefined) => undefined'.
 @fluentui/docs: ERROR in /office-ui-fabric-react/packages/fluentui/docs/src/prototypes/VirtualizedTree/VirtualizedTree.tsx
-@fluentui/docs: ERROR in /office-ui-fabric-react/packages/fluentui/docs/src/prototypes/VirtualizedTree/VirtualizedTree.tsx(64,31):
+@fluentui/docs: ERROR in /office-ui-fabric-react/packages/fluentui/docs/src/prototypes/VirtualizedTree/VirtualizedTree.tsx(62,31):
 @fluentui/docs: TS2538: Type 'undefined' cannot be used as an index type.
 @fluentui/docs: Child HtmlWebpackCompiler:
 @fluentui/docs:     Entrypoint HtmlWebpackPlugin_0 = __child-HtmlWebpackPlugin_0
@@ -126,9 +126,9 @@ info cli using local version of lerna
 @fluentui/docs:     /office-ui-fabric-react/packages/fluentui/docs/src/examples/components/Toolbar/Content/ToolbarExampleMenuRadioGroup.shorthand.tsx
 @fluentui/docs: ERROR in /office-ui-fabric-react/packages/fluentui/docs/src/examples/components/Toolbar/Content/ToolbarExampleMenuRadioGroup.shorthand.tsx(35,25):
 @fluentui/docs: TS2345: Argument of type 'boolean' is not assignable to parameter of type '(prevState: undefined) => undefined'.,/office-ui-fabric-react/packages/fluentui/docs/src/prototypes/VirtualizedTree/VirtualizedTree.tsx
-@fluentui/docs: ERROR in /office-ui-fabric-react/packages/fluentui/docs/src/prototypes/VirtualizedTree/VirtualizedTree.tsx(34,22):
+@fluentui/docs: ERROR in /office-ui-fabric-react/packages/fluentui/docs/src/prototypes/VirtualizedTree/VirtualizedTree.tsx(32,22):
 @fluentui/docs: TS2345: Argument of type 'number' is not assignable to parameter of type '(prevState: undefined) => undefined'.,/office-ui-fabric-react/packages/fluentui/docs/src/prototypes/VirtualizedTree/VirtualizedTree.tsx
-@fluentui/docs: ERROR in /office-ui-fabric-react/packages/fluentui/docs/src/prototypes/VirtualizedTree/VirtualizedTree.tsx(64,31):
+@fluentui/docs: ERROR in /office-ui-fabric-react/packages/fluentui/docs/src/prototypes/VirtualizedTree/VirtualizedTree.tsx(62,31):
 @fluentui/docs: TS2538: Type 'undefined' cannot be used as an index type.
 @fluentui/docs: Details:
 @fluentui/docs:     domainThrown: true

tests/baselines/reference/docker/vue-next.log

@@ -1,7 +1,7 @@
 Exit Code: 0
 Standard output:
 
-> @X.X.X-alpha.7 build /vue-next
+> @X.X.X-alpha.8 build /vue-next
 > node scripts/build.js "--types"
 Rolling up type definitions for compiler-core...
 Writing: /vue-next/temp/compiler-core.api.json
@@ -28,21 +28,6 @@ Writing: /vue-next/temp/reactivity.api.json
 The API report is up to date: temp/reactivity.api.md
 Writing package typings: /vue-next/packages/reactivity/dist/reactivity.d.ts
 API Extractor completed successfully.
-Rolling up type definitions for runtime-core...
-Writing: /vue-next/temp/runtime-core.api.json
-The API report is up to date: temp/runtime-core.api.md
-Writing package typings: /vue-next/packages/runtime-core/dist/runtime-core.d.ts
-API Extractor completed successfully.
-Rolling up type definitions for runtime-dom...
-Writing: /vue-next/temp/runtime-dom.api.json
-The API report is up to date: temp/runtime-dom.api.md
-Writing package typings: /vue-next/packages/runtime-dom/dist/runtime-dom.d.ts
-API Extractor completed successfully.
-Rolling up type definitions for runtime-test...
-Writing: /vue-next/temp/runtime-test.api.json
-The API report is up to date: temp/runtime-test.api.md
-Writing package typings: /vue-next/packages/runtime-test/dist/runtime-test.d.ts
-API Extractor completed successfully.
 
 
 
@@ -90,49 +75,27 @@ created packages/reactivity/dist/reactivity.global.prod.js in ?s
 /vue-next/packages/reactivity/src/index.ts → packages/reactivity/dist/reactivity.esm.prod.js...
 created packages/reactivity/dist/reactivity.esm.prod.js in ?s
 /vue-next/packages/runtime-core/src/index.ts → packages/runtime-core/dist/runtime-core.esm-bundler.js...
-created packages/runtime-core/dist/runtime-core.esm-bundler.js in ?s
-/vue-next/packages/runtime-core/src/index.ts → packages/runtime-core/dist/runtime-core.cjs.js...
-created packages/runtime-core/dist/runtime-core.cjs.js in ?s
-/vue-next/packages/runtime-core/src/index.ts → packages/runtime-core/dist/runtime-core.cjs.prod.js...
-created packages/runtime-core/dist/runtime-core.cjs.prod.js in ?s
-/vue-next/packages/runtime-dom/src/index.ts → packages/runtime-dom/dist/runtime-dom.esm-bundler.js...
-created packages/runtime-dom/dist/runtime-dom.esm-bundler.js in ?s
-/vue-next/packages/runtime-dom/src/index.ts → packages/runtime-dom/dist/runtime-dom.cjs.js...
-created packages/runtime-dom/dist/runtime-dom.cjs.js in ?s
-/vue-next/packages/runtime-dom/src/index.ts → packages/runtime-dom/dist/runtime-dom.global.js...
-created packages/runtime-dom/dist/runtime-dom.global.js in ?s
-/vue-next/packages/runtime-dom/src/index.ts → packages/runtime-dom/dist/runtime-dom.esm.js...
-created packages/runtime-dom/dist/runtime-dom.esm.js in ?s
-/vue-next/packages/runtime-dom/src/index.ts → packages/runtime-dom/dist/runtime-dom.cjs.prod.js...
-created packages/runtime-dom/dist/runtime-dom.cjs.prod.js in ?s
-/vue-next/packages/runtime-dom/src/index.ts → packages/runtime-dom/dist/runtime-dom.global.prod.js...
-created packages/runtime-dom/dist/runtime-dom.global.prod.js in ?s
-/vue-next/packages/runtime-dom/src/index.ts → packages/runtime-dom/dist/runtime-dom.esm.prod.js...
-created packages/runtime-dom/dist/runtime-dom.esm.prod.js in ?s
-/vue-next/packages/runtime-test/src/index.ts → packages/runtime-test/dist/runtime-test.global.js...
-created packages/runtime-test/dist/runtime-test.global.js in ?s
-/vue-next/packages/runtime-test/src/index.ts → packages/runtime-test/dist/runtime-test.global.prod.js...
-created packages/runtime-test/dist/runtime-test.global.prod.js in ?s
-/vue-next/packages/server-renderer/src/index.ts → packages/server-renderer/dist/server-renderer.cjs.js...
-[!] (plugin rpt2) Error: /vue-next/packages/vue/src/devCheck.ts(2,11): semantic error TS2774: This condition will always return true since the function is always defined. Did you mean to call it instead?
-packages/vue/src/devCheck.ts
-Error: /vue-next/packages/vue/src/devCheck.ts(2,11): semantic error TS2774: This condition will always return true since the function is always defined. Did you mean to call it instead?
+[!] (plugin rpt2) Error: /vue-next/packages/runtime-core/src/apiOptions.ts(137,18): semantic error TS2344: Type 'Function & T[key]["get"]' does not satisfy the constraint '(...args: any) => any'.
+  Type 'Function' provides no match for the signature '(...args: any): any'.
+packages/runtime-core/src/apiOptions.ts
+Error: /vue-next/packages/runtime-core/src/apiOptions.ts(137,18): semantic error TS2344: Type 'Function & T[key]["get"]' does not satisfy the constraint '(...args: any) => any'.
+  Type 'Function' provides no match for the signature '(...args: any): any'.
     at error (/vue-next/node_modules/rollup/dist/shared/node-entry.js:5400:30)
-    at throwPluginError (/vue-next/node_modules/rollup/dist/shared/node-entry.js:11874:12)
-    at Object.error (/vue-next/node_modules/rollup/dist/shared/node-entry.js:12908:24)
-    at Object.error (/vue-next/node_modules/rollup/dist/shared/node-entry.js:12077:38)
+    at throwPluginError (/vue-next/node_modules/rollup/dist/shared/node-entry.js:11878:12)
+    at Object.error (/vue-next/node_modules/rollup/dist/shared/node-entry.js:12912:24)
+    at Object.error (/vue-next/node_modules/rollup/dist/shared/node-entry.js:12081:38)
     at RollupContext.error (/vue-next/node_modules/rollup-plugin-typescript2/src/rollupcontext.ts:37:18)
     at /vue-next/node_modules/rollup-plugin-typescript2/src/print-diagnostics.ts:41:11
     at arrayEach (/vue-next/node_modules/rollup-plugin-typescript2/node_modules/lodash/lodash.js:516:11)
     at forEach (/vue-next/node_modules/rollup-plugin-typescript2/node_modules/lodash/lodash.js:9342:14)
     at _.each (/vue-next/node_modules/rollup-plugin-typescript2/src/print-diagnostics.ts:9:2)
     at Object.transform (/vue-next/node_modules/rollup-plugin-typescript2/src/index.ts:234:5)
-(node:18) UnhandledPromiseRejectionWarning: Error: Command failed with exit code 1 (EPERM): rollup -c --environment COMMIT:e6ef52c,NODE_ENV:production,TARGET:server-renderer,TYPES:true
+(node:17) UnhandledPromiseRejectionWarning: Error: Command failed with exit code 1 (EPERM): rollup -c --environment COMMIT:ca5f39e,NODE_ENV:production,TARGET:runtime-core,TYPES:true
     at makeError (/vue-next/node_modules/execa/lib/error.js:59:11)
     at handlePromise (/vue-next/node_modules/execa/index.js:112:26)
     at processTicksAndRejections (internal/process/task_queues.js:97:5)
     at async build (/vue-next/scripts/build.js:72:3)
     at async buildAll (/vue-next/scripts/build.js:51:5)
     at async run (/vue-next/scripts/build.js:41:5)
-(node:18) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
-(node:18) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
+(node:17) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
+(node:17) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.