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

GPU CI times out with debug=true #280

Open
samuelburnham opened this issue Jan 24, 2024 · 0 comments
Open

GPU CI times out with debug=true #280

samuelburnham opened this issue Jan 24, 2024 · 0 comments

Comments

@samuelburnham
Copy link
Contributor

samuelburnham commented Jan 24, 2024

Problem

The dev-ci Cargo profile implicitly enables debug info to troubleshoot CI failures on pull requests. However, when running GPU CI in e.g. https://github.com/lurk-lab/arecibo/actions/runs/7560396589/job/20592226334, we observe the following:

  • GPU usage spikes to 100% and the program hangs when running tests::test_ivc_nontrivial_with_spark_compression
  • Running with --release or adding debug = false to the dev-ci profile fixes the issue
  • This also occurs when run with only the Pasta engines in https://github.com/lurk-lab/arecibo/blob/dev/src/lib.rs#L1485
  • This likely occurs with the other hanging tests in the above GPU CI run: supernova::snark::test::test_compression_with_circuit_size_difference, supernova::snark::test::test_nivc_trivial_with_compression, and tests::test_ivc_nontrivial_with_compression.
  • This issue does not occur on non-GPU servers or in lurk-rs.

Potential Diagnosis

Grumpkin-msm compiles a lot of code when GPU acceleration is enabled, as seen by its long compile times, so including debug info could be overloading the GPU resources. However, this wouldn't explain the lack of timeouts in lurk-rs.

Solutions

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

1 participant