TBB issues when CRAN runs tests on package
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- backend, testing-qa
Research direction
Start with src/tbb/scheduler.cpp at line 328 and the linked clang-ASAN and clang-UBSAN test outputs. Reproduce the reports by running testthat::test_check for secr and openCR under the sanitizer configurations. Done means identifying the RcppParallel cause and either eliminating the invalid tbb::task report or documenting the required supported setting.
Written by the indexing model from the issue text.
Description
Firstly, please direct me to a more suitable list if this is not where I should seek help with RcppParallel.
CRAN would like me to fix clang-ASAN and clang-UBSAN issues from RcppParallel when I submit packages 'secr' and 'openCR'. These are completely arcane to me. The problem only seems to arise when running tests. Is there a setting in RcppParallel >=5.1.1 that will get me through?
The test results are at
https://www.stats.ox.ac.uk/pub/bdr/memtests/clang-ASAN/secr/tests/testthat.Rout.fail
and
https://www.stats.ox.ac.uk/pub/bdr/memtests/clang-UBSAN/openCR/tests/testthat.Rout
Here is a typical snippet from the first:
library(testthat)
test_check("secr")
Loading required package: secr
This is secr 4.4.1. For overview type ?secr
../../src/tbb/scheduler.cpp:328:16: runtime error: member call on address 0x7f795c81ff40 which does not point to an object of type 'tbb::task'
0x7f795c81ff40: note: object has invalid vptr
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Thanks
Murray
- Dominant language
- C++
- Stars
- 173
- Forks
- 60
- Avg merge
- 1h 55m
- Merged PRs (30d)
- 2
Contributor guide
No contributing guide indexed for this repository
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.
More from RcppCore/RcppParallel
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
RcppCore/RcppParallel#239 · 6 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 20/100
RcppCore/RcppParallel#228 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
RcppCore/RcppParallel#227 · 6 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
RcppCore/RcppParallel#216 · 5 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
RcppCore/RcppParallel#213 ·
All issues in RcppCore/RcppParallel
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
objectionary/eo-graphs#74 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 88/100
QuantStack/git2cpp#187 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100