Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Defect: cafrun should report an error if -n # argument is not provided #717

Closed
1 task done
everythingfunctional opened this issue Oct 28, 2020 · 2 comments · Fixed by #719
Closed
1 task done

Defect: cafrun should report an error if -n # argument is not provided #717

everythingfunctional opened this issue Oct 28, 2020 · 2 comments · Fixed by #719
Assignees

Comments

@everythingfunctional
Copy link
Collaborator

  • I am reporting a bug others will be able to reproduce and not asking a question or requesting a new feature.

System information including:

  • OpenCoarrays Version: 2.9.0
  • Fortran Compiler: gfortran 10.2.0
  • C compiler used for building lib: Installed from AUR
  • Installation method: from AUR
  • All flags & options passed to the installer: N/A
  • Output of uname -a: Linux darter 5.9.1-arch1-1 tests dis_transpose: test passed  #1 SMP PREEMPT Sat, 17 Oct 2020 13:30:37 +0000 x86_64 GNU/Linux
  • MPI library being used: MPICH 3.4
  • Machine architecture and number of physical cores: Intel 4 core (i7?)
  • Version of CMake: 3.18.4

To help us debug your issue please explain:

executing cafrun path_to_executable simply exits with a 0 status, and does nothing

What you were trying to do (and why)

I was simply trying to run my program

What happened (include command output, screenshots, logs, etc.)

Nothing. No output was produced and the exit status was 0

What you expected to happen

Either, the program was run with a single image, or an error was reported about the misuse of the command

Step-by-step reproduction instructions to reproduce the error/bug

  1. Compile a program with caf main.f90 -o main
  2. Run the program with cafrun main
@rouson rouson self-assigned this Oct 28, 2020
@vehre
Copy link
Collaborator

vehre commented Oct 28, 2020 via email

@everythingfunctional
Copy link
Collaborator Author

That does not solve this particular issue, and in any case is only necessary if the command you're trying to run is in the current directory, and . is not in your PATH environment variable. For example running the command main may not work, and would need to be ./main, but in this case ./cafrun would not be appropriate because the cafrun executable is not in the current directory.

rouson added a commit that referenced this issue Nov 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants