Skip to content

Improve pipe protocol implementation for 'dotnet test' #50630

Closed

Description

@Youssef1313

If you are not doing a follow-up soon, please create a ticket for it so we have less chances of forgetting.

Originally posted by @Evangelink in #50625 (comment)

Activity

  1. Youssef1313 commented on Sep 4, 2025

    @Youssef1313
    MemberAuthor

    It's not only about this specific occurrence. But we should think for every single message, what are the unexpected states of it (either timing of receiving, or data it contains), and have explicit protocol failure messages.

    Also, we should address any TODO comments in Test command.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions