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

collecting idle-rate performance counters on multiple localities produces an error #2905

Closed
zbyerly opened this issue Sep 15, 2017 · 1 comment · Fixed by #2906
Closed

collecting idle-rate performance counters on multiple localities produces an error #2905

zbyerly opened this issue Sep 15, 2017 · 1 comment · Fixed by #2906

Comments

@zbyerly
Copy link
Member

zbyerly commented Sep 15, 2017

collecting idle-rate performance counters (on hello_world) on multiple localities produces the error:
pool 1 (zero-based index) requested out of bounds. The partitioner owns only 1 pools: HPX(bad_parameter)

running this sbatch script on Rostam:
https://gist.github.com/zbyerly/b06bfd32567c677e15c4483f76819c89

produces this:
https://gist.github.com/zbyerly/8fed68788ff317590f242e46905d6f44

@hkaiser
Copy link
Member

hkaiser commented Sep 15, 2017

Thanks for reporting. This is a genuine bug introduced by the recent introduction of the resource-partitioner and the related changes to the performance counters

hkaiser added a commit that referenced this issue Sep 15, 2017
- this fixes #2905
- flyby: fixing lock held during suspension problem in resource_partitioner
hkaiser added a commit that referenced this issue Sep 15, 2017
- this fixes #2905
- flyby: fixing lock held during suspension problem in resource_partitioner
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants