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

gasnet CI Failures #1836

Closed
Ethan-DeBandi99 opened this issue Oct 13, 2022 · 2 comments · Fixed by #1841
Closed

gasnet CI Failures #1836

Ethan-DeBandi99 opened this issue Oct 13, 2022 · 2 comments · Fixed by #1841
Assignees
Labels
bug Something isn't working In Progress Work on ticket is in progress / ticket is actively being worked

Comments

@Ethan-DeBandi99
Copy link
Contributor

This issue is related to the Chapel issue #20845.

Arkouda compilation for multi-locale systems appears to require enough memory to cause failures in the CI. The exact error is documented in the Chapel issue. It was recommended that if this becomes severe enough, we could remove gasnet from the CI until compilation is more memory efficient in Chapel. I am not a huge fan of this because it will leave a massive hole in our testing. Posting this as a question to get feedback from others.

@Ethan-DeBandi99 Ethan-DeBandi99 added the question Further information is requested label Oct 13, 2022
@Ethan-DeBandi99 Ethan-DeBandi99 self-assigned this Oct 14, 2022
@Ethan-DeBandi99 Ethan-DeBandi99 added bug Something isn't working and removed question Further information is requested labels Oct 14, 2022
@Ethan-DeBandi99
Copy link
Contributor Author

Ethan-DeBandi99 commented Oct 14, 2022

After discussing with @hokiegeek2 and @pierce314159, we are going to remove the gasnet testing from the workflow at this time. A suggestion to utilize the Chapel C backend was brought up in the Chapel issue, but @ronawho indicated this was not trivial as the docker container being used does not support this. This leaves a hole in our testing and will require us to consistently check the nightly testing, but we cannot keep having CI failures due to memory exhaustion during compilation.

@Ethan-DeBandi99 Ethan-DeBandi99 added the In Progress Work on ticket is in progress / ticket is actively being worked label Oct 14, 2022
@ronawho
Copy link
Contributor

ronawho commented Oct 14, 2022

This leaves a hole in our testing and will require us to consistently check the nightly testing

FWIW we're already checking nightly testing consistently as part of our normal triage so don't think this changes anything there.

Still though, I agree it's unfortunate to lose this as part of CI testing. Hopefully we can do something to reduce memory pressure for the next release and re-enable, but if you find yourselves really missing this testing before then please let me know and we can explore getting the C backend built for docker and separating the chapel and backend compiles to reduce peak memory pressure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working In Progress Work on ticket is in progress / ticket is actively being worked
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants