-
Notifications
You must be signed in to change notification settings - Fork 13
Enable testing of LSP server #192
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
Changes from all commits
8867f89
c7cccd2
aedbcac
f5973ce
9f5b3e2
85b147d
a34194e
641578e
337ea07
71cb10e
9835b2a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,23 @@ | ||
| # schedules: | ||
| # - cron: "0 19 * * Sun" # time is in UTC | ||
| # displayName: Sunday overnight run | ||
| # always: true | ||
| # branches: | ||
| # include: | ||
| # - main | ||
|
|
||
| pr: none | ||
| trigger: none | ||
|
|
||
| pool: | ||
| name: TypeScript-1ES-Large | ||
| demands: | ||
| - ImageOverride -equals azure-linux-3 | ||
|
|
||
| extends: | ||
| template: azure-pipelines-gitTests-template.yml | ||
| parameters: | ||
| ENTRYPOINT: lsp | ||
| OLD_VERSION: '0' | ||
| NEW_VERSION: latest | ||
| LANGUAGE: TypeScript | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -54,7 +54,7 @@ jobs: | |
| retryCountOnTaskFailure: 3 | ||
| - task: UseNode@1 | ||
| inputs: | ||
| version: '20.x' | ||
| version: '22.x' | ||
|
Member
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. Would be great to make this Node 24 in a follow-up or something, but not critical.
Member
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. Why is this changing from 20?
Member
Author
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. It'll stop being LTS pretty soon, no? |
||
| displayName: 'Install Node.js' | ||
| - script: | | ||
| npm ci | ||
|
|
@@ -77,7 +77,7 @@ jobs: | |
| artifact: RepoList | ||
| - task: UseNode@1 | ||
| inputs: | ||
| version: '20.x' | ||
| version: '22.x' | ||
| displayName: 'Install Node.js' | ||
| - script: | | ||
| df -h | ||
|
|
@@ -118,7 +118,7 @@ jobs: | |
| - download: current | ||
| - task: UseNode@1 | ||
| inputs: | ||
| version: '20.x' | ||
| version: '22.x' | ||
| displayName: 'Install Node.js' | ||
| - script: | | ||
| npm ci | ||
|
|
||
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -3,16 +3,16 @@ import { mainAsync, reportError, TsEntrypoint } from "./main"; | |
|
|
||
| const { argv } = process; | ||
|
|
||
| if (argv.length !== 11) { | ||
| console.error(`Usage: ${path.basename(argv[0])} ${path.basename(argv[1])} <ts_entrypoint> <old_ts_npm_version> <new_ts_npm_version> <repo_list_path> <worker_count> <worker_number> <result_dir_name> <diagnostic_output> <prng_seed>`); | ||
| if (argv.length < 11) { | ||
gabritto marked this conversation as resolved.
Show resolved
Hide resolved
|
||
| console.error(`Usage: ${path.basename(argv[0])} ${path.basename(argv[1])} <ts_entrypoint> <old_ts_npm_version> <new_ts_npm_version> <repo_list_path> <worker_count> <worker_number> <result_dir_name> <diagnostic_output> <prng_seed> <use_tempfs>?`); | ||
| process.exit(-1); | ||
| } | ||
|
|
||
| const [,, entrypoint, oldTsNpmVersion, newTsNpmVersion, repoListPath, workerCount, workerNumber, resultDirName, diagnosticOutput, prngSeed] = argv; | ||
| const [,, entrypoint, oldTsNpmVersion, newTsNpmVersion, repoListPath, workerCount, workerNumber, resultDirName, diagnosticOutput, prngSeed, tmpfs] = argv; | ||
|
|
||
| mainAsync({ | ||
| testType: "github", | ||
| tmpfs: true, | ||
| tmpfs: tmpfs && tmpfs.toLowerCase() === "false" ? false : true, | ||
|
Member
Author
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. If I ran this with
Member
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. Yeah, no idea on this one. @jakebailey or @sandersn might have ideas, I don't know anything about tmpfs.
Member
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 don't see how this would happen, if you don't use tmpfs it goes mega slow. Where did it give that error? Maybe you're just ooming?
Member
Author
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 can try and reproduce it again, but pretty sure the error was caused by one of the mount commands that we run when |
||
| entrypoint: entrypoint as TsEntrypoint, | ||
| diagnosticOutput: diagnosticOutput.toLowerCase() === "true", | ||
| buildWithNewWhenOldFails: false, | ||
|
|
||
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.
Are there parameters missing to be compatible with the bot? Or are we not doing the bot for now?
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.
For now, I haven't updated the code to handle comparing versions. I don't know how the fuzzer is going to behave, so I wanted to get a sense of it before enabling the whole comparison of versions, and I also need to set up the regular compiler entry point for tsgo because that's probably what would be most useful. If you think I'm being overly cautious, I could set up the whole thing here, but I'm thinking e.g. for the compiler entry point we'll have deprecations to deal with.