Skip to content
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

Argobots state dump is very large #138

Open
roblatham00 opened this issue May 6, 2021 · 1 comment
Open

Argobots state dump is very large #138

roblatham00 opened this issue May 6, 2021 · 1 comment

Comments

@roblatham00
Copy link
Contributor

Argobots stack dump is helpful, or at least the human readable part is. I don't know who reads the 64k lines of raw data. There's a way to turn it off, though: pmodels/argobots#330 Margo should suppress the raw stack dump.

@carns
Copy link
Member

carns commented May 7, 2021

I just realized that the env variable option must be set at margo init time (it is not re-evaluated at run time when collecting a stack trace). That's not terrific because it means that until we have an external function to set parameters (for use in ssg etc.) it will be hard to get consistent.

Leaving this open for now; when there is a new abt release and corresponding spack package update we can set the build-time option for this. When the general margo abt settings path is cleaned up a big (sort of in #118) we can try to standardize on setting the env variable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants