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
Syntax error near unexpected token '(' from export of BASH_FUNC_module() #61
Comments
Jobs and the module system are a recurring issue Questions:
|
My .bashrc and bash_profiles are below... ################################################## commands which work for both GPC and TCS can go here#setting $scratch setting alias to the camh sccalias scc='edickie@192.197.205.74' #adding this to PATH #other enviroment stuff #export LD_LIBRARY_PATH=/home/t/tpaus/tpaus/opt/minc_prereq/lib HOST=$(uname) if [ "${HOST}" == "AIX" ]; then
hdf5/187-v18-serial-intel octave/3.8.1
fi #################################################### commands which work for both GPC and TCS can go herealias passwd='echo "Please use the SciNet portal to change password: HOST=$(uname) if [ "${HOST}" == "AIX" ]
else fi PS1="\h-$ " if [ -f ~/.bashrc ]; then FSL Setup#FSLDIR=/home/j/jlerch/edickie/fsl5/fsl On Wed, Mar 23, 2016 at 3:14 PM, Gabriel A. Devenyi <
|
Did the jobs work? |
You are loading modules in your .bashrc/.bash_profile From what I recall, those are the origin of the modules errors you posted. Please remove those and try again. |
We could add |
We should test of excluding that breaks module loading in the job script preamble |
FYI, just tested this on scinet and I am also seeing this same error. I am investigating. |
Okay, if I remove the export, the jobs run fine. Question is, why aren't you seeing this error on scinet? If I run a job script modified to not have the module() export and to contain a module load statement, then I do get an error when trying to load modules as expected:
Oh |
Okay, I've submitted a fix to ignore the |
Does this allow modules to be loaded in the job? Or is that now broken? |
Does this allow modules to be loaded in the job? Or is that now broken?
It's broken on scinet now (unless we switch back to using bash -l). I
don't yet understand it, but bash on Ubuntu (and the same version of
Bash on Centos here at CAMH) doesn't export the BASH_FUNC_modules()
variable so isn't broken by this change.
|
I'd still like to know more about how you have things configured on
Scinet such that you aren't seeing this error. What does your .bashrc
look like?
|
I actually didn't say anywhere than I don't see those errors... I haven't tested the latest version with module saving directly on scinet. Furthermore, on SGE here at the CIC, I get that error with the latest qbatch. |
I haven't tested the latest version with module saving directly on scinet.
What do you mean by "module saving"?
Furthermore, on SGE here at the CIC, I get that error with the latest qbatch.
Latest, as in, including the fix to ignore "BASH_FUNC_module()"?
|
** environment saving intrinsic to qbatch, rather than using the scheduler system to handle it. Latest as in immediately prior to the "fix" |
Fun fact, this isn't an SGE issue, this in an importing bash environment issue. Running python tests for an (unrelated change):
This is of course, without the "fix" |
See PR #68 for a broader fix to ignore function exports. |
Fixed by #68 |
Hey guys,
My jobs finish with the following error message:
Here is what the .array script looked like...
The text was updated successfully, but these errors were encountered: