sql: refactor deps tests to use bazel#79409
Conversation
This commit refactors most `VerifyNoImports` dependency tests in the sql folder to use the newly introduced bazel test utilities. Release note: None
|
Your flake, womp womp: Are there features regarding prefixes or |
|
Newbie question: why do we disallow these imports? Is it to prevent layer violations in the vectorized engine? |
|
The flake appears to be known (#74554).
I don't think so - all tests that are converted in this PR didn't use those features, and it was pretty simple to convert them to the new format. One thing I noticed is that some of the prohibited dependencies would form import cycles if they were actual dependencies, so I guess I could have trimmed down the lists a bit, but I decided to not think too much and converted things as is. There were a couple of failures though, so I had to adjust the lists. Still, the process was quite straightforward, thanks for setting it up! TFTRs! bors r+ |
No, mostly to make the packages that are imported in many places lightweight - recent example, a change in |
It would be very helpful if you could provide a list of the deps you had to delete to get these tests to pass. Would be great if we could drill down on the forbidden imports that got introduced due to bitrot and start addressing them. |
Sorry, I should have been more specific. I don't think any of the dependencies were bad - the tests were broken when they were introduced. A couple of examples: |
Makes sense, thank you! |
|
The way I see it, this test is primarily about enforcing dependency graph hygiene. |
|
Build failed (retrying...): |
|
Build succeeded: |
This commit refactors most
VerifyNoImportsdependency tests in the sqlfolder to use the newly introduced bazel test utilities.
Release note: None
Jira issue: CRDB-14814