Tests are very brittle on low memory cards
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- testing-qa
Research direction
Start with the RayleighTiming test and the cuda_malloc failures in the checked-in test suite; first reproduce the failure on the reported 1 GB card. Done means the suite runs unmodified on a reasonable low-memory card, with test resolutions chosen from available memory up to a maximum, and the existing tests still pass.
Written by the indexing model from the issue text.
Description
I'm working with a 1Gb card (Quadro FX 3800, if it matters) and the test
suite fails (cuda_malloc, unsurprisingly) when I attempt to run it as it's
currently checked in on HEAD. RayleighTiming, at least, fails, as it
defaults to trying a 384^2 x 192 grid, which I can't allocate. Easily fixed
by modifying the test, but I think that the test should probably run
unmodified on any reasonable card.
One simple change I can see would be querying the card for available memory,
and then running each test at a resolution that fills most of the available
memory (up to some maximum.) If you are amenable to this change, I'm happy
to make it for you, in fact.
Original issue reported on code.google.com by andrewhh...@gmail.com on 13 May 2010 at 10:01
- Dominant language
- Cuda
- Stars
- 6
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
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 ExpectationMax/opencurrent
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
ExpectationMax/opencurrent#23 · 1 comment ·
-
all tests failed Openauto-migrated Priority-Medium Type-Defect
Difficulty 4/5 3-5 days Newbie friendliness 25/100
ExpectationMax/opencurrent#20 · 1 comment ·
-
auto-migrated Priority-Medium Type-Defect
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
auto-migrated Priority-Medium Type-Defect
Difficulty 4/5 3-5 days Newbie friendliness 28/100
-
auto-migrated Priority-Medium Type-Defect
Difficulty 2/5 1-3 hours Newbie friendliness 25/100
ExpectationMax/opencurrent#17 · 1 comment ·
All issues in ExpectationMax/opencurrent
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fulcrumgenomics/ferro-hgvs#2251 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
personalrobotics/tsr#127 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Flaky: conversation-lifecycle terminal-error gate compares rendered clock time across settle/reload Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nesquena/hermes-webui#7792 ·
-
category/development priority/P2 scope/file-operations scope/testing type/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100