<?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="CreatingDumpFile" xml:space="preserve">
    <value>Creating dump file '{0}'</value>
    <comment>{0} is the dump file path.</comment>
  </data>
  <data name="DumpingProcess" xml:space="preserve">
    <value>Dumping process {0} - {1}</value>
    <comment>0 is pid, 1 is the name of the process</comment>
  </data>
  <data name="DumpingProcessTree" xml:space="preserve">
    <value>Dumping this process tree (from bottom):</value>
  </data>
  <data name="ErrorGettingParentOfProcess" xml:space="preserve">
    <value>Error getting parent of process {0} - {1}: {2}"</value>
    <comment>0 is pid, 1 is name, 2 is the exception</comment>
  </data>
  <data name="ErrorKillingProcess" xml:space="preserve">
    <value>Error while killing process {0} - {1}: {2}</value>
    <comment>0 is pid, 1 is name, 2 is the exception</comment>
  </data>
  <data name="ErrorWhileDumpingProcess" xml:space="preserve">
    <value>Error while taking dump of process {0} - {1}: {2}</value>
    <comment>0 is pid, 1 is name, 2 is the exception from the system</comment>
  </data>
  <data name="HangDumpArtifactDescription" xml:space="preserve">
    <value>The hang dump file</value>
  </data>
  <data name="HangDumpArtifactDisplayName" xml:space="preserve">
    <value>Hang dump file</value>
  </data>
  <data name="HangDumpEnvironmentVariableInvalidValueErrorMessage" xml:space="preserve">
    <value>Environment variable '{0}' is set to '{1}' instead of '{2}'</value>
    <comment>{0} is the environment variable name. {1} is the actual value. {2} is the expected value.</comment>
  </data>
  <data name="HangDumpEnvironmentVariableIsMissingErrorMessage" xml:space="preserve">
    <value>Environment variable '{0}' is not set</value>
    <comment>{0} is the environment variable name.</comment>
  </data>
  <data name="HangDumpExtensionDescription" xml:space="preserve">
    <value>Produce hang dump files when a test execution exceed a given time.</value>
  </data>
  <data name="HangDumpExtensionDisplayName" xml:space="preserve">
    <value>Hang dump</value>
  </data>
  <data name="HangDumpFailed" xml:space="preserve">
    <value>The following exception occurred while taking hang dump:
{0}

Disk info:
{1}</value>
    <comment>{0} is the exception that occurred. {1} is disk information detailing free space.</comment>
  </data>
  <data name="HangDumpFileNameOptionDescription" xml:space="preserve">
    <value>Specify the name of the dump file.
Supports the following placeholders: {pname} (test application name), {pid} (process ID), {asm} (entry assembly name), {tfm} (target framework moniker), {arch} (process architecture), {time} (timestamp). The legacy %p token (process ID) is also supported for backward compatibility.</value>
    <comment>Do not localize option name {Locked="--hangdump-filename"}, placeholder tokens {Locked="{pname}"}{Locked="{pid}"}{Locked="{asm}"}{Locked="{tfm}"}{Locked="{arch}"}{Locked="{time}"}, or legacy token {Locked="%p"}.</comment>
  </data>
  <data name="HangDumpOptionDescription" xml:space="preserve">
    <value>Generate a dump file if the test process hangs</value>
    <comment>Do not localize option name {Locked="--hangdump"}.</comment>
  </data>
  <data name="HangDumpTimeoutExpired" xml:space="preserve">
    <value>Hang dump timeout of '{0}' expired</value>
    <comment>{0} is the hang dump timeout value.</comment>
  </data>
  <data name="HangDumpTimeoutOptionDescription" xml:space="preserve">
    <value>Specify the timeout after which the dump will be generated.
The timeout value is specified in one of the following formats:
    500ms, 500mil, 500millisecond, 500milliseconds,
    5400s, 5400sec, 5400second, 5400seconds,
    90m, 90min, 90minute, 90minutes,
    1.5h, 1.5hour, 1.5hours,
    1d, 1day, 1days.
    A bare number (with no suffix) is interpreted as milliseconds.
    Default is 30m.</value>
    <comment>Do not localize option name {Locked="--hangdump-timeout"} or time examples {Locked="500ms"}{Locked="500mil"}{Locked="500millisecond"}{Locked="500milliseconds"}{Locked="5400s"}{Locked="5400sec"}{Locked="5400second"}{Locked="5400seconds"}{Locked="90m"}{Locked="90min"}{Locked="90minute"}{Locked="90minutes"}{Locked="1.5h"}{Locked="1.5hour"}{Locked="1.5hours"}{Locked="1d"}{Locked="1day"}{Locked="1days"}{Locked="30m"}.</comment>
  </data>
  <data name="HangDumpTimeoutOptionInvalidArgument" xml:space="preserve">
    <value>'--hangdump-timeout' expects a single timeout argument</value>
    <comment>Do not localize option name {Locked="--hangdump-timeout"}.</comment>
  </data>
  <data name="HangDumpTypeAndIfSupportedAreMutuallyExclusiveErrorMessage" xml:space="preserve">
    <value>'--hangdump-type' and '--hangdump-type-if-supported' are mutually exclusive. Use '--hangdump-type-if-supported' to opt into a best-effort dump type that falls back to the closest available type (with an informational message) when the requested type is unavailable on the current runtime, or '--hangdump-type' to fail fast on unsupported runtimes.</value>
    <comment>Do not localize option names {Locked="--hangdump-type"}{Locked="--hangdump-type-if-supported"}.</comment>
  </data>
  <data name="HangDumpTypeIfSupportedFallbackInfoMessage" xml:space="preserve">
    <value>'--hangdump-type-if-supported {0}' is not supported on the current runtime. Falling back to '{1}'.</value>
    <comment>0 is the requested dump type. 1 is the fallback dump type. Do not localize option name {Locked="--hangdump-type-if-supported"}.</comment>
  </data>
  <data name="HangDumpTypeIfSupportedOptionDescription" xml:space="preserve">
    <value>Same as '--hangdump-type' but silently falls back (with an informational message) to the closest supported dump type when the requested type is not available on the current runtime (e.g. 'Triage' is only supported on .NET Core and falls back to 'Mini' on .NET Framework). Use this option to keep the same command line across CI matrices that mix .NET Framework and .NET. Valid values are 'Mini', 'Heap', 'Full', 'Triage', 'None'. Mutually exclusive with '--hangdump-type'.</value>
    <comment>Do not localize option names {Locked="--hangdump-type"}{Locked="--hangdump-type-if-supported"}, dump type values {Locked="Mini"}{Locked="Heap"}{Locked="Full"}{Locked="Triage"}{Locked="None"}, or runtime names {Locked=".NET Core"}{Locked=".NET Framework"}{Locked=".NET"}.</comment>
  </data>
  <data name="HangDumpTypeOptionDescription" xml:space="preserve">
    <value>Specify the type of the dump.
Valid values are {0}.
Default type is 'Full'</value>
    <comment>0 is the list of valid dump type values. Do not localize option name {Locked="--hangdump-type"} or default dump type {Locked="Full"}.</comment>
  </data>
  <data name="HangDumpTypeOptionInvalidType" xml:space="preserve">
    <value>'{0}' is not a valid dump type.
Valid options are {1}</value>
    <comment>{0} is the invalid dump type. {1} is the list of valid dump type values.</comment>
  </data>
  <data name="HangDumpUnsupportedRequestTypeErrorMessage" xml:space="preserve">
    <value>Request of type '{0}' is not supported</value>
    <comment>{0} is the unsupported request type name.</comment>
  </data>
  <data name="HangTestListArtifactDescription" xml:space="preserve">
    <value>The list of tests that were running at the time of the hang</value>
  </data>
  <data name="HangTestListArtifactDisplayName" xml:space="preserve">
    <value>Hang test list</value>
  </data>
  <data name="MissingHangDumpMainOption" xml:space="preserve">
    <value>You specified one or more hang dump parameters but did not enable it, add --hangdump to the command line</value>
    <comment>Do not localize option name {Locked="--hangdump"}.</comment>
  </data>
  <data name="RunningTestsWhileDumping" xml:space="preserve">
    <value>The following tests were still running when dump was taken (format: [&lt;time-elapsed-since-start&gt;] &lt;name&gt;):</value>
    <comment>Do not localize format tokens {Locked="[&lt;time-elapsed-since-start&gt;]"} and {Locked="&lt;name&gt;"}.</comment>
  </data>
</root>