NWChemEx / NWChemEx/TensorWrapper
Deadlock during Testing
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 0
- Forks
- 0
- Avg merge
- 5h 33m
- Merged PRs (30d)
- 6
Description
During the unit testing of PR #128, test_tensorwrapper kept hanging for some reason. Here is the link to the failed action: https://github.com/NWChemEx-Project/TensorWrapper/actions/runs/4661680114/jobs/8252100420, as well as the error output in case the link is not accessible at some point:
test 1
Start 1: test_tensorwrapper
1: Test command: /home/runner/work/TensorWrapper/TensorWrapper/build/test_tensorwrapper
1: Working Directory: /home/runner/work/TensorWrapper/TensorWrapper/build
1: Test timeout computed to be: 1500
1:
1: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1: test_tensorwrapper is a Catch v2.13.10 host application.
1: Run with -? for options
1:
1: -------------------------------------------------------------------------------
1: remove_redundancy
1: No redundancy
1: -------------------------------------------------------------------------------
1: /home/runner/work/TensorWrapper/TensorWrapper/tests/ta_helpers/remove_redundancy.cpp:49
1: ...............................................................................
1:
1: /home/runner/work/TensorWrapper/TensorWrapper/tests/ta_helpers/remove_redundancy.cpp:49: FAILED:
1: due to unexpected exception with message:
1: /home/runner/work/TensorWrapper/TensorWrapper/build/_deps/tiledarray-src/src/
1: TiledArray/tensor/tensor.h:668: TA_ASSERT failed: this->range_.rank() != 1 &&
1: "use Tensor::operator[](index) or " "Tensor::at_ordinal(index_ordinal) if
1: this->range().rank()==1"
1:
1: -------------------------------------------------------------------------------
1: remove_redundancy
1: One redundancy
1: -------------------------------------------------------------------------------
1: /home/runner/work/TensorWrapper/TensorWrapper/tests/ta_helpers/remove_redundancy.cpp:55
1: ...............................................................................
1:
1: /home/runner/work/TensorWrapper/TensorWrapper/tests/ta_helpers/remove_redundancy.cpp:55: FAILED:
1: due to unexpected exception with message:
1: /home/runner/work/TensorWrapper/TensorWrapper/build/_deps/tiledarray-src/src/
1: TiledArray/tensor/tensor.h:668: TA_ASSERT failed: this->range_.rank() != 1 &&
1: "use Tensor::operator[](index) or " "Tensor::at_ordinal(index_ordinal) if
1: this->range().rank()==1"
1:
1: !!MADNESS: Hung queue?
1: !!MADNESS: Hung queue?
1: !!MADNESS: Hung queue?
1: !!MADNESS: Hung queue?
1: !!MADNESS: Hung queue?
1: !!MADNESS ERROR: Exception thrown in WorldTaskQueue::fence() with 2 pending task(s)
1: -------------------------------------------------------------------------------
1: sparse_remove_redundancy
1: No redundancy
1: -------------------------------------------------------------------------------
1: /home/runner/work/TensorWrapper/TensorWrapper/tests/ta_helpers/remove_redundancy.cpp:75
1: ...............................................................................
1:
1: /home/runner/work/TensorWrapper/TensorWrapper/tests/ta_helpers/remove_redundancy.cpp:75: FAILED:
1: due to unexpected exception with :
1:
1/1 Test #1: test_tensorwrapper ...............***Timeout 1500.10 sec
0% tests passed, 1 tests failed out of 1
Errors while running CTest
Output from these tests are in: /home/runner/work/TensorWrapper/TensorWrapper/build/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.
Total Test time (real) = 1500.12 sec
The following tests FAILED:
1 - test_tensorwrapper (Timeout)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by running test_tensorwrapper and inspect tests/ta_helpers/remove_redundancy.cpp alongside the linked failed action output. Trace the assertion failures and subsequent hung queue, then confirm the test completes without timing out and the affected cases pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100