Closed mikepqr closed 2 years ago
Idea for this: compare the mtime before and after running chrome. If it's changed, assume resume.pdf was written succesfully and log SIGABRT at info level. Then raise chrome --log-level to get rid of its warning.
No longer seeing this in CI or locally, so closing, but may need to reopen.
python resume.py on macOS results in:
This appears to be harmless. resume.pdf is created just fine. But it's not a great UX.