You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was just about to open this same issue, after creating a transcript for #5453.
While we don’t want exceptions to happen, we should at least be able to add exceptional transcripts to unison-src/transcripts/errors, and have them pass. But we don’t catch the exceptions, and so EasyTest just yells “EXCEPTION!!!”.
Maybe we can get partial output, but I don’t think we want to have exceptions as something permitted by :error (or even :bug), as we would never want them to be intentional.
This causes an exception (it shouldn’t, but it should error)
```unison :error
ability MyAbility g where get : '{MyAbility {g}} ()```
The proper declaration is:
```unisonability MyAbility g where get : '{MyAbility g} ()```
So, my expectation is that putting that in transcripts/errors would result in the transcript passing because the stanza has an exception, but once the exception is fixed, the transcript will fail, because the stanza will then error as it is expected to. At which point, we move the transcript to transcripts/idempotent, close the ticket, and smile because a bug is fixed.
This transcript
crashes with this error
but doesn't produce any transcript output.
The text was updated successfully, but these errors were encountered: