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
When we shutdown h2o as part of a pysparkling shell exit, all kinds of exceptions are logged to the console which can potentially cause the application to unnecessarily warn the user even though the application successfully completed.
{code:java}
exit()
H2O session _sid_833c closed.
/home/H2O/sparkling-water-2.1.16/py/build/dist/h2o_pysparkling_2.1-2.1.16.zip/pysparkling/context.py:151: UserWarning: Stopping H2OContext. (Restarting H2O is not yet fully supported...)
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
File "/opt/pythonz/pythons/CPython-2.7.5/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File "/home/H2O/sparkling-water-2.1.16/py/build/dist/h2o_pysparkling_2.1-2.1.16.zip/pysparkling/context.py", line 140, in
atexit.register(lambda: h2o_context.stop_with_jvm())
File "/home/H2O/sparkling-water-2.1.16/py/build/dist/h2o_pysparkling_2.1-2.1.16.zip/pysparkling/context.py", line 147, in stop_with_jvm
self.stop()
File "/home/H2O/sparkling-water-2.1.16/py/build/dist/h2o_pysparkling_2.1-2.1.16.zip/pysparkling/context.py", line 152, in stop
Initializer.clean_temp_dir()
File "/home/H2O/sparkling-water-2.1.16/py/build/dist/h2o_pysparkling_2.1-2.1.16.zip/pysparkling/initializer.py", line 81, in clean_temp_dir
shutil.rmtree(Initializer.__extracted_jar_dir)
File "/opt/pythonz/pythons/CPython-2.7.5/lib/python2.7/shutil.py", line 239, in rmtree
onerror(os.listdir, path, sys.exc_info())
File "/opt/pythonz/pythons/CPython-2.7.5/lib/python2.7/shutil.py", line 237, in rmtree
names = os.listdir(path)
OSError: [Errno 2] No such file or directory: '/tmp/tmpWCvXCm'
Error in sys.exitfunc:
{code}
The text was updated successfully, but these errors were encountered:
Nidhi Mehta commented: [~accountid:557058:eeeb611c-665e-431d-b442-1f255171db6f] Michal thinks it got introduced here - dae9f3a [SW-539] - new functionality registered on shutdown, but it expects to have enough time to make potentionally expensive cleanup
When we shutdown h2o as part of a pysparkling shell exit, all kinds of exceptions are logged to the console which can potentially cause the application to unnecessarily warn the user even though the application successfully completed.
{code:java}
The text was updated successfully, but these errors were encountered: