Generate executable `_job.sh` files
See original GitHub issueIt would be useful to have a configuration setting to generate _job.sh
files that are executable. Would this be a potential feature that could be added?
Thanks
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How to make a file (e.g. a .sh script) executable, so it can be ...
Right-click the file and select Properties. Go to the permissions tab, then tick the box Execute: [ ] Allow executing file as program...
Read more >How to create executable script to run job after one another ...
In command line we use executable script to run the hourly jobs; ./exec_oozie_jobs.sh FIX TOPUP DOMAIN_LENS HOURLY 2019100217,2019100218.
Read more >How to Make Executable .sh Files on Linux and ... - YouTube
Make your own . sh files on Linux with Nano. ... How to Make Executable . sh Files on Linux and Automatically Update...
Read more >Steps to Write and Execute a Shell Script - Javatpoint
Open the terminal. Go to the directory where you want to create your script. · Create a file with .sh extension. · Write...
Read more >Make a file executable in Terminal on Mac - Apple Support
Shell scripts must be executable files in order to run. You can use the chmod command to indicate that the text file is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@jg The
compile
of the check, it is defined here: https://github.com/eth-cscs/reframe/blob/13c372ef7aa5d63f6d74c73f61c4c033c0312d53/reframe/core/pipeline.py#L1165@jgphpc Actually the building phase where @teojgo pointed you has nothing to do with the job script creation. The job script is created by the
ShellScriptGenerator
here:https://github.com/eth-cscs/reframe/blob/13c372ef7aa5d63f6d74c73f61c4c033c0312d53/reframe/core/shell.py#L114
Currently, setting the executable bit is handled by the scheduler backends (only the
local
scheduler does that):https://github.com/eth-cscs/reframe/blob/13c372ef7aa5d63f6d74c73f61c4c033c0312d53/reframe/core/schedulers/local.py#L63-L64
I think the best solution is to move that responsibility to the shell script generator by adding an option that controls whether to set
+x
or not. And then we remove this logic from the local backend, which is just a leftover from the past.