Skip to content
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

Do not schedule a syntactic test rescan if we know that we already have an up-to-date syntactic test index for it #1956

Merged
merged 1 commit into from
Feb 5, 2025

Conversation

ahoppen
Copy link
Member

@ahoppen ahoppen commented Jan 28, 2025

If the build system is sending us with buildTarget/didChange, we would always create processor count * 4 new entries in the indexingQueue to rescan those files, if they are up-to-date. This can be quite wasteful if the underlying files didn’t actually change. Do a quick scan up-front to check if the files actually need to be re-scanned up-front.

…ve an up-to-date syntactic test index for it

If the build system is sending us with `buildTarget/didChange`, we would always create processor count * 4 new entries in the `indexingQueue` to rescan those files, if they are up-to-date. This can be quite wasteful if the underlying files didn’t actually change. Do a quick scan up-front to check if the files actually need to be re-scanned up-front.
@ahoppen
Copy link
Member Author

ahoppen commented Jan 28, 2025

@swift-ci Please test

@ahoppen
Copy link
Member Author

ahoppen commented Feb 5, 2025

@swift-ci Please test Windows

@ahoppen ahoppen merged commit 03da7e9 into swiftlang:main Feb 5, 2025
3 checks passed
@ahoppen ahoppen deleted the reduce-syntactic-test-rescan branch February 5, 2025 18:09
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