peakschris
peakschris
We also have very large compilation commands files (1GB in our case). 24kb per entry. The interesting thing with ours is that all files in a directory have the same...
> If you could have e.g. "per-target" entries listing all the common flags for the file entries below, the file size would go down massively. Yes, this would be a...
@bazelbuild/triage @bazel-io please reopen this This is still an issue with bazel 8.2.1, and makes debugging bazel executables that use DLLs difficult on windows. To reproduce (on windows): ``` git...
@oquenchil could you reopen this? It is possible we may have some time to look at this. Could you advise on where the fix might be?
I'm happy with that restriction (perhaps it could be documented if not already)? I was trying to put it in the root of my drive because I would like a...
Ah, good thought! https://github.com/bazelbuild/bazel/issues/22865 was opened by me, so I have the fix. Sadly the fixed bazel doesn't resolve this - launch time still 5+s Just to confirm that I...
Ok, I updated from 0.32.2 to 0.33.2, and the precompiling option started working. But unfortunately no improvement in speed: ``` INFO: Elapsed time: 0.377s bazel run //:myscript --@rules_python//python/config_settings:precompile=enabled -- --help...
Another datapoint: Using 7z to recursively extract the zip created by py_binary takes 0.64s
Thank you, this is very helpful. The measurements below are with rules_python 0.34. So with a larger python project, myscript.zip is 34MB - 95% python, 4.9% pip modules, 0.1% script...
I've just checked with rules_python@HEAD, nothing in my message above is fixed/improved there vs 0.34