You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The error message raised on badly formatted bash apps is not clear. This is slightly better for threads than IPP, but both are not as helpful as they should be. We need to make sure the error message the user sees is actually formatted with the info we want to provide. Also, we should add more info: all of the args, kwargs, template, etc.
With IPP:
Traceback (most recent call last):
File "/Users/awoodard/ci/parsl/parsl/dataflow/dflow.py", line 187, in handle_update
res = future.result()
File "/Users/awoodard/software/anaconda3/envs/parsl_py36/lib/python3.6/concurrent/futures/_base.py", line 398, in result
return self.__get_result()
File "/Users/awoodard/software/anaconda3/envs/parsl_py36/lib/python3.6/concurrent/futures/_base.py", line 357, in __get_result
raise self._exception
File "/Users/awoodard/software/anaconda3/envs/parsl_py36/lib/python3.6/site-packages/ipyparallel/client/asyncresult.py", line 224, in _resolve_result
raise r
ipyparallel.error.RemoteError: AppBadFormatting()
With threads:
Traceback (most recent call last):
File "/Users/awoodard/ci/parsl/parsl/app/bash.py", line 34, in remote_side_bash_executor
executable = partial_cmdline.format(*args, **kwargs)
IndexError: tuple index out of range
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "test_bash_apps/test_error_codes.py", line 184, in <module>
test_bash_formatting()
File "test_bash_apps/test_error_codes.py", line 76, in test_bash_formatting
f.result()
File "/Users/awoodard/ci/parsl/parsl/dataflow/futures.py", line 117, in result
res = self.parent.result(timeout=timeout)
File "/Users/awoodard/software/anaconda3/envs/parsl_py36/lib/python3.6/concurrent/futures/_base.py", line 405, in result
return self.__get_result()
File "/Users/awoodard/software/anaconda3/envs/parsl_py36/lib/python3.6/concurrent/futures/_base.py", line 357, in __get_result
raise self._exception
File "/Users/awoodard/ci/parsl/parsl/dataflow/dflow.py", line 187, in handle_update
res = future.result()
File "/Users/awoodard/software/anaconda3/envs/parsl_py36/lib/python3.6/concurrent/futures/_base.py", line 398, in result
return self.__get_result()
File "/Users/awoodard/software/anaconda3/envs/parsl_py36/lib/python3.6/concurrent/futures/_base.py", line 357, in __get_result
raise self._exception
File "/Users/awoodard/software/anaconda3/envs/parsl_py36/lib/python3.6/concurrent/futures/thread.py", line 55, in run
result = self.fn(*self.args, **self.kwargs)
File "/Users/awoodard/ci/parsl/parsl/app/bash.py", line 43, in remote_side_bash_executor
raise pe.AppBadFormatting("[{}] App formatting failed during cmd_line resolution: {}".format(func_name, e), None)
parsl.app.errors.AppBadFormatting
The text was updated successfully, but these errors were encountered:
As reported by @madduri.
The error message raised on badly formatted bash apps is not clear. This is slightly better for threads than IPP, but both are not as helpful as they should be. We need to make sure the error message the user sees is actually formatted with the info we want to provide. Also, we should add more info: all of the args, kwargs, template, etc.
With IPP:
With threads:
The text was updated successfully, but these errors were encountered: