pabot --pabotlib --resourcefile common_utilities/common_actions/login.resource smoke_tests
Traceback (most recent call last):
File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/runpy.py", line 196, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/runpy.py", line 86, in _run_code
exec(code, run_globals)
File "/Users/a.c.chen/Library/Python/3.10/lib/python/site-packages/pabot/pabotlib.py", line 572, in
_PabotLib(sys.argv[1]), host=sys.argv[2], port=sys.argv[3], allow_stop=True
File "/Users/a.c.chen/Library/Python/3.10/lib/python/site-packages/pabot/pabotlib.py", line 55, in init
self._values = self._parse_values(resourcefile)
File "/Users/a.c.chen/Library/Python/3.10/lib/python/site-packages/pabot/pabotlib.py", line 66, in _parse_values
conf.read(resourcefile)
File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/configparser.py", line 698, in read
self._read(fp, filename)
File "/Library/Frameworks/Python.framework/Versions/3.10/lib/python3.10/configparser.py", line 1086, in _read
raise MissingSectionHeaderError(fpname, lineno, line)
configparser.MissingSectionHeaderError: File contains no section headers.
file: 'common_utilities/common_actions/login.resource', line: 1
'*** Settings ***\n'
[ERROR] EXCEPTION RAISED DURING PABOT EXECUTION
[ERROR] PLEASE CONSIDER REPORTING THIS ISSUE TO https://github.com/mkorpela/pabot/issues
Pabot: 2.13.0
Python: 3.10.7 (v3.10.7:6cc6b13308, Sep 5 2022, 14:02:52) [Clang 13.0.0 (clang-1300.0.29.30)]
Robot Framework: 5.0.1
Stopping PabotLib process
Could not connect to PabotLib - assuming stopped already
Total testing: 0.0 seconds
Elapsed time: 30.91 seconds
Traceback (most recent call last):
File "/Users/a.c.chen/Library/Python/3.10/bin/pabot", line 8, in
sys.exit(main())
File "/Users/a.c.chen/Library/Python/3.10/lib/python/site-packages/pabot/pabot.py", line 1850, in main
return sys.exit(main_program(args))
File "/Users/a.c.chen/Library/Python/3.10/lib/python/site-packages/pabot/pabot.py", line 1879, in main_program
_initialize_queue_index()
File "/Users/a.c.chen/Library/Python/3.10/lib/python/site-packages/pabot/pabot.py", line 1814, in _initialize_queue_index
raise RuntimeError("Can not connect to PabotLib at %s" % _PABOTLIBURI)
RuntimeError: Can not connect to PabotLib at 127.0.0.1:8270
This issue shows on Linux OS.
same issue on Linux
[ERROR] EXCEPTION RAISED DURING PABOT EXECUTION
[ERROR] PLEASE CONSIDER REPORTING THIS ISSUE TO https://github.com/mkorpela/pabot/issues
Pabot: 2.15.0
Python: 3.8.0 (default, Dec 9 2021, 17:53:27)
[GCC 8.4.0]
Robot Framework: 4.1.3
Stopping PabotLib process
Could not connect to PabotLib - assuming stopped already
Total testing: 48.20 seconds
Elapsed time: 32.4 seconds
Traceback (most recent call last):
File "/var/lib/jenkins/workspace/env/bin/pabot", line 8, in
sys.exit(main())
File "/var/lib/jenkins/workspace/env/lib/python3.8/site-packages/pabot/pabot.py", line 1875, in main
return sys.exit(main_program(args))
File "/var/lib/jenkins/workspace/env/lib/python3.8/site-packages/pabot/pabot.py", line 1918, in main_program
_parallel_execute(
File "/var/lib/jenkins/workspace/env/lib/python3.8/site-packages/pabot/pabot.py", line 1330, in _parallel_execute
dynamic_items = _get_dynamically_created_execution_items(
File "/var/lib/jenkins/workspace/env/lib/python3.8/site-packages/pabot/pabot.py", line 1848, in _get_dynamically_created_execution_items
new_suites = plib.run_keyword("get_added_suites", [], {})
File "/var/lib/jenkins/workspace/env/lib/python3.8/site-packages/robot/libraries/Remote.py", line 116, in run_keyword
result = RemoteResult(self._client.run_keyword(name, args, kwargs))
File "/var/lib/jenkins/workspace/env/lib/python3.8/site-packages/robot/libraries/Remote.py", line 279, in run_keyword
raise RuntimeError(message)
RuntimeError: Connection to remote server broken: [Errno 111] Connection refused
Hello, I'm also facing this problem. Have any of you figured it out yet? I'd be grateful for your guidance on how to solve it.
Hi!
This appears to be the same "connection refused" issue as in #546, so I’m closing this one.
We can reopen it if needed — especially if someone can provide the additional details requested in #546.
mkorpela
