-
Notifications
You must be signed in to change notification settings - Fork 12.9k
🤖 User test baselines have changed for refs/heads/release-3.8 #36815
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
sandersn
merged 1 commit into
microsoft:release-3.8
from
typescript-bot:user-update-Microsoft-20200106-refs/heads/release-3.8
Feb 19, 2020
Merged
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 |
|---|---|---|
|
|
@@ -2,7 +2,7 @@ Exit Code: 1 | |
| Standard output: | ||
|
|
||
| Rush Multi-Project Build Tool 5.X.X - https://rushjs.io | ||
| Node.js version is 12.15.0 (LTS) | ||
| Node.js version is 12.16.0 (LTS) | ||
| Starting "rush rebuild" | ||
| Executing a maximum of ?simultaneous processes... | ||
| XX of XX: [@azure/abort-controller] completed successfully in ? seconds | ||
|
|
@@ -41,13 +41,12 @@ npm ERR! Failed at the @azure/[email protected] 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 | ||
| Warning: You have changed the public API signature for this project. Updating review/service-bus.api.md | ||
| npm ERR! code ELIFECYCLE | ||
| npm ERR! errno 2 | ||
| npm ERR! @azure/[email protected].8 build:es6: `tsc -p tsconfig.json` | ||
| npm ERR! @azure/[email protected].9 build:es6: `tsc -p tsconfig.json && npm run build:types` | ||
| npm ERR! Exit status 2 | ||
| npm ERR! | ||
| npm ERR! Failed at the @azure/[email protected].8 build:es?script. | ||
| npm ERR! Failed at the @azure/[email protected].9 build:es?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 | ||
|
|
@@ -75,7 +74,7 @@ SUCCESS (17) | |
| @azure/template (? seconds) | ||
| testhub (? seconds) | ||
| ================================ | ||
| SUCCESS WITH WARNINGS (7) | ||
| SUCCESS WITH WARNINGS (6) | ||
| ================================ | ||
| @azure/event-hubs (? seconds) | ||
| Warning: You have changed the public API signature for this project. Updating review/event-hubs.api.md | ||
|
|
@@ -93,14 +92,12 @@ os-name (imported by dist-esm/utils/user-agent.js) | |
| Use output.globals to specify browser global variable names corresponding to external modules | ||
| os-name (guessing 'osName') | ||
| created dist/index.js in ?s | ||
| @azure/service-bus (? seconds) | ||
| Warning: You have changed the public API signature for this project. Updating review/service-bus.api.md | ||
| @azure/storage-file-share (? seconds) | ||
| Warning: You have changed the public API signature for this project. Updating review/storage-file-share.api.md | ||
| @azure/storage-queue (? seconds) | ||
| Warning: You have changed the public API signature for this project. Updating review/storage-queue.api.md | ||
| ================================ | ||
| FAILURE (4) | ||
| FAILURE (5) | ||
| ================================ | ||
| @azure/app-configuration ( ? seconds) | ||
| >>> @azure/app-configuration | ||
|
|
@@ -147,13 +144,22 @@ npm ERR! Failed at the @azure/[email protected] 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/service-bus (? seconds) | ||
| >>> @azure/service-bus | ||
| tsc -p . && rollup -c 2>&1 && npm run extract-api | ||
| src/serviceBusClient.ts(90,34): error TS1109: Expression expected. | ||
| src/serviceBusClient.ts(90,52): error TS1109: Expression expected. | ||
| src/serviceBusClient.ts(90,62): error TS1005: ':' expected. | ||
| src/serviceBusClient.ts(92,52): error TS1109: Expression expected. | ||
| src/serviceBusClient.ts(92,70): error TS1109: Expression expected. | ||
| src/serviceBusClient.ts(92,98): error TS1005: ':' expected. | ||
| @azure/storage-file-datalake (? seconds) | ||
| npm ERR! code ELIFECYCLE | ||
| npm ERR! errno 2 | ||
| npm ERR! @azure/[email protected].8 build:es6: `tsc -p tsconfig.json` | ||
| npm ERR! @azure/[email protected].9 build:es6: `tsc -p tsconfig.json && npm run build:types` | ||
| npm ERR! Exit status 2 | ||
| npm ERR! | ||
| npm ERR! Failed at the @azure/[email protected].8 build:es?script. | ||
| npm ERR! Failed at the @azure/[email protected].9 build:es?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 | ||
|
|
@@ -171,11 +177,12 @@ XX of XX: [@azure/app-configuration] failed! | |
| XX of XX: [@azure/cosmos] completed with warnings in ? seconds | ||
| XX of XX: [@azure/eventhubs-checkpointstore-blob] failed! | ||
| XX of XX: [@azure/keyvault-certificates] failed! | ||
| XX of XX: [@azure/service-bus] completed with warnings in ? seconds | ||
| XX of XX: [@azure/service-bus] failed! | ||
| XX of XX: [@azure/storage-file-datalake] failed! | ||
| XX of XX: [@azure/storage-file-share] completed with warnings in ? seconds | ||
| XX of XX: [@azure/storage-queue] completed with warnings in ? seconds | ||
| [@azure/app-configuration] Returned error code: 2 | ||
| [@azure/eventhubs-checkpointstore-blob] Returned error code: 2 | ||
| [@azure/keyvault-certificates] Returned error code: 2 | ||
| [@azure/service-bus] Returned error code: 2 | ||
| [@azure/storage-file-datalake] Returned error code: 2 | ||
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.
this looks bad and is not in master
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.
file hasn't changed since November
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.
Never mind, I was looking at an old commit. There was a commit 4 days ago that added a couple of
?.uses. This fails to parse, which makes me think that the TS we're using isn't actually latest.@weswigham
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.
It is now in master, so might as well fix it there.