compile failure on chromium.memory/win-asan |
|||||
Issue descriptionFiled by sheriff-o-matic@appspot.gserviceaccount.com on behalf of wolenetz@chromium.org compile failure on chromium.memory/win-asan Builders failed on: - win-asan: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/win-asan
,
Jan 4
,
Jan 4
,
Jan 4
Looking
,
Jan 4
The very next build's compile step succeeded; the problem on the bot seems to have been ephemeral.https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/win-asan/2828
,
Jan 4
FYI - https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/win-asan/2828 succeeded. Closing.
,
Jan 10
This happened again today: https://ci.chromium.org/p/chromium/builders/luci.chromium.ci/win-asan/2904 lld-link: error: could not get the buffer for the member defining ??0ElapsedTimer@base@@QEAA@XZ: Insufficient system resources exist to complete the requested service.
,
Jan 10
My guess is that the bot is running out of memory. We have some monitoring data which seems to suggest this could be happening, although it's not definitive. The graphs seem to stop producing data right around when the errors occur, which I could imagine happens because the system is under high load, and so can't send any data. Is it expected that asan builds would use large amounts of memory? That seems to make sense to me, but I'm not that familiar with how asan builds work, and what it means exactly about how the code is compiled. I think it's worth beefing up the machine, at least with more ram, and possibly CPU. I'll work on that (and take a look at other asan builders, to see if those should be beefed up as well).
,
Jan 11
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by wolenetz@chromium.org
, Jan 4