Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for “known failures” to transcripts #5394

Open
wants to merge 4 commits into
base: trunk
Choose a base branch
from

Commits on Oct 7, 2024

  1. Configuration menu
    Copy the full SHA
    27073a6 View commit details
    Browse the repository at this point in the history
  2. Add the first “known failure” transcript

    Shows that unisonweb#5337 is _not_ fixed.
    sellout committed Oct 7, 2024
    Configuration menu
    Copy the full SHA
    dc2db62 View commit details
    Browse the repository at this point in the history
  3. Add an :incorrect transcript tag

    This is basically the opposite of `:failure` – it indicates that a
    successful result is incorrect. The correct result may either be an
    error (which will be caught by the transcript runner) or a different
    result then what is currently expected (which won’t be caught by the
    runner, but the appearance of `:incorrect` conveys to the programmer
    that the output.md diff may be an improvement from the previous state).
    sellout committed Oct 7, 2024
    Configuration menu
    Copy the full SHA
    728c2a3 View commit details
    Browse the repository at this point in the history
  4. Add first :incorrect transcript

    Shows that unisonweb#5178 is _not_ fixed.
    sellout committed Oct 7, 2024
    Configuration menu
    Copy the full SHA
    56a2f5c View commit details
    Browse the repository at this point in the history