test: compare Starlark and Python deps parsing for host_plat #2851
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP: This PR is probably not fully done and I am creating this so that the
contributors can collaborate.
I was thinking how we can start enabling the starlark implementation and roll
it out for more and more packages and for that we need more testing and this
test goes like following:
METADATA
file with Starlark and dump therequires_dist
to abzl
file.
rules_testing
test, run the Starlark implementation ofdeps
parsingand compare it with the results we are getting for the Python
implementation.
Once we have sufficient amount of testing done on all platforms our CI has, we
can think of how we can continue improving this. Some ideas:
This can hopefully be a tool to compare and debug problematic cases where we
need to understand what is going on and add a regression test to the Starlark
implementation.
Work towards #260, #2826