Skip to content

🤖 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

Conversation

typescript-bot
Copy link
Collaborator

This test run was triggerd by a request on #33716
Please review the diff and merge if no changes are unexpected.
You can view the build log here.

cc @microsoft/typescript

@typescript-bot typescript-bot force-pushed the user-update-Microsoft-20200106-refs/heads/release-3.8 branch from 110f5e7 to e5cfa5a Compare February 15, 2020 00:10
@typescript-bot typescript-bot force-pushed the user-update-Microsoft-20200106-refs/heads/release-3.8 branch from e5cfa5a to 39c89c4 Compare February 15, 2020 00:44
Copy link
Member

@sandersn sandersn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

azure-sdk has a new parse error. I'm investigating

@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.
Copy link
Member

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

Copy link
Member

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

Copy link
Member

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

  1. can you take a look?
  2. do you want to merge this in the meantime?

Copy link
Member

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.

@sandersn sandersn merged commit af614cc into microsoft:release-3.8 Feb 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants