-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revert "typified map.h and dependents" (#79106) #79132
Conversation
cc @PatrikLundell (forgot to tag you in the OP and i'm not sure if github pings people upon edits) |
I did receive two messages for whatever reason, so I guess the explicit pinging might be redundant (not that it matters). I certainly don't understand what's going on, nor why this wasn't flagged on the PR. I don't understand what GENERATE does, but it wouldn't be impossible that it chokes on typed coordinates for some reason. Edit: |
I would expect it chokes on the calculations instead of the typed points, though I don't actually know. Personally I'd try to use it with And I agree that a complete revert is overkill for "just" an asan failure. |
I would be extremely happy if this can be fixed in a more surgical fashion! Thank you! |
The tests are using coordinates in a rather odd way at times, setting up relative coordinates and then using them as bubble ones (and sometimes relative ones in other places in the same test). This is one of these tests. This type of calculations work fine elsewhere, so I don't think switching to tripoint_rel_ms would help, but I guess we won't find out unless someone is willing to expend the effort to test it. @moxian: It seems to me the limited approach should work, but I guess we won't know until the tests have been performed. Edit: |
Summary
None
Purpose of change
#79106 seems to have introduced ASan failure. See failed runs
The timing is suspicious (the failures started happening rouhgly after #79106 got merged), and the errors have
map_test.cpp
in them, which is vaguely related to what #79106 was doing.The error itself is rather cryptic and I don't think this helps, but I'll add it here for posterity:
I don't think I am able to debug this, but I do believe it's valuable to revert it first in order to get CI back to mostly-green, and then reapply later when we better understand what's going on and how to fix.
Describe the solution
Click the Revert button on github.
Describe alternatives you've considered
Testing
None.
Hopefully CI will pass.
Additional context