-
Notifications
You must be signed in to change notification settings - Fork 146
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
Realm barrier assert in generation on PowerPC #1820
Comments
@elliottslaughter Which commit from September 2024 is this based on? |
It's based on b8316fb. |
If there is any bug that will be on me |
@apryakhin I think this particular assertion predates the changes you made to the barriers which is why I wanted to see the version of the code that matters. @elliottslaughter That commit hash does not align with the backtrace that you gave above. Here's the assertion from the backtrace, but you can see that the line numbers don't align (and I don't think the difference can be explained by the one other commit that you merged). |
Hi all, I have not been able to reproduce this one on |
This is a fairly old runtime, so this may not be actionable. But I wanted to document this, and we can close the issue if we conclude that it's been resolved in a newer version.
This is S3D on Lassen at 32 nodes. It's non-deterministic, probability < 20%.
s3d.x: /g/g19/eslaught/s3d-subranks-2025-01-08-sep2024-legion/legion/runtime/realm/event_impl.cc:2759: static void Realm::BarrierSubscribeMessage::handle_message(Realm::NodeID, const Realm::BarrierSubscribeMessage&, const void*, size_t): Assertion `it->second > impl->generation.load()' failed.
Backtrace:
Legion version is a branch based on a September 2024 commit, plus one fix: https://gitlab.com/StanfordLegion/legion/-/commit/d4392d6f01762cdde198a8f44da8c05643c9ea34
The text was updated successfully, but these errors were encountered: