This repository was archived by the owner on Jul 1, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
MLX5_INFINIBAND variant of error: call to '__read_overflow2' #146
Labels
tuxml-study-buildfailures
Discussions/insights about build failures
Comments
Similar story:
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When investigating one specific failure (thanks to rule-based decision tree):
rawtuxdata.query("MLX5_INFINIBAND == 'm' & GENERIC_ALLOCATOR == 'n' & DRM_VBOXVIDEO != 'y' & WANXL_BUILD_FIRMWARE != 'y' & AIC7XXX_BUILD_FIRMWARE != 'y' & AIC79XX_BUILD_FIRMWARE != 'y'")[['cid', 'vmlinux', 'IPV6', 'UBSAN_SANITIZE_ALL', 'INFINIBAND_ADDR_TRANS', 'FORTIFY_SOURCE', 'UBSAN_ALIGNMENT', 'UBSAN_NULL', 'NET_FOU_IP_TUNNELS']]
I was surprised to notice similar error messages as in #142 and #145
Again, we have our friend
FORTIFY_SOURCE
, IPV6 ton
andUBSAN
checking)So here again it's not a masking effect, but a possible misclassification of the decision tree that "fails" to group together some options...
The text was updated successfully, but these errors were encountered: