-
Notifications
You must be signed in to change notification settings - Fork 12.9k
Update user baselines #42451
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
Update user baselines #42451
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,28 @@ | ||
Exit Code: 0 | ||
Standard output: | ||
yarn run vX.X.X | ||
$ node --max-old-space-size=3072 ./scripts/build/build.js | ||
Building packages | ||
index.js....................... DONE | ||
doc.js......................... DONE | ||
standalone.js.................. DONE | ||
bin-prettier.js................ DONE | ||
third-party.js................. DONE | ||
parser-babel.js................ DONE | ||
parser-flow.js................. DONE | ||
parser-typescript.js........... DONE | ||
parser-espree.js............... DONE | ||
parser-meriyah.js.............. DONE | ||
parser-angular.js.............. DONE | ||
parser-postcss.js.............. DONE | ||
esm/parser-postcss.mjs......... DONE | ||
parser-graphql.js.............. DONE | ||
parser-markdown.js............. DONE | ||
parser-glimmer.js.............. DONE | ||
parser-html.js................. DONE | ||
parser-yaml.js................. DONE | ||
Done in ?s. | ||
|
||
|
||
|
||
Standard error: |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,11 +1,24 @@ | ||
Exit Code: 0 | ||
Exit Code: 1 | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. this is worse than before, right? Is this due to our test harness changing or vscode changing? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We haven't been building There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is probably something we can ignore? The error reported is that |
||
Standard output: | ||
yarn run vX.X.X | ||
$ gulp compile --max_old_space_size=4095 | ||
[XX:XX:XX] Node flags detected: --max_old_space_size=4095 | ||
$ node --max_old_space_size=4095 ./node_modules/gulp/bin/gulp.js compile | ||
[XX:XX:XX] Using gulpfile /vscode/gulpfile.js | ||
Done in ?s. | ||
[XX:XX:XX] [monaco.d.ts] monaco.d.ts is changed - total time took ?s | ||
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command. | ||
|
||
|
||
|
||
Standard error: | ||
[XX:XX:XX] 'compile' errored after ?s | ||
[XX:XX:XX] Error: monaco.d.ts is no longer up to date. Please run gulp watch and commit the new file. | ||
at formatError (/vscode/node_modules/gulp-cli/lib/versioned/^4.0.0/format-error.js:20:10) | ||
at Gulp.<anonymous> (/vscode/node_modules/gulp-cli/lib/versioned/^4.0.0/log/events.js:31:15) | ||
at Gulp.emit (events.js:203:15) | ||
at Gulp.EventEmitter.emit (domain.js:448:20) | ||
at Object.error (/vscode/node_modules/undertaker/lib/helpers/createExtensions.js:61:10) | ||
at handler (/vscode/node_modules/now-and-later/lib/map.js:46:14) | ||
at f (/vscode/node_modules/once/once.js:25:25) | ||
at f (/vscode/node_modules/once/once.js:25:25) | ||
at tryCatch (/vscode/node_modules/async-done/index.js:24:15) | ||
at done (/vscode/node_modules/async-done/index.js:40:12) | ||
error Command failed with exit code 1. |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,14 +3,37 @@ Standard output: | |
|
||
> [email protected] build /xtermjs | ||
> tsc -b ./tsconfig.all.json | ||
src/browser/Terminal2.test.ts(80,11): error TS2794: Expected 1 arguments, but got 0. Did you forget to include 'void' in your type argument to 'Promise'? | ||
error TS2688: Cannot find type definition file for '../../../out-test/api/TestUtils'. | ||
The file is in the program because: | ||
Entry point of type library '../../../out-test/api/TestUtils' specified in compilerOptions | ||
error TS2688: Cannot find type definition file for '../../../out-test/api/TestUtils'. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. these errors seem worse than before There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm not certain we can know what broke this. None of the projects fixed by #42431 have been building or contributing updated logs for some time now, so there's no way to know what caused these breaks. All of these breaks are based on what is in master now. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The only thing I changed for xterm was the NodeJS version (since xterm started requiring features not present in NodeJS 8). This seems like a problem with their build, not our test (and these user tests often seem to run afoul of that). |
||
The file is in the program because: | ||
Entry point of type library '../../../out-test/api/TestUtils' specified in compilerOptions | ||
addons/xterm-addon-ligatures/src/font.ts(6,29): error TS2307: Cannot find module 'font-finder' or its corresponding type declarations. | ||
addons/xterm-addon-ligatures/src/font.ts(7,32): error TS2307: Cannot find module 'font-ligatures' or its corresponding type declarations. | ||
addons/xterm-addon-ligatures/src/index.ts(7,22): error TS2307: Cannot find module 'font-ligatures' or its corresponding type declarations. | ||
addons/xterm-addon-ligatures/src/index.ts(75,14): error TS2347: Untyped function calls may not accept type arguments. | ||
addons/xterm-addon-ligatures/src/index.ts(76,9): error TS7006: Parameter 'range' implicitly has an 'any' type. | ||
addons/xterm-addon-ligatures/src/index.test.ts(6,23): error TS2307: Cannot find module 'path' or its corresponding type declarations. | ||
addons/xterm-addon-ligatures/src/index.test.ts(7,24): error TS2307: Cannot find module 'sinon' or its corresponding type declarations. | ||
addons/xterm-addon-ligatures/src/index.test.ts(9,29): error TS2307: Cannot find module 'font-finder' or its corresponding type declarations. | ||
addons/xterm-addon-ligatures/src/index.test.ts(10,32): error TS2307: Cannot find module 'font-ligatures' or its corresponding type declarations. | ||
addons/xterm-addon-ligatures/src/index.test.ts(26,25): error TS2304: Cannot find name '__dirname'. | ||
addons/xterm-addon-ligatures/src/index.test.ts(33,25): error TS2304: Cannot find name '__dirname'. | ||
addons/xterm-addon-ligatures/src/index.test.ts(40,25): error TS2304: Cannot find name '__dirname'. | ||
error TS2688: Cannot find type definition file for '../../../out-test/api/TestUtils'. | ||
The file is in the program because: | ||
Entry point of type library '../../../out-test/api/TestUtils' specified in compilerOptions | ||
error TS2688: Cannot find type definition file for '../../../out-test/api/TestUtils'. | ||
The file is in the program because: | ||
Entry point of type library '../../../out-test/api/TestUtils' specified in compilerOptions | ||
error TS2688: Cannot find type definition file for '../../../out-test/api/TestUtils'. | ||
The file is in the program because: | ||
Entry point of type library '../../../out-test/api/TestUtils' specified in compilerOptions | ||
error TS2688: Cannot find type definition file for '../../../out-test/api/TestUtils'. | ||
The file is in the program because: | ||
Entry point of type library '../../../out-test/api/TestUtils' specified in compilerOptions | ||
|
||
|
||
|
||
|
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.
looks like azure-sdk is still blocked by not installing (or a bad install?)
@typescript-eslint/scope-manager
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.
Is this our issue or an issue in
azure-sdk
? I didn't do anything forazure-sdk
in #42431, so as far as I can tell this is just the latest build output frommaster
.