Pod Status: Succeeded
Initialized: True
Ready: False
ContainersReady: False
PodScheduled: True
Traceback (most recent call last):
  File "/venv/lib/python3.9/runpy.py", line 239, in _get_main_module_details
    return _get_module_details(main_name)
  File "/venv/lib/python3.9/runpy.py", line 141, in _get_module_details
    raise error("No module named %s" % mod_name)
ImportError: No module named __main__

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/venv/lib/python3.9/runpy.py", line 190, in _run_module_as_main
    mod_name, mod_spec, code = _get_main_module_details(_Error)
  File "/venv/lib/python3.9/runpy.py", line 242, in _get_main_module_details
    raise error("can't find %r module in %r" %
runpy._Error: can't find '__main__' module in '/data/onesis/kt4/job_results/o1871924516071014400.str'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/venv/lib/python3.9/runpy.py", line 193, in _run_module_as_main
    sys.exit(msg)
SystemExit: /venv/bin/python: can't find '__main__' module in '/data/onesis/kt4/job_results/o1871924516071014400.str'
>>> 
