Testflo default NUM_PROCS causes tests to fail on centos with Intel compilers
Nobody has claimed this yet.
- Dominant language
- Fortran
- Stars
- 332
- Forks
- 124
- PR merge metrics
- No merged PRs in 30d
Description
Description
When the tests are run on Intel with testflo -v . or with testflo -v -n 5 (or greater) the tests encounter a bus error
Caught signal number 7 BUS: Bus Error, possibly illegal memory access
It is not well understood why this issue occurs, but it can easily be avoid by passing testflo the arguement -n followed by a number less than or equal to 4 (this maybe greater if your machine has more than 4 cores).
Steps to reproduce issue
Please provide a minimum working example (MWE) if possible
- run lastest centos intel docker image
- navigate to adflow folder and download the test input files
- run the tests with
testflo .
Code versions
List versions only if relevant
- Python 3
- ADflow 2.2.1
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.
Research direction
Start by reproducing the failure with testflo . in the latest CentOS Intel Docker image, using the ADflow 2.2.1 test inputs. Compare it with runs using testflo -n at four or fewer processes; done means the default NUM_PROCS no longer causes a bus error while the test suite runs successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fortran, python
- Domain
- devtools, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100