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

ci/nightly: Compare parsec and parsec-tool dependency versions #116

Conversation

tgonzalezorlandoarm
Copy link
Member

Depends on #115 . Please only review when this one is merged.

  • Compare dependencies between parsec and parsec-tool to spot common dependencies that are being used with different versions.
  • Incorporate a nightly check to test this

Closes parallaxsecond/parsec#360

@tgonzalezorlandoarm
Copy link
Member Author

Triggered Nightly check:
https://github.com/tgonzalezorlandoarm/parsec-tool/actions/runs/6972003989

Note: This one should fail as parsec is currently using a different version of rustix

@tgonzalezorlandoarm
Copy link
Member Author

@tgonzalezorlandoarm tgonzalezorlandoarm marked this pull request as draft November 24, 2023 15:42
@tgonzalezorlandoarm
Copy link
Member Author

@tgonzalezorlandoarm tgonzalezorlandoarm marked this pull request as ready for review November 24, 2023 16:17
if args.compare:
parsec_repo, parsec_tool_repo = args.deps_dir
mismatches_parsec = run_deps_mismatcher(run_cargo_tree(parsec_repo))
mismatches_parsec_tool = run_deps_mismatcher(run_cargo_tree(parsec_tool_repo))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the parsec service needs a few additional flags in the cargo tree command right?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for noticing! Well spotted

@tgonzalezorlandoarm
Copy link
Member Author

tests/ci.sh Outdated Show resolved Hide resolved
 * Print error information on the dependency mismatch checker instead
   of doing so in the ci.sh script.

This simplifies the logic and reduces maintainability efforts.

Signed-off-by: Tomás González <[email protected]>
@tgonzalezorlandoarm tgonzalezorlandoarm force-pushed the tg/deps-matching-w-parsec branch 2 times, most recently from df3ef09 to 263202d Compare November 27, 2023 13:56
parsec and parsec-tool share some dependencies. In those shared
dependencies, the used versions should be the same.

 * Modify utils/dependency_cross_matcher.py to cover the case of
   comparing parsec and parsec-tool dependencies as well as the
   previous case of checking mismatches in parsec-tool dependencies.

Signed-off-by: Tomás González <[email protected]>
We could easily discover mismatches in a normal CI run instead of in
a nightly run.

 * Update the mismatcher job so that it's run on each PR instead of
   on a nightly.

Signed-off-by: Tomás González <[email protected]>
 * Use the newly added --compare option in
   utils/dependency_cross_matcher.py to compare dependencies between
   parsec and parsec-tool to spot common dependencies that are being
   used with different versions.

Signed-off-by: Tomás González <[email protected]>
Keep rustix updated and avoid a dependency mismatch with parsec.
Please check:
parallaxsecond/parsec#741

Signed-off-by: Tomás González <[email protected]>
@tgonzalezorlandoarm
Copy link
Member Author

Once this is merged, I will create a PR in https://github.com/parallaxsecond/parsec to keep the tests synced.

@tgonzalezorlandoarm tgonzalezorlandoarm merged commit 6fa0f5c into parallaxsecond:main Nov 28, 2023
5 checks passed
@tgonzalezorlandoarm tgonzalezorlandoarm deleted the tg/deps-matching-w-parsec branch November 28, 2023 10:19
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.

Set up build to track dependency mismatches
2 participants