Hi there,
I’m a Solutions Engineer for Develocity at Gradle, and we’ve recently observed an issue where builds running on CircleCI agents no longer report accurate CPU and memory usage.
This wasn’t always the case — when we originally released the feature, resource tracking worked correctly on CircleCI. For example, this older build scan shows accurate usage data:
Working example (October 2024)
However, since the beginning of this year, we’ve noticed that tracked memory and CPU values remain fixed throughout the entire build, rather than reflecting dynamic usage:
Example of current behavior
Our Build Scans use a lightweight library that reads data directly from /proc/meminfo, but we’ve verified that the values returned on CircleCI agents are now constant from the start to the end of the build.
We’ve also received similar reports from multiple customers using CircleCI. Could someone from your team confirm if there have been recent changes in the container or VM environment that might affect process-level resource reporting?
Thank you for your time and any insights you can provide!