builderrors should handle PathConfig exceptions
See https://code.gramener.com/barc/BARC-Advertising/-/jobs/54090
It reports the following traceback:
Traceback (most recent call last):
File "/monitor/builderrorutils.py", line 176, in <module>
globals()[sys.argv[1]](*sys.argv[2:])
File "/monitor/builderrorutils.py", line 74, in yamllint
config = gramex.config.PathConfig(os.path.join(os.path.abspath(path), 'gramex.yaml')) or {}
File "/gramex/gramex/config.py", line 572, in __init__
self.__pos__()
File "/gramex/gramex/config.py", line 595, in __pos__
self.__info__.imports = load_imports(self, source=path, warn=self.__info__.warn)
File "/gramex/gramex/config.py", line 515, in load_imports
paths = root.glob(paths) if '*' in paths else [Path(paths)]
File "/opt/conda/lib/python2.7/site-packages/pathlib.py", line 936, in __new__
self = cls._from_parts(args, init=False)
File "/opt/conda/lib/python2.7/site-packages/pathlib.py", line 613, in _from_parts
drv, root, parts = self._parse_args(args)
File "/opt/conda/lib/python2.7/site-packages/pathlib.py", line 606, in _parse_args
return cls._flavour.parse_parts(parts)
File "/opt/conda/lib/python2.7/site-packages/pathlib.py", line 93, in parse_parts
parsed.append(intern(rel))
TypeError: can't intern subclass of string
If this is caused by an invalid YAML config, this should report an error.