-
Notifications
You must be signed in to change notification settings - Fork 18k
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
x/tools/gopls: add regtests for multiple workspace folders #42111
Comments
Change https://golang.org/cl/257138 mentions this issue: |
Reopening because this isn't just for nested modules--we need to add tests for multiple workspace folders, each containing a module. |
Ah, wrong issue. My bad! |
Change https://golang.org/cl/276975 mentions this issue: |
This change both simplifies the options used to configure workspace folders in regtests, and allows for configuring multiple workspace folders. The WithoutWorkspaceFolders, RootPath, and NestWorkdir options are all replaced by a single WorkspaceFolders option. NestWorkdir was always a bit too magical, modifying the execution directory within the runner itself. Instead, just explicitly move files down into a nested directory. runModfileTests was also a bit too much of a special case. Eliminate it by adding functionality to run multiple times with different options. Upon the way I started using literals to configure runs, and I think this is cleaner. Let me know what you think about runMultiple, etc. This overlaps with the execution modes, which could probably be eliminated in a later CL. For golang/go#42111 Change-Id: I56915d8930bc47561cc827b918621cff4b994226 Reviewed-on: https://go-review.googlesource.com/c/tools/+/276975 Run-TryBot: Robert Findley <rfindley@google.com> gopls-CI: kokoro <noreply+kokoro@google.com> TryBot-Result: Go Bot <gobot@golang.org> Trust: Robert Findley <rfindley@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Rebecca Stambler <rstambler@golang.org>
This change both simplifies the options used to configure workspace folders in regtests, and allows for configuring multiple workspace folders. The WithoutWorkspaceFolders, RootPath, and NestWorkdir options are all replaced by a single WorkspaceFolders option. NestWorkdir was always a bit too magical, modifying the execution directory within the runner itself. Instead, just explicitly move files down into a nested directory. runModfileTests was also a bit too much of a special case. Eliminate it by adding functionality to run multiple times with different options. Upon the way I started using literals to configure runs, and I think this is cleaner. Let me know what you think about runMultiple, etc. This overlaps with the execution modes, which could probably be eliminated in a later CL. For golang/go#42111 Change-Id: I56915d8930bc47561cc827b918621cff4b994226 Reviewed-on: https://go-review.googlesource.com/c/tools/+/276975 Run-TryBot: Robert Findley <rfindley@google.com> gopls-CI: kokoro <noreply+kokoro@google.com> TryBot-Result: Go Bot <gobot@golang.org> Trust: Robert Findley <rfindley@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> Reviewed-by: Rebecca Stambler <rstambler@golang.org>
I don't think this is a high priority anymore, since workspaces are now our recommended way to work on multiple modules simultaneously. |
We've got several tests, and can add more if and when we have specific things to test for multiple folders. Closing as obsolete. |
We currently have no test coverage for multiple workspace folders (not using
experimentalWorkspaceModule
). We can add a new mode to the regression tests to cover this case.The text was updated successfully, but these errors were encountered: