-
Notifications
You must be signed in to change notification settings - Fork 13.1k
🤖 User test baselines have changed for update-dom-2019-07-10 #32336
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
Closed
typescript-bot
wants to merge
1
commit into
microsoft:update-dom-2019-07-10
from
typescript-bot:user-update-microsoft-20190603-update-dom-2019-07-10
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -13,7 +13,7 @@ npm ERR! | |
| npm ERR! Failed at the @azure/[email protected] compile 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/2019-07-10T13_39_33_862Z-debug.log | ||
| npm ERR! /root/.npm/_logs/2019-07-10T20_59_41_442Z-debug.log | ||
| [@azure/service-bus] started | ||
| [@azure/storage-blob] started | ||
| XX of XX: [@azure/storage-blob] completed successfully in ? seconds | ||
|
|
@@ -32,106 +32,89 @@ XX of XX: [@azure/core-asynciterator-polyfill] completed successfully in ? secon | |
| [@azure/core-auth] started | ||
| XX of XX: [@azure/core-auth] completed successfully in ? seconds | ||
| [@azure/core-http] started | ||
| XX of XX: [@azure/core-http] completed successfully in ? seconds | ||
| [@azure/core-arm] started | ||
| XX of XX: [@azure/core-arm] completed successfully in ? seconds | ||
| [@azure/core-paging] started | ||
| XX of XX: [@azure/core-paging] completed successfully in ? seconds | ||
| [@azure/event-processor-host] started | ||
| XX of XX: [@azure/event-processor-host] completed successfully in ? seconds | ||
| [testhub] started | ||
| XX of XX: [testhub] completed successfully in ? seconds | ||
| [@azure/identity] started | ||
| XX of XX: [@azure/identity] completed successfully in ? seconds | ||
| [@azure/keyvault-certificates] started | ||
| [@azure/keyvault-keys] started | ||
| npm ERR! code ELIFECYCLE | ||
| npm ERR! errno 2 | ||
| npm ERR! @azure/keyvault-keys@X.X.X-preview.2 extract-api: `tsc -p . && api-extractor run --local` | ||
| npm ERR! @azure/core-http@X.X.X-preview.1 build:tsc: `tsc -p tsconfig.es.json` | ||
| npm ERR! Exit status 2 | ||
| npm ERR! | ||
| npm ERR! Failed at the @azure/keyvault-keys@X.X.X-preview.2 extract-api script. | ||
| npm ERR! Failed at the @azure/core-http@X.X.X-preview.1 build:tsc 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/2019-07-10T13_41_42_464Z-debug.log | ||
| [@azure/keyvault-secrets] started | ||
| npm ERR! /root/.npm/_logs/2019-07-10T21_01_01_429Z-debug.log | ||
| ERROR: "build:tsc" exited with 2. | ||
| npm ERR! code ELIFECYCLE | ||
| npm ERR! errno 2 | ||
| npm ERR! @azure/keyvault-secrets@X.X.X-preview.2 extract-api: `tsc -p . && api-extractor run --local` | ||
| npm ERR! Exit status 2 | ||
| npm ERR! errno 1 | ||
| npm ERR! @azure/core-http@X.X.X-preview.1 build:lib: `run-s build:tsc build:rollup build:minify-browser` | ||
| npm ERR! Exit status 1 | ||
| npm ERR! | ||
| npm ERR! Failed at the @azure/keyvault-secrets@X.X.X-preview.2 extract-api script. | ||
| npm ERR! Failed at the @azure/core-http@X.X.X-preview.1 build:lib 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/2019-07-10T13_41_46_371Z-debug.log | ||
| [@azure/core-amqp] started | ||
| SUCCESS (14) | ||
| npm ERR! /root/.npm/_logs/2019-07-10T21_01_01_483Z-debug.log | ||
| ERROR: "build:lib" exited with 1. | ||
| [@azure/core-paging] started | ||
| XX of XX: [@azure/core-paging] completed successfully in ? seconds | ||
| [@azure/event-processor-host] started | ||
| XX of XX: [@azure/event-processor-host] completed successfully in ? seconds | ||
| [testhub] started | ||
| XX of XX: [testhub] completed successfully in ? seconds | ||
| SUCCESS (11) | ||
| ================================ | ||
| @azure/abort-controller (? seconds) | ||
| @azure/core-arm (? seconds) | ||
| @azure/core-asynciterator-polyfill (? seconds) | ||
| @azure/core-auth (? seconds) | ||
| @azure/core-http (? seconds) | ||
| @azure/core-paging (? seconds) | ||
| @azure/event-processor-host (? seconds) | ||
| @azure/identity (? seconds) | ||
| @azure/storage-blob (? seconds) | ||
| @azure/storage-datalake (? seconds) | ||
| @azure/storage-file (? seconds) | ||
| @azure/storage-queue (? seconds) | ||
| @azure/template (? seconds) | ||
| testhub (? seconds) | ||
| ================================ | ||
| BLOCKED (1) | ||
| BLOCKED (7) | ||
| ================================ | ||
| @azure/core-amqp | ||
| @azure/core-arm | ||
| @azure/event-hubs | ||
| @azure/identity | ||
| @azure/keyvault-certificates | ||
| @azure/keyvault-keys | ||
| @azure/keyvault-secrets | ||
| ================================ | ||
| FAILURE (6) | ||
| FAILURE (3) | ||
| ================================ | ||
| @azure/core-amqp (? seconds) | ||
| >>> @azure/core-amqp | ||
| tsc -p . && rollup -c 2>&1 | ||
| src/errors.ts(586,20): error TS7053: Element implicitly has an 'any' type because expression of type 'any' can't be used to index type 'typeof ConditionErrorNameMapper'. | ||
| src/errors.ts(607,34): error TS7053: Element implicitly has an 'any' type because expression of type 'any' can't be used to index type 'typeof SystemErrorConditionMapper'. | ||
| src/errors.ts(608,20): error TS7053: Element implicitly has an 'any' type because expression of type 'any' can't be used to index type 'typeof ConditionErrorNameMapper'. | ||
| @azure/cosmos ( ? seconds) | ||
| @azure/core-http (? seconds) | ||
| npm ERR! code ELIFECYCLE | ||
| npm ERR! errno 2 | ||
| npm ERR! @azure/cosmos@X.X.X compile: `echo Using TypeScript && tsc --version && tsc -p tsconfig.prod.json --pretty` | ||
| npm ERR! @azure/core-http@X.X.X-preview.1 build:tsc: `tsc -p tsconfig.es.json` | ||
| npm ERR! Exit status 2 | ||
| npm ERR! | ||
| npm ERR! Failed at the @azure/cosmos@X.X.X compile script. | ||
| npm ERR! Failed at the @azure/core-http@X.X.X-preview.1 build:tsc 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/2019-07-10T13_39_33_862Z-debug.log | ||
| @azure/keyvault-certificates (? seconds) | ||
| >>> @azure/keyvault-certificates | ||
| tsc && rollup -c rollup.config.js 2>&1 | ||
| error TS2318: Cannot find global type 'AsyncGenerator'. | ||
| src/index.ts(154,60): error TS2739: Type '{}' is missing the following properties from type 'AsyncIterableIterator<CertificateAttributes>': [Symbol.asyncIterator], next | ||
| src/index.ts(180,128): error TS2322: Type '{}' is not assignable to type 'AsyncIterableIterator<CertificateAttributes>'. | ||
| src/index.ts(232,101): error TS2739: Type '{}' is missing the following properties from type 'AsyncIterableIterator<CertificateIssuer>': [Symbol.asyncIterator], next | ||
| src/index.ts(381,103): error TS2739: Type '{}' is missing the following properties from type 'AsyncIterableIterator<DeletedCertificate>': [Symbol.asyncIterator], next | ||
| @azure/keyvault-keys (? seconds) | ||
| npm ERR! /root/.npm/_logs/2019-07-10T21_01_01_429Z-debug.log | ||
| ERROR: "build:tsc" exited with 2. | ||
| npm ERR! code ELIFECYCLE | ||
| npm ERR! errno 2 | ||
| npm ERR! @azure/keyvault-keys@X.X.X-preview.2 extract-api: `tsc -p . && api-extractor run --local` | ||
| npm ERR! Exit status 2 | ||
| npm ERR! errno 1 | ||
| npm ERR! @azure/core-http@X.X.X-preview.1 build:lib: `run-s build:tsc build:rollup build:minify-browser` | ||
| npm ERR! Exit status 1 | ||
| npm ERR! | ||
| npm ERR! Failed at the @azure/keyvault-keys@X.X.X-preview.2 extract-api script. | ||
| npm ERR! Failed at the @azure/core-http@X.X.X-preview.1 build:lib 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/2019-07-10T13_41_42_464Z-debug.log | ||
| @azure/keyvault-secrets (? seconds) | ||
| npm ERR! /root/.npm/_logs/2019-07-10T21_01_01_483Z-debug.log | ||
| ERROR: "build:lib" exited with 1. | ||
| @azure/cosmos ( ? seconds) | ||
| npm ERR! code ELIFECYCLE | ||
| npm ERR! errno 2 | ||
| npm ERR! @azure/keyvault-secrets@X.X.X-preview.2 extract-api: `tsc -p . && api-extractor run --local` | ||
| npm ERR! @azure/cosmos@X.X.X compile: `echo Using TypeScript && tsc --version && tsc -p tsconfig.prod.json --pretty` | ||
| npm ERR! Exit status 2 | ||
| npm ERR! | ||
| npm ERR! Failed at the @azure/keyvault-secrets@X.X.X-preview.2 extract-api script. | ||
| npm ERR! Failed at the @azure/cosmos@X.X.X compile 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/2019-07-10T13_41_46_371Z-debug.log | ||
| npm ERR! /root/.npm/_logs/2019-07-10T20_59_41_442Z-debug.log | ||
| @azure/service-bus ( ? seconds) | ||
| >>> @azure/service-bus | ||
| tsc -p . && rollup -c 2>&1 && npm run extract-api | ||
|
|
@@ -148,14 +131,14 @@ Standard error: | |
| Your version of Node.js (X.X.X) has not been tested with this release of Rush. The Rush team will not accept issue reports for it. Please consider upgrading Rush or downgrading Node.js. | ||
| XX of XX: [@azure/cosmos] failed to build! | ||
| XX of XX: [@azure/service-bus] failed to build! | ||
| XX of XX: [@azure/keyvault-certificates] failed to build! | ||
| XX of XX: [@azure/keyvault-keys] failed to build! | ||
| XX of XX: [@azure/keyvault-secrets] failed to build! | ||
| XX of XX: [@azure/core-amqp] failed to build! | ||
| XX of XX: [@azure/event-hubs] blocked by [@azure/core-amqp]! | ||
| [@azure/core-amqp] Returned error code: 2 | ||
| XX of XX: [@azure/core-http] failed to build! | ||
| XX of XX: [@azure/core-arm] blocked by [@azure/core-http]! | ||
| XX of XX: [@azure/identity] blocked by [@azure/core-http]! | ||
| XX of XX: [@azure/core-amqp] blocked by [@azure/core-http]! | ||
| XX of XX: [@azure/event-hubs] blocked by [@azure/core-http]! | ||
| XX of XX: [@azure/keyvault-certificates] blocked by [@azure/core-http]! | ||
| XX of XX: [@azure/keyvault-keys] blocked by [@azure/core-http]! | ||
| XX of XX: [@azure/keyvault-secrets] blocked by [@azure/core-http]! | ||
| [@azure/core-http] Returned error code: 1 | ||
| [@azure/cosmos] Returned error code: 2 | ||
| [@azure/keyvault-certificates] Returned error code: 2 | ||
| [@azure/keyvault-keys] Returned error code: 2 | ||
| [@azure/keyvault-secrets] Returned error code: 2 | ||
| [@azure/service-bus] Returned error code: 2 | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh boy timestamps - another kind that needs to be purged from the log~