Info
It seems that older icecream versions do not handle the paths correctly for src: suppressions inside the blacklist file: https://github.com/icecc/icecream/commit/a2f0d7507c2fb87096c74582d05cdfc05c6e3e40
options include
force all icecreams to upgrade to at least 1.3 (not sure if icecream can enforce this or ignore nodes that are not at least a version)
use fun: function suppressions to mark third party issues
hard fail if user is using icecream and sanitizers
Workaround:
You can build most of the server with ubsan and icecream, the delete the build/$VARIANT/third_party folder and rebuild the same target without icecream.
Top User Comments
JIRAUSER1268551 commented on Tue, 3 Jan 2023 20:51:02 +0000:
Minimum icecream has been updated to 1.3 so this has already been fixed.
xgen-internal-githook commented on Mon, 4 Apr 2022 21:37:57 +0000:
Author:
{'name': 'Daniel Moody', 'email': 'daniel.moody@mongodb.com', 'username': 'dmoody256'}
Message: SERVER-64999 added icecc sanitizer build guard rail about SERVER-59243.
Branch: master
https://github.com/mongodb/mongo/commit/0493b83069d0a2597e8be9023afb480efb507c09
ryan.egesdahl commented on Sun, 15 Aug 2021 22:03:11 +0000:
daniel.moody There's no way to tell Icecream to enforce a minimum daemon version via the command line because the only thing that controls it is the minimum protocol version. It looks like we might be able to finagle this by compressing the environment tarball with `xz` and setting `ICECC_ENV_COMPRESSION=xz` when we have `icecc` version >= 1.3. Doing that enables a protocol restriction that effectively does what we want.
acm commented on Thu, 12 Aug 2021 13:46:00 +0000:
daniel.gottlieb - Yes, that's correct.
daniel.gottlieb@10gen.com commented on Thu, 12 Aug 2021 13:31:51 +0000:
hard fail if user is using icecream and sanitizers
Am I correct that this isn't a problem with the address sanitzer as our denylist for that has no items?