Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Consistent RayleighTest failure ("unspecified launch failure")

Open
#2 10 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Domain
hpc, testing-qa

Research direction

Start by running ./utest -gpu 0 RayleighTest, focusing on the failing “run resolution 32” case. Compare the failure with the attached rt_output.txt and dq_output.txt diagnostics; done means the RayleighTest passes on the reported GTX 260 setup in both release and debug builds.

Written by the indexing model from the issue text.

Description

auto-migrated Priority-Medium Type-Defect
When running the RayleighTest unit test I encounter a consistent
"unspecified launch failure".  This error is observed for both release and
debug versions.

What steps will reproduce the problem?
1. Run the RayleighTest unit test ( ./utest -gpu 0 RayleighTest ) Failure
observed for the "run resolution 32" case.  See rt_output.txt for sample
output.

What version of the product are you using? On what operating system?
Running current release version available via hg clone.

Running on CentOS 5.4 x86-64 system (uname -a):

Linux manzano 2.6.18-164.el5 #1 SMP Thu Sep 3 03:28:30 EDT 2009 x86_64
x86_64 x86_64 GNU/Linux

Using GeForce GTX 260 MaxCore device (216 cores / 27 multiprocessors).  See
dq_output.txt for more details.




Original issue reported on code.google.com by doug.enr...@gmail.com on 31 Oct 2009 at 5:44

Attachments:

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

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ExpectationMax/opencurrent

All issues in ExpectationMax/opencurrent

Similar issues

More HPC issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.