-
Notifications
You must be signed in to change notification settings - Fork 60
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
Slow (2 hours) for 7000 targets #221
Comments
Thanks for your response. I will give that a try. I think I can just use bazel's git_override to get that particular commit. Btw is there a reason you don't merge that branch in / any downsides? |
I don't see any downsides from this approach, it should be just as precise with dramatically less file reads. I will work on trying to use this internally to help with validation |
Did this end up working for you? |
Hi @tinder-maxwellelliott. Unfortunately it didn't seem to help us much. Still taking over 2 hours. Just to confirm we get a list of targets that changed with git diff --name-only "$previous_revision" "$final_revision" > "$modified_file_paths" and then the two generate-hashes we add --modified-filepaths=$modified_file_paths |
Are you using cquery for your execution? That can explain the slowdown |
(sorry for the slow response, I didn't see a notification about this reply). I don't think so? This is the script we were trying.
|
Hi,
I'm not quite sure how to get a simple reproduction. In our repo (bazel 7.1.1, bazel-diff 7.0) when we have a large number (7000) targets change (due to e.g. changing a build flag) then bazel-diff get-impacted-targets step takes 2 hours to complete.
We are running a setup very similar to the example script in this repo.
I'm just wondering if you had any pointer how we could try and determine what's going on. From other comments, I don't think this is expected.
The text was updated successfully, but these errors were encountered: