Notice that it doesn't tell you which file the syntax error is in; the error is thrown from the import statement. This should produce a better error message which tells you which file failed to import, and ideally even continues with the rest of the test suites while registering a failure for the problematic one.
If you have a test suite that can't be imported, for example because of a syntax error, then the error message you get is quite unhelpful:
Notice that it doesn't tell you which file the syntax error is in; the error is thrown from the import statement. This should produce a better error message which tells you which file failed to import, and ideally even continues with the rest of the test suites while registering a failure for the problematic one.