(In reply to Jorg K (GMT+2) from comment #16) > What about the `mach clobber` from bug 1578198? I believe this bug is a separate issue from the `clobber` one (though stem from similar places). I'm still confused about why it started happening. Jorg, you are running from comm-central right? It's possible the Python detection for commands isn't working quite right in that context. Can you verify the version of Python that is being run by adding: ``` import sys print(sys.version_info) ``` somewhere before you see the traceback? I would expect it to be 2.7 for both `eslint` and `clang-format`. If it's saying anything else, that's the root issue and you can ignore all the other errors you see.
Bug 1577826 Comment 17 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Jorg K (GMT+2) from comment #16) > What about the `mach clobber` from bug 1578198? I believe this bug is a separate issue from the `clobber` one (though stem from similar places). I'm still confused about why this one started happening (but have decent understanding on the clobber one). Jorg, you are running from comm-central right? It's possible the Python detection for commands isn't working quite right in that context. Can you verify the version of Python that is being run by adding: ``` import sys print(sys.version_info) ``` somewhere before you see the traceback? I would expect it to be 2.7 for both `eslint` and `clang-format`. If it's saying anything else, that's the root issue and you can ignore all the other errors you see.