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

all tests failed

Open
#20 1 comment 0 reactions 0 assignees View on GitHub

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
testing

Research direction

Start by running make test and reading LastTest.log, especially the Diffusion1DTest output. Inspect src/ocuequation/eqn_diffusion1d.cpp around line 91 and trace the reported CUDA failures in the device equation code. Done means the 17 test cases complete successfully on the stated Linux environment.

Written by the indexing model from the issue text.

Description

auto-migrated Priority-Medium Type-Defect
What steps will reproduce the problem?
1.make test
2.
3.

What is the expected output? What do you see instead?

0% tests passed, 17 tests failed out of 17

What version of the product are you using? On what operating system?

opencurrent 1.1.0,Linux 2.6.18-238.19.1.el5, x86_64 GNU/Linux

Please provide any additional information below.

LastTest.log

"Diffusion1DTest" start time: Oct 04 17:23 EDT
Output:
----------------------------------------------------------
[INFO] Running on GPU 0
Running tests: Diffusion1DTest
running Diffusion1DTest on thread 0
[ERROR] Sol_LaplacianCentered1DDevice::apply_boundary_conditions - CUDA error 
"invalid device function "
[ERROR] Sol_LaplacianCentered1DDevice::solve - CUDA error "invalid device 
function "
[ERROR] Grid1DDeviceF::linear_combination - CUDA error "invalid device function 
"
[WARNING] Failure in file 
"~/opencurrent-1.1.0/src/ocuequation/eqn_diffusion1d.cpp" at line 91
[ERROR] Equation::advance - failed to advance equation

Original issue reported on code.google.com by bliu...@gmail.com on 4 Oct 2011 at 9:38

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 Testing & QA issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.