-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Excessive re-building triggered by commit 27c983b (#2534) #2552
Comments
This was a longstanding problem with external deps that manifested in google/oss-fuzz#1130. Signed-off-by: Harvey Tuch <htuch@google.com>
Should add that none of the related environment variables are defined (CC CXX CFLAGS CXXFLAGS LD_LIBRARY_PATH). I have not tested with any of them defined. |
I'll take an AI to look into this. Would be helpful if you could set them to "" and see if it still does this as a data point. |
Do you know if setting these env variables to "" is safe? Would that not override some defaults with nothing? |
Retested with |
@htuch FYI I just tried it locally and this is also broken for me with our external build script outside of bazel:
Rebuilds for me every time. It used to detect no changes. |
Fixes envoyproxy#2552. Signed-off-by: Harvey Tuch <htuch@google.com>
Fixes #2552. Signed-off-by: Harvey Tuch <htuch@google.com>
Description: Replace an old link that does not work anymore (404) with a new one. Risk Level: Low Testing: Checked that I can open the page Docs Changes: fix link url Release Notes: N/A Signed-off-by: JP Simard <jp@jpsim.com>
Description: Replace an old link that does not work anymore (404) with a new one. Risk Level: Low Testing: Checked that I can open the page Docs Changes: fix link url Release Notes: N/A Signed-off-by: JP Simard <jp@jpsim.com>
Title: Excessive re-building triggered by commit 27c983b (#2534)
Description:
commit 27c983b (PR #2534) seemingly works as intended as long as the bazel server is running. If the bazel server is restarted, however, some, if not most, dependencies are re-built, taking about 10 minutes CPU time.
This issue is easy to see with the bazel
--batch
option, as it does not leave the server running in the background.Repro steps:
Note that this behavior is not observed on previous commits, there bazel caching works also across bazel server restarts and in batch mode.
The text was updated successfully, but these errors were encountered: