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 block level messages #867

Draft
wants to merge 10 commits into
base: master
Choose a base branch
from
Draft

Commits on Sep 4, 2024

  1. use forked silver

    trktby committed Sep 4, 2024
    Configuration menu
    Copy the full SHA
    175e0c3 View commit details
    Browse the repository at this point in the history
  2. Send BlockReached/ProcessedMessage

    Only labeled blocks are reported.
    BlockProcessedMessages are currently sent when the entire
    subtree rooted in the respective block has finished executing.
    trktby committed Sep 4, 2024
    Configuration menu
    Copy the full SHA
    ecbcb01 View commit details
    Browse the repository at this point in the history
  3. Add parallel branch execution handling

    Use a path id and method names to communicate messages with
    execution paths.
    trktby committed Sep 4, 2024
    Configuration menu
    Copy the full SHA
    33e41a6 View commit details
    Browse the repository at this point in the history
  4. Update silver submodule

    trktby committed Sep 4, 2024
    Configuration menu
    Copy the full SHA
    aca1a0d View commit details
    Browse the repository at this point in the history
  5. Add flag "--generateBlockMessages" to enable block level reporting

    Also fix minor bug causing crashes for empty blocks.
    trktby committed Sep 4, 2024
    Configuration menu
    Copy the full SHA
    2ae38b9 View commit details
    Browse the repository at this point in the history
  6. Configuration menu
    Copy the full SHA
    6b993ac View commit details
    Browse the repository at this point in the history
  7. Add emission of BlockFailureMessages, clean up a bit

    There were issues with the --numErrorsToReport option.
    PathProcessedMessages may have emitted false results since the result of
    the last explored block did not match the expected path result. It was
    success if the last explored block succeeded, while it was expected to
    be Failure if any block on the path failed. Now the message should
    merely signify that the path has finished.
    trktby committed Sep 4, 2024
    Configuration menu
    Copy the full SHA
    5182057 View commit details
    Browse the repository at this point in the history
  8. Configuration menu
    Copy the full SHA
    fafb247 View commit details
    Browse the repository at this point in the history
  9. Configuration menu
    Copy the full SHA
    a35d3ee View commit details
    Browse the repository at this point in the history
  10. Whitespace fix

    trktby committed Sep 4, 2024
    Configuration menu
    Copy the full SHA
    b4b3ddc View commit details
    Browse the repository at this point in the history