Exception reporter bug

[thumbnail]

Brief

discovered in #154, in some cases an exception occur, which are passed into reporter, without filenames. This is expected as the exception sometimes escapes the context where the filename is available (especially in process-in-parallel!).

This triggers a spec-error which hides the initial exception, as shown in the failing CI here: https://circleci.com/gh/nedap/formatting-stack/1818

QA plan

Fixed CI after 3a9c4a7 (revert to see breakage)

Author checklist

• I have QAed the functionality
• The PR has a reasonably reviewable size and a meaningful commit history
• I have run the branch formatter and observed no new/significative warnings
• The build passes
• I have self-reviewed the PR prior to assignment
• Additionally, I have code-reviewed iteratively the PR considering the following aspects in isolation:
  • Correctness
  • Robustness (red paths, failure handling etc)
  • Test coverage
  • Spec coverage
  • Documentation
  • Security
  • Performance
  • Breaking API changes
  • Cross-compatibility (Clojure/ClojureScript)

Reviewer checklist

• I have checked out this branch and reviewed it locally, running it
• I have QAed the functionality
• I have reviewed the PR
• Additionally, I have code-reviewed iteratively the PR considering the following aspects in isolation:
  • Correctness
  • Robustness (red paths, failure handling etc)
  • Test coverage
  • Spec coverage
  • Documentation
  • Security
  • Performance
  • Breaking API changes
  • Cross-compatibility (Clojure/ClojureScript)

[vemv]

u.t/expect?

It would look like overkill atm, but one never knows how tests could grow

[thumbnail]

I tried u.t/expect, but it's a bit hard to use in this case, as it uses meta=. Kept the test as is, can reevaluate when we expand it.

[lennartbuit]

Not intimately familiar with the code, but seems good to me