<?xml version="1.0" encoding="utf-8"?>
<root>
  <!-- 
    Microsoft ResX Schema 
    
    Version 2.0
    
    The primary goals of this format is to allow a simple XML format 
    that is mostly human readable. The generation and parsing of the 
    various data types are done through the TypeConverter classes 
    associated with the data types.
    
    Example:
    
    ... ado.net/XML headers & schema ...
    <resheader name="resmimetype">text/microsoft-resx</resheader>
    <resheader name="version">2.0</resheader>
    <resheader name="reader">System.Resources.ResXResourceReader, System.Windows.Forms, ...</resheader>
    <resheader name="writer">System.Resources.ResXResourceWriter, System.Windows.Forms, ...</resheader>
    <data name="Name1"><value>this is my long string</value><comment>this is a comment</comment></data>
    <data name="Color1" type="System.Drawing.Color, System.Drawing">Blue</data>
    <data name="Bitmap1" mimetype="application/x-microsoft.net.object.binary.base64">
        <value>[base64 mime encoded serialized .NET Framework object]</value>
    </data>
    <data name="Icon1" type="System.Drawing.Icon, System.Drawing" mimetype="application/x-microsoft.net.object.bytearray.base64">
        <value>[base64 mime encoded string representing a byte array form of the .NET Framework object]</value>
        <comment>This is a comment</comment>
    </data>
                
    There are any number of "resheader" rows that contain simple 
    name/value pairs.
    
    Each data row contains a name, and value. The row also contains a 
    type or mimetype. Type corresponds to a .NET class that support 
    text/value conversion through the TypeConverter architecture. 
    Classes that don't support this are serialized and stored with the 
    mimetype set.
    
    The mimetype is used for serialized objects, and tells the 
    ResXResourceReader how to depersist the object. This is currently not 
    extensible. For a given mimetype the value must be set accordingly:
    
    Note - application/x-microsoft.net.object.binary.base64 is the format 
    that the ResXResourceWriter will generate, however the reader can 
    read any of the formats listed below.
    
    mimetype: application/x-microsoft.net.object.binary.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Binary.BinaryFormatter
            : and then encoded with base64 encoding.
    
    mimetype: application/x-microsoft.net.object.soap.base64
    value   : The object must be serialized with 
            : System.Runtime.Serialization.Formatters.Soap.SoapFormatter
            : and then encoded with base64 encoding.

    mimetype: application/x-microsoft.net.object.bytearray.base64
    value   : The object must be serialized into a byte array 
            : using a System.ComponentModel.TypeConverter
            : and then encoded with base64 encoding.
    -->
  <xsd:schema id="root" xmlns="" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:msdata="urn:schemas-microsoft-com:xml-msdata">
    <xsd:import namespace="http://www.w3.org/XML/1998/namespace" />
    <xsd:element name="root" msdata:IsDataSet="true">
      <xsd:complexType>
        <xsd:choice maxOccurs="unbounded">
          <xsd:element name="metadata">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" />
              </xsd:sequence>
              <xsd:attribute name="name" use="required" type="xsd:string" />
              <xsd:attribute name="type" type="xsd:string" />
              <xsd:attribute name="mimetype" type="xsd:string" />
              <xsd:attribute ref="xml:space" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="assembly">
            <xsd:complexType>
              <xsd:attribute name="alias" type="xsd:string" />
              <xsd:attribute name="name" type="xsd:string" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="data">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
                <xsd:element name="comment" type="xsd:string" minOccurs="0" msdata:Ordinal="2" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" msdata:Ordinal="1" />
              <xsd:attribute name="type" type="xsd:string" msdata:Ordinal="3" />
              <xsd:attribute name="mimetype" type="xsd:string" msdata:Ordinal="4" />
              <xsd:attribute ref="xml:space" />
            </xsd:complexType>
          </xsd:element>
          <xsd:element name="resheader">
            <xsd:complexType>
              <xsd:sequence>
                <xsd:element name="value" type="xsd:string" minOccurs="0" msdata:Ordinal="1" />
              </xsd:sequence>
              <xsd:attribute name="name" type="xsd:string" use="required" />
            </xsd:complexType>
          </xsd:element>
        </xsd:choice>
      </xsd:complexType>
    </xsd:element>
  </xsd:schema>
  <resheader name="resmimetype">
    <value>text/microsoft-resx</value>
  </resheader>
  <resheader name="version">
    <value>2.0</value>
  </resheader>
  <resheader name="reader">
    <value>System.Resources.ResXResourceReader, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <resheader name="writer">
    <value>System.Resources.ResXResourceWriter, System.Windows.Forms, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</value>
  </resheader>
  <data name="AnnotationsOptionDescription" xml:space="preserve">
    <value>Enable or disable Azure DevOps failure annotations ('on' or 'off'). Defaults to 'on'. Requires '--report-azdo'.</value>
    <comment>{Locked="on"}{Locked="off"}{Locked="--report-azdo"}</comment>
  </data>
  <data name="ArtifactUploadOptionsRequireUploadArtifacts" xml:space="preserve">
    <value>'--report-azdo-upload-artifact-include', '--report-azdo-upload-artifact-exclude', and '--report-azdo-upload-artifact-name' require '--report-azdo-upload-artifacts' to be set to a value other than 'off'.</value>
    <comment>{Locked="--report-azdo-upload-artifact-include"}{Locked="--report-azdo-upload-artifact-exclude"}{Locked="--report-azdo-upload-artifact-name"}{Locked="--report-azdo-upload-artifacts"}{Locked="off"}</comment>
  </data>
  <data name="ArtifactUploadRequiresTfBuildWarning" xml:space="preserve">
    <value>Azure DevOps artifact upload was requested, but TF_BUILD is not set to 'true'; skipping Azure DevOps artifact upload and build tags.</value>
    <comment>{Locked="TF_BUILD"}{Locked="true"}</comment>
  </data>
  <data name="AzureDevOpsAnnotationsRequiresAzureDevOps" xml:space="preserve">
    <value>'--report-azdo-annotations' requires '--report-azdo' to be enabled</value>
    <comment>{Locked="--report-azdo-annotations"}{Locked="--report-azdo"}</comment>
  </data>
  <data name="AzureDevOpsDemoteKnownFlakyRequiresAzureDevOps" xml:space="preserve">
    <value>'--report-azdo-demote-known-flaky' requires '--report-azdo' to be enabled</value>
    <comment>{Locked="--report-azdo-demote-known-flaky"}{Locked="--report-azdo"}</comment>
  </data>
  <data name="AzureDevOpsDemoteKnownFlakyRequiresFlakyHistory" xml:space="preserve">
    <value>'--report-azdo-demote-known-flaky' requires '--report-azdo-flaky-history' to be enabled</value>
    <comment>{Locked="--report-azdo-demote-known-flaky"}{Locked="--report-azdo-flaky-history"}</comment>
  </data>
  <data name="AzureDevOpsFlakyHistoryRequiresAzureDevOps" xml:space="preserve">
    <value>'--report-azdo-flaky-history' requires '--report-azdo' to be enabled</value>
    <comment>{Locked="--report-azdo-flaky-history"}{Locked="--report-azdo"}</comment>
  </data>
  <data name="AzureDevOpsGroupsRequiresAzureDevOps" xml:space="preserve">
    <value>'--report-azdo-groups' requires '--report-azdo' to be enabled</value>
    <comment>{Locked="--report-azdo-groups"}{Locked="--report-azdo"}</comment>
  </data>
  <data name="AzureDevOpsLivePublishingAttachmentsDropped" xml:space="preserve">
    <value>Azure DevOps live publishing could not upload {0} attachment(s); they will be missing from the Azure DevOps test run.</value>
    <comment>{0} is the number of attachments that could not be uploaded.</comment>
  </data>
  <data name="AzureDevOpsLivePublishingCompleteRunFailed" xml:space="preserve">
    <value>Azure DevOps live publishing failed to complete the test run.</value>
  </data>
  <data name="AzureDevOpsLivePublishingCreateRunFailed" xml:space="preserve">
    <value>Azure DevOps live publishing failed to create the test run.</value>
  </data>
  <data name="AzureDevOpsLivePublishingFailedToDeleteCoordinationFile" xml:space="preserve">
    <value>Azure DevOps live publishing failed to delete coordination file</value>
  </data>
  <data name="AzureDevOpsLivePublishingFailedToReadCoordinationFile" xml:space="preserve">
    <value>Azure DevOps live publishing failed to read coordination file</value>
  </data>
  <data name="AzureDevOpsLivePublishingFailedToWriteCoordinationFile" xml:space="preserve">
    <value>Azure DevOps live publishing failed to write coordination file</value>
  </data>
  <data name="AzureDevOpsLivePublishingFinalizeWaitTimedOut" xml:space="preserve">
    <value>Azure DevOps live publishing timed out after {0} waiting for {1} participant file(s); finalizing the run anyway.</value>
    <comment>{0} is the finalize wait timeout. {1} is the number of participant files still pending.</comment>
  </data>
  <data name="AzureDevOpsLivePublishingHttpError" xml:space="preserve">
    <value>Azure DevOps REST API request failed with status code {0}. Response: {1}</value>
    <comment>{0} is the HTTP status code. {1} is the response body. {Locked="REST API"}</comment>
  </data>
  <data name="AzureDevOpsLivePublishingInvalidResponse" xml:space="preserve">
    <value>Azure DevOps REST API returned an unexpected response payload.</value>
    <comment>{Locked="REST API"}</comment>
  </data>
  <data name="AzureDevOpsLivePublishingMissingConfiguration" xml:space="preserve">
    <value>'--publish-azdo-test-results' was set, but Azure DevOps live publishing is disabled because the following environment variables are missing or invalid: {0}.</value>
    <comment>{0} is the comma-separated list of missing or invalid environment variables. {Locked="--publish-azdo-test-results"}{Locked="TF_BUILD=true"}{Locked="SYSTEM_TEAMPROJECT"}{Locked="SYSTEM_ACCESSTOKEN"}{Locked="BUILD_BUILDID"}</comment>
  </data>
  <data name="AzureDevOpsLivePublishingMissingRunIdFile" xml:space="preserve">
    <value>Azure DevOps live publishing could not locate azdo-runid.&lt;buildId&gt;.json for the shared run.</value>
    <comment>{Locked="azdo-runid.&lt;buildId&gt;.json"}</comment>
  </data>
  <data name="AzureDevOpsLivePublishingPublishResultsFailed" xml:space="preserve">
    <value>Azure DevOps live publishing failed to publish test results.</value>
  </data>
  <data name="AzureDevOpsLivePublishingRequestFailed" xml:space="preserve">
    <value>Azure DevOps REST API request failed after all retries.</value>
    <comment>{Locked="REST API"}</comment>
  </data>
  <data name="AzureDevOpsLivePublishingResultAttachmentFailed" xml:space="preserve">
    <value>Azure DevOps live publishing failed to upload a test result attachment.</value>
  </data>
  <data name="AzureDevOpsLivePublishingResultIdParseFailedWarning" xml:space="preserve">
    <value>Azure DevOps live publishing accepted a batch of test results but could not parse the assigned result IDs; result-level attachments for this batch will be skipped.</value>
  </data>
  <data name="AzureDevOpsLivePublishingResultMapHandoffFailed" xml:space="preserve">
    <value>Azure DevOps live publishing failed to update the result map handoff.</value>
  </data>
  <data name="AzureDevOpsLivePublishingResultsDropped" xml:space="preserve">
    <value>Azure DevOps live publishing could not publish {0} test result(s); they will be missing from the Azure DevOps test run.</value>
    <comment>{0} is the number of test results that could not be published.</comment>
  </data>
  <data name="AzureDevOpsLivePublishingRunAttachmentFailed" xml:space="preserve">
    <value>Azure DevOps live publishing failed to upload a test run attachment.</value>
  </data>
  <data name="AzureDevOpsLivePublishingRunCreated" xml:space="preserve">
    <value>Azure DevOps live publishing is streaming results to test run {0}, which you can follow while the tests are still running at {1}. The build's Tests tab lists the run once it completes.</value>
    <comment>{0} is the Azure DevOps test run id. {1} is the URL of the test run.</comment>
  </data>
  <data name="AzureDevOpsLivePublishingRunIdFileMismatch" xml:space="preserve">
    <value>Azure DevOps live publishing found an azdo-runid.&lt;buildId&gt;.json file for a different Azure DevOps project.</value>
    <comment>{Locked="azdo-runid.&lt;buildId&gt;.json"}</comment>
  </data>
  <data name="AzureDevOpsLivePublishingRunIdHandoffFailed" xml:space="preserve">
    <value>Azure DevOps live publishing failed to update the test run id handoff.</value>
  </data>
  <data name="AzureDevOpsLivePublishingRunLeftInProgress" xml:space="preserve">
    <value>The Azure DevOps test run was not marked as completed and may not appear in the build's Tests tab.</value>
  </data>
  <data name="AzureDevOpsLivePublishingTimeoutErrorMessage" xml:space="preserve">
    <value>Timeout</value>
  </data>
  <data name="AzureDevOpsLivePublishingTimeoutErrorMessageWithReason" xml:space="preserve">
    <value>Timeout: {0}</value>
    <comment>{0} is the timeout reason.</comment>
  </data>
  <data name="AzureDevOpsLivePublishingWarningDisplayFailed" xml:space="preserve">
    <value>Azure DevOps live publishing could not display a warning on the output device.</value>
  </data>
  <data name="AzureDevOpsQuarantineFileRequiresAzureDevOps" xml:space="preserve">
    <value>'--report-azdo-quarantine-file' requires '--report-azdo' to be enabled</value>
    <comment>{Locked="--report-azdo-quarantine-file"}{Locked="--report-azdo"}</comment>
  </data>
  <data name="AzureDevOpsReportSeverityRequiresAzureDevOps" xml:space="preserve">
    <value>'--report-azdo-severity' requires '--report-azdo' to be enabled</value>
    <comment>{Locked="--report-azdo-severity"}{Locked="--report-azdo"}</comment>
  </data>
  <data name="AzureDevOpsStackFrameFilterRequiresAzureDevOps" xml:space="preserve">
    <value>'--report-azdo-stackframe-filter' requires '--report-azdo' to be enabled</value>
    <comment>{Locked="--report-azdo-stackframe-filter"}{Locked="--report-azdo"}</comment>
  </data>
  <data name="AzureDevOpsSummaryRequiresAzureDevOps" xml:space="preserve">
    <value>'--report-azdo-summary' requires '--report-azdo' to be enabled</value>
    <comment>{Locked="--report-azdo-summary"}{Locked="--report-azdo"}</comment>
  </data>
  <data name="DemoteKnownFlakyOptionDescription" xml:space="preserve">
    <value>Demote failures with an Azure DevOps flaky history of at least {0}% in the selected window to warnings.</value>
    <comment>{0} is the percentage threshold (e.g., 25).</comment>
  </data>
  <data name="Description" xml:space="preserve">
    <value>Azure DevOps report generator to write errors to the output in a way that Azure DevOps understands.</value>
  </data>
  <data name="DisplayName" xml:space="preserve">
    <value>Azure DevOps report generator</value>
  </data>
  <data name="FlakyHistoryFailureAnnotation" xml:space="preserve">
    <value>[flaky: failed {0}/{1} in last {2}d]</value>
    <comment>{0} is the failure count. {1} is the total run count. {2} is the history window in days. {Locked="[flaky: failed {0}/{1} in last {2}d]"}</comment>
  </data>
  <data name="FlakyHistoryLoadFailedWarning" xml:space="preserve">
    <value>Unable to load Azure DevOps flaky history. Continuing without history annotations. {0}</value>
    <comment>{0} is the exception message. {Locked="--report-azdo-flaky-history"}</comment>
  </data>
  <data name="FlakyHistoryLoadTimedOutInfo" xml:space="preserve">
    <value>Azure DevOps flaky history did not finish loading within {0} seconds. Continuing without history annotations.</value>
    <comment>{0} is the timeout in seconds.</comment>
  </data>
  <data name="FlakyHistoryMissingEnvironmentWarning" xml:space="preserve">
    <value>Azure DevOps flaky history was requested but the required Azure DevOps environment variables are missing. Continuing without history annotations.</value>
    <comment>{Locked="--report-azdo-flaky-history"}{Locked="TF_BUILD"}{Locked="SYSTEM_TEAMPROJECT"}{Locked="SYSTEM_ACCESSTOKEN"}</comment>
  </data>
  <data name="FlakyHistoryOptionDescription" xml:space="preserve">
    <value>Query Azure DevOps test result history for the past N days (1-90) and annotate reported failures with flakiness context.</value>
  </data>
  <data name="FlakyHistoryRegressionAnnotation" xml:space="preserve">
    <value>[REGRESSION]</value>
    <comment>{Locked="[REGRESSION]"}</comment>
  </data>
  <data name="FlakyHistoryRunsCappedInfo" xml:space="preserve">
    <value>Azure DevOps flaky history returned {0} runs. Only the first {1} runs will be inspected.</value>
    <comment>{0} is the number of runs returned. {1} is the maximum number of runs to inspect.</comment>
  </data>
  <data name="FlakyHistoryResultsPagingStoppedWarning" xml:space="preserve">
    <value>Azure DevOps flaky history for run '{0}' exceeded {1} pages or returned an unchanged continuation token. Remaining results will be ignored.</value>
    <comment>{0} is the Azure DevOps run URL. {1} is the maximum number of pages.</comment>
  </data>
  <data name="GroupsOptionDescription" xml:space="preserve">
    <value>Enable or disable per-assembly Azure DevOps log groups ('on' or 'off'). Defaults to 'off'. Requires '--report-azdo'.</value>
    <comment>{Locked="on"}{Locked="off"}{Locked="--report-azdo"}</comment>
  </data>
  <data name="InvalidArtifactUploadGlob" xml:space="preserve">
    <value>Invalid glob pattern {0}.</value>
    <comment>{0} is the invalid glob pattern.</comment>
  </data>
  <data name="InvalidArtifactUploadMode" xml:space="preserve">
    <value>Invalid artifact upload mode {0}.</value>
    <comment>{0} is the invalid artifact upload mode.</comment>
  </data>
  <data name="InvalidFlakyHistoryDays" xml:space="preserve">
    <value>Invalid value '{0}' for '--report-azdo-flaky-history'. Provide an integer between 1 and 90.</value>
    <comment>{0} is the invalid value. {Locked="--report-azdo-flaky-history"}</comment>
  </data>
  <data name="InvalidOnOffValue" xml:space="preserve">
    <value>Invalid value '{0}'. Valid values are 'on' and 'off'.</value>
    <comment>{Locked="on"}{Locked="off"}</comment>
  </data>
  <data name="InvalidSeverity" xml:space="preserve">
    <value>Invalid option {0}.</value>
    <comment>{0} is the invalid option value.</comment>
  </data>
  <data name="InvalidStackFrameFilterRegex" xml:space="preserve">
    <value>Invalid '--report-azdo-stackframe-filter' regex '{0}': {1}</value>
    <comment>{0} is the regex pattern. {1} is the validation error message. {Locked="--report-azdo-stackframe-filter"}</comment>
  </data>
  <data name="LogGroupHeader" xml:space="preserve">
    <value>Tests: {0}</value>
    <comment>{0} is the test assembly name and target framework, e.g. 'MSTest.UnitTests (net9.0)'. This text is the collapsible Azure DevOps log group header.</comment>
  </data>
  <data name="NoFailureMessageFallback" xml:space="preserve">
    <value>Test failed without an additional message.</value>
  </data>
  <data name="OptionDescription" xml:space="preserve">
    <value>Enable Azure DevOps report generator to write errors to the output in a way that Azure DevOps understands.</value>
  </data>
  <data name="PublishAzdoRunNameOptionDescription" xml:space="preserve">
    <value>Custom Azure DevOps test run name for live test-result publishing.</value>
  </data>
  <data name="PublishAzdoRunNameRequiresPublishAzdoTestResults" xml:space="preserve">
    <value>'--publish-azdo-run-name' requires '--publish-azdo-test-results' to be enabled</value>
    <comment>{Locked="--publish-azdo-run-name"}{Locked="--publish-azdo-test-results"}</comment>
  </data>
  <data name="PublishAzdoTestResultsOptionDescription" xml:space="preserve">
    <value>Publish test results to an Azure DevOps test run as tests complete. The run is listed in the build's Tests tab once the test session finishes.</value>
  </data>
  <data name="QuarantinedAnnotation" xml:space="preserve">
    <value>[quarantined]</value>
    <comment>{Locked="[quarantined]"}</comment>
  </data>
  <data name="QuarantineFileLoadFailedWarning" xml:space="preserve">
    <value>Unable to load Azure DevOps quarantine file '{0}'. Continuing without quarantine awareness. {1}</value>
    <comment>{0} is the quarantine file path. {1} is the exception message. {Locked="--report-azdo-quarantine-file"}</comment>
  </data>
  <data name="QuarantineFileMissingWarning" xml:space="preserve">
    <value>Azure DevOps quarantine file '{0}' does not exist. Continuing without quarantine awareness.</value>
    <comment>{0} is the quarantine file path.</comment>
  </data>
  <data name="QuarantineFileOptionDescription" xml:space="preserve">
    <value>Path to a text file that lists quarantined test fully qualified names or glob patterns. Matching failures are reported as warnings.</value>
  </data>
  <data name="QuarantinePatternTooLongWarning" xml:space="preserve">
    <value>Azure DevOps quarantine pattern exceeds the {0} character limit and will be ignored.</value>
    <comment>{0} is the maximum character limit.</comment>
  </data>
  <data name="QuarantinePatternsCappedWarning" xml:space="preserve">
    <value>Azure DevOps quarantine file contains more than {0} patterns. Remaining patterns will be ignored.</value>
    <comment>{0} is the maximum pattern count.</comment>
  </data>
  <data name="SeverityOptionDescription" xml:space="preserve">
    <value>Severity to use for the reported event. Options are: error (default) and warning.</value>
    <comment>{Locked="error"}{Locked="warning"}</comment>
  </data>
  <data name="StackFrameFilterOptionDescription" xml:space="preserve">
    <value>Additional regex patterns (matched against the fully-qualified type prefix of each stack frame) that should be skipped when looking for the user's call site to annotate. Repeatable; up to {0} patterns. Compiled with a {1}ms match timeout. Additive to the extension's built-in MSTest assertion-implementation prefixes.</value>
    <comment>{0} is the maximum allowed pattern count. {1} is the per-match timeout in milliseconds. {Locked="MSTest"}</comment>
  </data>
  <data name="StackFrameFilterTooManyRegexes" xml:space="preserve">
    <value>'--report-azdo-stackframe-filter' accepts at most {0} patterns.</value>
    <comment>{0} is the maximum pattern count. {Locked="--report-azdo-stackframe-filter"}</comment>
  </data>
  <data name="SummaryOptionDescription" xml:space="preserve">
    <value>Write a Markdown job summary at the end of the test run and upload it via '##vso[task.uploadsummary]'. An optional file path argument overrides the default location ('{testResultsDir}/azdo-summary-{assembly}-{tfm}-{arch}.md'). Requires '--report-azdo'.</value>
    <comment>{Locked="Markdown"}{Locked="##vso[task.uploadsummary]"}{Locked="{testResultsDir}/azdo-summary-{assembly}-{tfm}-{arch}.md"}{Locked="--report-azdo"}</comment>
  </data>
  <data name="SummaryRequiresTfBuildWarning" xml:space="preserve">
    <value>Azure DevOps job summary was requested, but TF_BUILD is not set to 'true'; skipping summary emission.</value>
    <comment>{Locked="TF_BUILD"}{Locked="true"}</comment>
  </data>
  <data name="SummaryWriteFailedWarning" xml:space="preserve">
    <value>Failed to write Azure DevOps summary file '{0}': {1}</value>
    <comment>{0} is the summary file path. {1} is the error message.</comment>
  </data>
  <data name="UploadArtifactExcludeOptionDescription" xml:space="preserve">
    <value>Exclude files from Azure DevOps artifact upload using glob patterns relative to the test results directory.</value>
  </data>
  <data name="UploadArtifactIncludeOptionDescription" xml:space="preserve">
    <value>Include files in Azure DevOps artifact upload using glob patterns relative to the test results directory. Defaults to '**/*'.</value>
    <comment>{Locked="**/*"}</comment>
  </data>
  <data name="UploadArtifactNameOptionDescription" xml:space="preserve">
    <value>Override the Azure DevOps artifact container name. Defaults to 'TestResults_{assemblyName}_{tfm}'.</value>
    <comment>{Locked="TestResults_{assemblyName}_{tfm}"}</comment>
  </data>
  <data name="UploadArtifactsOptionDescription" xml:space="preserve">
    <value>Upload test result files and/or add build tags to Azure DevOps. Options are: off (default), tags-only, files, and all.</value>
    <comment>{Locked="off"}{Locked="tags-only"}{Locked="files"}{Locked="all"}</comment>
  </data>
  <data name="AzureDevOpsSlowTestHistoryRequiresAzureDevOps" xml:space="preserve">
    <value>'--report-azdo-slow-test-history' requires '--report-azdo' to be enabled</value>
    <comment>{Locked="--report-azdo-slow-test-history"}{Locked="--report-azdo"}</comment>
  </data>
  <data name="AzureDevOpsSlowTestHistoryMinSampleRequiresSlowTestHistory" xml:space="preserve">
    <value>'--report-azdo-slow-test-history-min-sample' requires '--report-azdo-slow-test-history' to be enabled</value>
    <comment>{Locked="--report-azdo-slow-test-history-min-sample"}{Locked="--report-azdo-slow-test-history"}</comment>
  </data>
  <data name="AzureDevOpsSlowTestHistoryMultiplierRequiresSlowTestHistory" xml:space="preserve">
    <value>'--report-azdo-slow-test-history-multiplier' requires '--report-azdo-slow-test-history' to be enabled</value>
    <comment>{Locked="--report-azdo-slow-test-history-multiplier"}{Locked="--report-azdo-slow-test-history"}</comment>
  </data>
  <data name="InvalidSlowTestHistoryDays" xml:space="preserve">
    <value>Invalid value '{0}' for '--report-azdo-slow-test-history'. Provide an integer between 1 and 90.</value>
    <comment>{0} is the invalid value. {Locked="--report-azdo-slow-test-history"}</comment>
  </data>
  <data name="InvalidSlowTestHistoryMinSample" xml:space="preserve">
    <value>Invalid value '{0}' for '--report-azdo-slow-test-history-min-sample'. Provide an integer greater than or equal to 1.</value>
    <comment>{0} is the invalid value. {Locked="--report-azdo-slow-test-history-min-sample"}</comment>
  </data>
  <data name="InvalidSlowTestHistoryMultiplier" xml:space="preserve">
    <value>Invalid value '{0}' for '--report-azdo-slow-test-history-multiplier'. Provide a number greater than 0 and at most 10000.</value>
    <comment>{0} is the invalid value. {Locked="--report-azdo-slow-test-history-multiplier"}</comment>
  </data>
  <data name="SlowTestHistoryOptionDescription" xml:space="preserve">
    <value>Query Azure DevOps test result history for the past N days (1-90) and lower the per-test 'still running' threshold for tests with a known-short historical runtime. Requires '--report-azdo'.</value>
    <comment>{Locked="--report-azdo"}</comment>
  </data>
  <data name="SlowTestHistoryMinSampleOptionDescription" xml:space="preserve">
    <value>Minimum number of historical samples required before a test's history is used to adjust its slow-test threshold or decorate emitted lines. Defaults to {0}. Requires '--report-azdo-slow-test-history'.</value>
    <comment>{0} is the default minimum sample count. {Locked="--report-azdo-slow-test-history"}</comment>
  </data>
  <data name="SlowTestHistoryMultiplierOptionDescription" xml:space="preserve">
    <value>Multiplier applied to a test's historical p99 duration to derive its slow-test threshold (threshold = min(static default, p99 * multiplier)). Defaults to {0}. Requires '--report-azdo-slow-test-history'.</value>
    <comment>{0} is the default multiplier. {Locked="--report-azdo-slow-test-history"}</comment>
  </data>
  <data name="SlowTestHistoryRequiresTfBuildWarning" xml:space="preserve">
    <value>Azure DevOps slow-test history was requested, but TF_BUILD is not set to 'true'; skipping slow-test surfacing.</value>
    <comment>{Locked="TF_BUILD"}{Locked="true"}</comment>
  </data>
  <data name="SlowTestStillRunning" xml:space="preserve">
    <value>[slow] still running after {0}: {1}</value>
    <comment>{0} is the elapsed duration. {1} is the test name. {Locked="[slow]"}</comment>
  </data>
  <data name="SlowTestHistoryDecoration" xml:space="preserve">
    <value>(historical p95 = {0}, p99 = {1}, samples = {2})</value>
    <comment>{0} is the p95 duration. {1} is the p99 duration. {2} is the sample count.</comment>
  </data>
</root>
