strager
https://github.com/quick-lint/quick-lint-js/actions/runs/5889667835/job/15973875729
https://github.com/quick-lint/quick-lint-js/actions/runs/5923102122/job/16058538086
I ran the test suite on my M1 laptop for an hour and a half and it didn't hit this flaky failure. (It did hit another flaky failure, though: `Running...
Unusual logs in this failure: https://github.com/quick-lint/quick-lint-js/actions/runs/5945589414/job/16125151877 ``` Running open existing non-JS file ... OK open existing non-JS file Running rename open .js file to .py ... Unable to read file...
Unusual logs again: https://github.com/quick-lint/quick-lint-js/actions/runs/5954183289/job/16150616742 The unusual logs correlate with commit 246d60ad02ab5d2bf7d93a10ec4cb36b87e2efc8 which upgraded the VS Code we test against.
Git commit 550b51d67e2fca7834f29de191d695e2dd50c3fa added `--disable-gpu` to the VS Code flags. I think this will help with macOS AArch64 flakiness. It doesn't seem to help with Windows flakiness though: https://github.com/quick-lint/quick-lint-js/actions/runs/6129946246/job/16638617081
Some thoughts: * Do we look for only certain file extensions? Which ones? .js .mjs .cjs? Do we also look for .JS (capital)? * Do we consider hidden files? *...
Anything related to the following syntax is a namespace alias (despite the fact that the keyword `import` is used): ```typescript import ns = otherns; ``` Anything related to the following...
@cmstoddard No, this issue is still present.
> I found some files in test folder, which has some function name like ...import_alias... but verifies namespace alias, does it mean to change function name to ...namespace_alias...? Yes. >...