Skip to content

Fix confusing test results for known-broken jobs #2117

Open

Description

@dagood

E.g. { experiment: systemcrypto, os: windows, arch: amd64, config: test, distro: '2019', broken: true }

Currently the known-broken jobs still submit test results to AzDO, and the AzDO test viewer doesn't indicate that the tests were expected to fail. This should be fixed to avoid misleading results and wasting time on known failures.

A simple fix that preserves the data and would probably work well enough would be to prepend "(BROKEN)" to the job name, because it shows up in the test viewer and has to be expanded before seeing any of the misleading failures.

Activity

  1. dagood commented on Mar 18, 2026

    @dagood
    MemberAuthor

    We don't have any jobs marked broken since:

    So, might need to temporarily mark a working job as broken and add a simulated test failure to test this work in a draft PR.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions