🔥 Device tests completed (Failed) on TvOS on [Azure DevOps](https://dev.azure.com/devdiv/DevDiv/_build/index?buildId=3414620)(TvOS): [Html Report](http://xamarin-storage/jenkins/xamarin-macios/alex-newsamples/910ea0d6651f3cafd8e47f8f2b9c869f056a8545/3414620/device-tests/jenkins-results/tests/index.html) 🔥

# Test results

<details>
<summary>142 tests failed, 0 tests passed.</summary>

## Failed tests

 * monotouch-test/tvOS - device/Debug: Failed
 * framework-test/tvOS - device/Debug: Failed
 * interdependent-binding-projects/tvOS - device/Debug: Failed
 * fsharp/tvOS - device/Debug: Failed
 * dont link/tvOS - device/Debug: Failed
 * link all/tvOS - device/Debug: Failed
 * link sdk/tvOS - device/Debug: Failed
 * mono-native-compat/tvOS - device/Debug: Failed
 * mono-native-unified/tvOS - device/Debug: HarnessException (Harness exception for 'mono-native-unified': System.IO.IOException: Sharing violation on path /Users/xamarinqa/agent/_work/1/s/tests/[Unknown]
  at System.IO.FileStream.WriteInternal (System.Byte[] src, System.Int32 offset, System.Int32 count) [0x000be] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:658
  at System.IO.FileStream.Write (System.Byte[] array, System.Int32 offset, System.Int32 count) [0x00090] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:614
  at System.IO.StreamWriter.Flush (System.Boolean flushStream, System.Boolean flushEncoder) [0x00080] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:335
  at System.IO.StreamWriter.WriteSpan (System.ReadOnlySpan`1[T] buffer, System.Boolean appendNewLine) [0x0016b] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:516
  at System.IO.StreamWriter.WriteLine (System.String value) [0x00006] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:530
  at System.IO.TextWriter+SyncTextWriter.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/TextWriter.cs:817
  at (wrapper synchronized) System.IO.TextWriter+SyncTextWriter.WriteLine(string)
  at System.Console.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System/Console.cs:428
  at xharness.Harness.LogWrench (System.String message) [0x00010] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Harness.cs:673
  at xharness.AppRunner.ParseResult (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x002e7] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:516
  at xharness.AppRunner.TestsSucceeded (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x00001] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:553
  at xharness.AppRunner.RunAsync () [0x0193d] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:902
  at xharness.RunDeviceTask.RunTestAsync () [0x0067e] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3744
  at xharness.RunDeviceTask.RunTestAsync () [0x00c17] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3794
  at xharness.RunTestTask.ExecuteAsync () [0x00191] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3523
  at xharness.TestTask.RunInternalAsync () [0x00226] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:2635 )
 * [NUnit] Mono BCL tests group 1/tvOS - device/Debug: Failed
 * [NUnit] Mono BCL tests group 2/tvOS - device/Debug: Failed
 * [xUnit] Mono BCL tests group 3/tvOS - device/Debug: Failed
 * [xUnit] Mono BCL tests group 4/tvOS - device/Debug: Failed
 * [xUnit] Mono BCL tests group 5/tvOS - device/Debug: HarnessException (Harness exception for '[xUnit] Mono BCL tests group 5': System.IO.IOException: Sharing violation on path /Users/xamarinqa/agent/_work/1/s/tests/[Unknown]
  at System.IO.FileStream.WriteInternal (System.Byte[] src, System.Int32 offset, System.Int32 count) [0x000be] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:658
  at System.IO.FileStream.Write (System.Byte[] array, System.Int32 offset, System.Int32 count) [0x00090] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:614
  at System.IO.StreamWriter.Flush (System.Boolean flushStream, System.Boolean flushEncoder) [0x00080] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:335
  at System.IO.StreamWriter.WriteSpan (System.ReadOnlySpan`1[T] buffer, System.Boolean appendNewLine) [0x0016b] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:516
  at System.IO.StreamWriter.WriteLine (System.String value) [0x00006] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:530
  at System.IO.TextWriter+SyncTextWriter.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/TextWriter.cs:817
  at (wrapper synchronized) System.IO.TextWriter+SyncTextWriter.WriteLine(string)
  at System.Console.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System/Console.cs:428
  at xharness.Harness.LogWrench (System.String message) [0x00010] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Harness.cs:673
  at xharness.AppRunner.ParseResult (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x002e7] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:516
  at xharness.AppRunner.TestsSucceeded (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x00001] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:553
  at xharness.AppRunner.RunAsync () [0x0193d] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:902
  at xharness.RunDeviceTask.RunTestAsync () [0x0067e] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3744
  at xharness.RunDeviceTask.RunTestAsync () [0x00c17] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3794
  at xharness.RunTestTask.ExecuteAsync () [0x00191] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3523
  at xharness.TestTask.RunInternalAsync () [0x00226] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:2635 )
 * mscorlib Part 1/tvOS - device/Debug: Failed
 * mscorlib Part 2/tvOS - device/Debug: Failed
 * [xUnit] Mono SystemCoreXunit Part 1/tvOS - device/Debug: Failed
 * [xUnit] Mono SystemCoreXunit Part 2/tvOS - device/Debug: Failed
 * [xUnit] Mono SystemXunit/tvOS - device/Debug: Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * monotouch-test/tvOS - device/Release: Failed
 * monotouch-test/tvOS - device/AssemblyBuildTarget: SDK framework (release): HarnessException (Harness exception for 'monotouch-test': System.IO.IOException: Sharing violation on path /Users/xamarinqa/agent/_work/1/s/tests/[Unknown]
  at System.IO.FileStream.WriteInternal (System.Byte[] src, System.Int32 offset, System.Int32 count) [0x000be] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:658
  at System.IO.FileStream.Write (System.Byte[] array, System.Int32 offset, System.Int32 count) [0x00090] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:614
  at System.IO.StreamWriter.Flush (System.Boolean flushStream, System.Boolean flushEncoder) [0x00080] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:335
  at System.IO.StreamWriter.WriteSpan (System.ReadOnlySpan`1[T] buffer, System.Boolean appendNewLine) [0x0016b] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:516
  at System.IO.StreamWriter.WriteLine (System.String value) [0x00006] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:530
  at System.IO.TextWriter+SyncTextWriter.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/TextWriter.cs:817
  at (wrapper synchronized) System.IO.TextWriter+SyncTextWriter.WriteLine(string)
  at System.Console.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System/Console.cs:428
  at xharness.Harness.LogWrench (System.String message) [0x00010] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Harness.cs:673
  at xharness.AppRunner.ParseResult (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x002e7] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:516
  at xharness.AppRunner.TestsSucceeded (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x00001] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:553
  at xharness.AppRunner.RunAsync () [0x0193d] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:902
  at xharness.RunDeviceTask.RunTestAsync () [0x0067e] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3744
  at xharness.RunDeviceTask.RunTestAsync () [0x00c17] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3794
  at xharness.RunTestTask.ExecuteAsync () [0x00191] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3523
  at xharness.TestTask.RunInternalAsync () [0x00226] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:2635 )
 * monotouch-test/tvOS - device/Debug (dynamic registrar): Failed
 * monotouch-test/tvOS - device/Release (all optimizations): Failed
 * monotouch-test/tvOS - device/Debug (all optimizations): Failed
 * monotouch-test/tvOS - device/Debug: SGenConc: Failed
 * monotouch-test/tvOS - device/Debug (interpreter): Failed
 * monotouch-test/tvOS - device/Debug (interpreter -mscorlib): Failed
 * monotouch-test/tvOS - device/Release (interpreter -mscorlib): Failed
 * framework-test/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * framework-test/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * framework-test/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): HarnessException (Harness exception for 'framework-test': System.IO.IOException: Sharing violation on path /Users/xamarinqa/agent/_work/1/s/tests/[Unknown]
  at System.IO.FileStream.WriteInternal (System.Byte[] src, System.Int32 offset, System.Int32 count) [0x000be] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:658
  at System.IO.FileStream.Write (System.Byte[] array, System.Int32 offset, System.Int32 count) [0x00090] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:614
  at System.IO.StreamWriter.Flush (System.Boolean flushStream, System.Boolean flushEncoder) [0x00080] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:335
  at System.IO.StreamWriter.WriteSpan (System.ReadOnlySpan`1[T] buffer, System.Boolean appendNewLine) [0x0016b] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:516
  at System.IO.StreamWriter.WriteLine (System.String value) [0x00006] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:530
  at System.IO.TextWriter+SyncTextWriter.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/TextWriter.cs:817
  at (wrapper synchronized) System.IO.TextWriter+SyncTextWriter.WriteLine(string)
  at System.Console.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System/Console.cs:428
  at xharness.Harness.LogWrench (System.String message) [0x00010] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Harness.cs:673
  at xharness.AppRunner.ParseResult (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x002e7] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:516
  at xharness.AppRunner.TestsSucceeded (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x00001] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:553
  at xharness.AppRunner.RunAsync () [0x0193d] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:902
  at xharness.RunDeviceTask.RunTestAsync () [0x0067e] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3744
  at xharness.RunDeviceTask.RunTestAsync () [0x00c17] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3794
  at xharness.RunTestTask.ExecuteAsync () [0x00191] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3523
  at xharness.TestTask.RunInternalAsync () [0x00226] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:2635 )
 * framework-test/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): HarnessException (Harness exception for 'framework-test': System.IO.IOException: Sharing violation on path /Users/xamarinqa/agent/_work/1/s/tests/[Unknown]
  at System.IO.FileStream.WriteInternal (System.Byte[] src, System.Int32 offset, System.Int32 count) [0x000be] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:658
  at System.IO.FileStream.Write (System.Byte[] array, System.Int32 offset, System.Int32 count) [0x00090] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:614
  at System.IO.StreamWriter.Flush (System.Boolean flushStream, System.Boolean flushEncoder) [0x00080] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:335
  at System.IO.StreamWriter.WriteSpan (System.ReadOnlySpan`1[T] buffer, System.Boolean appendNewLine) [0x0016b] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:516
  at System.IO.StreamWriter.WriteLine (System.String value) [0x00006] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:530
  at System.IO.TextWriter+SyncTextWriter.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/TextWriter.cs:817
  at (wrapper synchronized) System.IO.TextWriter+SyncTextWriter.WriteLine(string)
  at System.Console.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System/Console.cs:428
  at xharness.Harness.LogWrench (System.String message) [0x00010] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Harness.cs:673
  at xharness.AppRunner.ParseResult (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x002e7] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:516
  at xharness.AppRunner.TestsSucceeded (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x00001] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:553
  at xharness.AppRunner.RunAsync () [0x0193d] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:902
  at xharness.RunDeviceTask.RunTestAsync () [0x0067e] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3744
  at xharness.RunDeviceTask.RunTestAsync () [0x00c17] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3794
  at xharness.RunTestTask.ExecuteAsync () [0x00191] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3523
  at xharness.TestTask.RunInternalAsync () [0x00226] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:2635 )
 * framework-test/tvOS - device/Release: Failed
 * framework-test/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: SDK framework (debug): HarnessException (Harness exception for 'interdependent-binding-projects': System.IO.IOException: Sharing violation on path /Users/xamarinqa/agent/_work/1/s/tests/[Unknown]
  at System.IO.FileStream.WriteInternal (System.Byte[] src, System.Int32 offset, System.Int32 count) [0x000be] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:658
  at System.IO.FileStream.Write (System.Byte[] array, System.Int32 offset, System.Int32 count) [0x00090] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:614
  at System.IO.StreamWriter.Flush (System.Boolean flushStream, System.Boolean flushEncoder) [0x00080] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:335
  at System.IO.StreamWriter.WriteSpan (System.ReadOnlySpan`1[T] buffer, System.Boolean appendNewLine) [0x0016b] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:516
  at System.IO.StreamWriter.WriteLine (System.String value) [0x00006] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:530
  at System.IO.TextWriter+SyncTextWriter.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/TextWriter.cs:817
  at (wrapper synchronized) System.IO.TextWriter+SyncTextWriter.WriteLine(string)
  at System.Console.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System/Console.cs:428
  at xharness.Harness.LogWrench (System.String message) [0x00010] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Harness.cs:673
  at xharness.AppRunner.ParseResult (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x002e7] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:516
  at xharness.AppRunner.TestsSucceeded (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x00001] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:553
  at xharness.AppRunner.RunAsync () [0x0193d] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:902
  at xharness.RunDeviceTask.RunTestAsync () [0x0067e] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3744
  at xharness.RunDeviceTask.RunTestAsync () [0x00c17] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3794
  at xharness.RunTestTask.ExecuteAsync () [0x00191] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3523
  at xharness.TestTask.RunInternalAsync () [0x00226] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:2635 )
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * interdependent-binding-projects/tvOS - device/Release: Failed
 * interdependent-binding-projects/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * fsharp/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * fsharp/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * fsharp/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * fsharp/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * fsharp/tvOS - device/Release: Failed
 * fsharp/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * dont link/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * dont link/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * dont link/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * dont link/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): HarnessException (Harness exception for 'dont link': System.IO.IOException: Sharing violation on path /Users/xamarinqa/agent/_work/1/s/tests/[Unknown]
  at System.IO.FileStream.WriteInternal (System.Byte[] src, System.Int32 offset, System.Int32 count) [0x000be] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:658
  at System.IO.FileStream.Write (System.Byte[] array, System.Int32 offset, System.Int32 count) [0x00090] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:614
  at System.IO.StreamWriter.Flush (System.Boolean flushStream, System.Boolean flushEncoder) [0x00080] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:335
  at System.IO.StreamWriter.WriteSpan (System.ReadOnlySpan`1[T] buffer, System.Boolean appendNewLine) [0x0016b] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:516
  at System.IO.StreamWriter.WriteLine (System.String value) [0x00006] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:530
  at System.IO.TextWriter+SyncTextWriter.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/TextWriter.cs:817
  at (wrapper synchronized) System.IO.TextWriter+SyncTextWriter.WriteLine(string)
  at System.Console.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System/Console.cs:428
  at xharness.Harness.LogWrench (System.String message) [0x00010] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Harness.cs:673
  at xharness.AppRunner.ParseResult (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x002e7] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:516
  at xharness.AppRunner.TestsSucceeded (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x00001] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:553
  at xharness.AppRunner.RunAsync () [0x0193d] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:902
  at xharness.RunDeviceTask.RunTestAsync () [0x0067e] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3744
  at xharness.RunDeviceTask.RunTestAsync () [0x00c17] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3794
  at xharness.RunTestTask.ExecuteAsync () [0x00191] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3523
  at xharness.TestTask.RunInternalAsync () [0x00226] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:2635 )
 * dont link/tvOS - device/Release: Failed
 * dont link/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * link all/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * link all/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * link all/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * link all/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): HarnessException (Harness exception for 'link all': System.IO.IOException: Sharing violation on path /Users/xamarinqa/agent/_work/1/s/tests/[Unknown]
  at System.IO.FileStream.WriteInternal (System.Byte[] src, System.Int32 offset, System.Int32 count) [0x000be] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:658
  at System.IO.FileStream.Write (System.Byte[] array, System.Int32 offset, System.Int32 count) [0x00090] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:614
  at System.IO.StreamWriter.Flush (System.Boolean flushStream, System.Boolean flushEncoder) [0x00080] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:335
  at System.IO.StreamWriter.WriteSpan (System.ReadOnlySpan`1[T] buffer, System.Boolean appendNewLine) [0x0016b] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:516
  at System.IO.StreamWriter.WriteLine (System.String value) [0x00006] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:530
  at System.IO.TextWriter+SyncTextWriter.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/TextWriter.cs:817
  at (wrapper synchronized) System.IO.TextWriter+SyncTextWriter.WriteLine(string)
  at System.Console.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System/Console.cs:428
  at xharness.Harness.LogWrench (System.String message) [0x00010] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Harness.cs:673
  at xharness.AppRunner.ParseResult (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x002e7] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:516
  at xharness.AppRunner.TestsSucceeded (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x00001] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:553
  at xharness.AppRunner.RunAsync () [0x0193d] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:902
  at xharness.RunDeviceTask.RunTestAsync () [0x0067e] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3744
  at xharness.RunDeviceTask.RunTestAsync () [0x00c17] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3794
  at xharness.RunTestTask.ExecuteAsync () [0x00191] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3523
  at xharness.TestTask.RunInternalAsync () [0x00226] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:2635 )
 * link all/tvOS - device/Release: Failed
 * link all/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * link sdk/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * link sdk/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * link sdk/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): HarnessException (Harness exception for 'link sdk': System.IO.IOException: Sharing violation on path /Users/xamarinqa/agent/_work/1/s/tests/[Unknown]
  at System.IO.FileStream.WriteInternal (System.Byte[] src, System.Int32 offset, System.Int32 count) [0x000be] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:658
  at System.IO.FileStream.Write (System.Byte[] array, System.Int32 offset, System.Int32 count) [0x00090] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:614
  at System.IO.StreamWriter.Flush (System.Boolean flushStream, System.Boolean flushEncoder) [0x00080] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:335
  at System.IO.StreamWriter.WriteSpan (System.ReadOnlySpan`1[T] buffer, System.Boolean appendNewLine) [0x0016b] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:516
  at System.IO.StreamWriter.WriteLine (System.String value) [0x00006] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:530
  at System.IO.TextWriter+SyncTextWriter.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/TextWriter.cs:817
  at (wrapper synchronized) System.IO.TextWriter+SyncTextWriter.WriteLine(string)
  at System.Console.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System/Console.cs:428
  at xharness.Harness.LogWrench (System.String message) [0x00010] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Harness.cs:673
  at xharness.AppRunner.ParseResult (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x002e7] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:516
  at xharness.AppRunner.TestsSucceeded (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x00001] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:553
  at xharness.AppRunner.RunAsync () [0x0193d] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:902
  at xharness.RunDeviceTask.RunTestAsync () [0x0067e] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3744
  at xharness.RunDeviceTask.RunTestAsync () [0x00c17] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3794
  at xharness.RunTestTask.ExecuteAsync () [0x00191] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3523
  at xharness.TestTask.RunInternalAsync () [0x00226] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:2635 )
 * link sdk/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * link sdk/tvOS - device/Release: Failed
 * link sdk/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * mono-native-compat/tvOS - device/Release: Failed
 * mono-native-compat/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * mono-native-unified/tvOS - device/Release: Failed
 * mono-native-unified/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * [NUnit] Mono BCL tests group 1/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * [NUnit] Mono BCL tests group 1/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [NUnit] Mono BCL tests group 1/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [NUnit] Mono BCL tests group 1/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [NUnit] Mono BCL tests group 1/tvOS - device/Release: Failed (MT1032: This application executable might be too large (848 MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.)
 * [NUnit] Mono BCL tests group 1/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * [NUnit] Mono BCL tests group 2/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * [NUnit] Mono BCL tests group 2/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [NUnit] Mono BCL tests group 2/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [NUnit] Mono BCL tests group 2/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [NUnit] Mono BCL tests group 2/tvOS - device/Release: Failed (MT1032: This application executable might be too large (1009 MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.)
 * [NUnit] Mono BCL tests group 2/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * [xUnit] Mono BCL tests group 3/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * [xUnit] Mono BCL tests group 3/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [xUnit] Mono BCL tests group 3/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [xUnit] Mono BCL tests group 3/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [xUnit] Mono BCL tests group 3/tvOS - device/Release: Failed (MT1032: This application executable might be too large (702 MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.)
 * [xUnit] Mono BCL tests group 3/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * [xUnit] Mono BCL tests group 4/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * [xUnit] Mono BCL tests group 4/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [xUnit] Mono BCL tests group 4/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [xUnit] Mono BCL tests group 4/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [xUnit] Mono BCL tests group 4/tvOS - device/Release: Failed (MT1032: This application executable might be too large (594 MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.)
 * [xUnit] Mono BCL tests group 4/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * [xUnit] Mono BCL tests group 5/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * [xUnit] Mono BCL tests group 5/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [xUnit] Mono BCL tests group 5/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [xUnit] Mono BCL tests group 5/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [xUnit] Mono BCL tests group 5/tvOS - device/Release: Failed
 * [xUnit] Mono BCL tests group 5/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * mscorlib Part 1/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * mscorlib Part 1/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * mscorlib Part 1/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * mscorlib Part 1/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * mscorlib Part 1/tvOS - device/Release: Failed (MT1032: This application executable might be too large (679 MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.)
 * mscorlib Part 1/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * mscorlib Part 1/tvOS - device/Debug: SGenConc: HarnessException (Harness exception for 'mscorlib Part 1': System.IO.IOException: Sharing violation on path /Users/xamarinqa/agent/_work/1/s/tests/[Unknown]
  at System.IO.FileStream.WriteInternal (System.Byte[] src, System.Int32 offset, System.Int32 count) [0x000be] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:658
  at System.IO.FileStream.Write (System.Byte[] array, System.Int32 offset, System.Int32 count) [0x00090] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/FileStream.cs:614
  at System.IO.StreamWriter.Flush (System.Boolean flushStream, System.Boolean flushEncoder) [0x00080] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:335
  at System.IO.StreamWriter.WriteSpan (System.ReadOnlySpan`1[T] buffer, System.Boolean appendNewLine) [0x0016b] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:516
  at System.IO.StreamWriter.WriteLine (System.String value) [0x00006] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/StreamWriter.cs:530
  at System.IO.TextWriter+SyncTextWriter.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/external/corefx/src/Common/src/CoreLib/System/IO/TextWriter.cs:817
  at (wrapper synchronized) System.IO.TextWriter+SyncTextWriter.WriteLine(string)
  at System.Console.WriteLine (System.String value) [0x00000] in /Users/builder/jenkins/workspace/build-package-osx-mono/2019-10/external/bockbuild/builds/mono-x64/mcs/class/corlib/System/Console.cs:428
  at xharness.Harness.LogWrench (System.String message) [0x00010] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Harness.cs:673
  at xharness.AppRunner.ParseResult (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x002e7] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:516
  at xharness.AppRunner.TestsSucceeded (xharness.Log listener_log, System.Boolean timed_out, System.Boolean crashed) [0x00001] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:553
  at xharness.AppRunner.RunAsync () [0x0193d] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/AppRunner.cs:902
  at xharness.RunDeviceTask.RunTestAsync () [0x0067e] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3744
  at xharness.RunDeviceTask.RunTestAsync () [0x00c17] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3794
  at xharness.RunTestTask.ExecuteAsync () [0x00191] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:3523
  at xharness.TestTask.RunInternalAsync () [0x00226] in /Users/xamarinqa/agent/_work/1/s/tests/xharness/Jenkins.cs:2635 )
 * mscorlib Part 2/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * mscorlib Part 2/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * mscorlib Part 2/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * mscorlib Part 2/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * mscorlib Part 2/tvOS - device/Release: Failed (MT1032: This application executable might be too large (740 MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.)
 * mscorlib Part 2/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * mscorlib Part 2/tvOS - device/Debug: SGenConc: Failed
 * [xUnit] Mono SystemCoreXunit Part 1/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * [xUnit] Mono SystemCoreXunit Part 1/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [xUnit] Mono SystemCoreXunit Part 1/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [xUnit] Mono SystemCoreXunit Part 1/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [xUnit] Mono SystemCoreXunit Part 1/tvOS - device/Release: Failed (MT1032: This application executable might be too large (667 MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.)
 * [xUnit] Mono SystemCoreXunit Part 1/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * [xUnit] Mono SystemCoreXunit Part 2/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * [xUnit] Mono SystemCoreXunit Part 2/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [xUnit] Mono SystemCoreXunit Part 2/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [xUnit] Mono SystemCoreXunit Part 2/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [xUnit] Mono SystemCoreXunit Part 2/tvOS - device/Release: Failed (MT1032: This application executable might be too large (735 MB) to execute on device. If bitcode was enabled you might want to disable it for development, it is only required to submit applications to Apple.)
 * [xUnit] Mono SystemCoreXunit Part 2/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
 * [xUnit] Mono SystemXunit/tvOS - device/AssemblyBuildTarget: dylib (debug): Failed
 * [xUnit] Mono SystemXunit/tvOS - device/AssemblyBuildTarget: SDK framework (debug): Failed
 * [xUnit] Mono SystemXunit/tvOS - device/AssemblyBuildTarget: dylib (debug, profiling): Failed
 * [xUnit] Mono SystemXunit/tvOS - device/AssemblyBuildTarget: SDK framework (debug, profiling): Failed
 * [xUnit] Mono SystemXunit/tvOS - device/Release: Failed
 * [xUnit] Mono SystemXunit/tvOS - device/AssemblyBuildTarget: SDK framework (release): Failed
</details>


Hey boss, anytime!

I'll work on the pull request for the ci workaround.


# Specs execution successful
:scroll: [View logs](http://bamboo.comnull)
### Plans updated

Bamboo specs have been successfully imported and the following plans have been updated.

Project | Plan | Build
---|---|---
[Test](http://bamboo.com/browse/TEST) | [Comment test](http://bamboo.com/browse/TEST-CTEST)  | :white_check_mark: [\#1](http://bamboo.com/browse/TEST-CTEST-1)
[New project](http://bamboo.com/browse/NEW) | [Disabled plan](http://bamboo.com/browse/NEW-DISABLED) **disabled** | :white_check_mark: [\#1](http://bamboo.com/browse/NEW-DISABLED-1)

### Deployments updated

Bamboo specs have been successfully imported and the following deployment projects have been updated.

|Deployment project |
----|
[Deployment test](http://bamboo.com/deploy/viewDeploymentProjectVersions.action?id=2162689)|


@kross00 Make sure to work out examples by hand! I think if you did, you'd notice you didn't start by thinking about seconds.

For example, something like `141` seconds, you'd ask:

1. How many minutes go into 141 seconds? 2 minutes, with 21 seconds left over.

What about something like 3780 seconds?

1. How many hours fit into 3780 seconds?
2. From what's leftover after (1), how many minutes fit into that?
3. From what's leftover after (2), that's the number of seconds.

In other words, when you do it by hand, I think you'd see you don't start from seconds and work up, but start from the largest bucket of time and work down.

Try half a dozen or so examples by hand first. That's what I did. Pay attention to what you're doing and why.


Successfully deployed to following URLs:

* https://ui-ktxbhxgfq.now.sh
* https://ui.roleypoly.com
* https://ui.roleypoly.now.sh
* https://ui-git-master.roleypoly.now.sh


It is a user option on GitHub


Maybe we can set `grid->table` before calling `parent::init` ?
Only `Grid` have these issues, right?


Deployment failed with the following error:

~~~
The property `builds` is only allowed on Now 2.0 — please upgrade: https://zeit.co/upgrade
~~~


Successfully deployed to following URLs:

* https://react-hook-form-website-gd4n3ljsa.now.sh
* https://react-hook-form.com
* https://www.react-hook-form.com
* https://react-hook-form-website.bluebill1049.now.sh
* https://react-hook-form-website-git-master.bluebill1049.now.sh


Successfully deployed to following URLs:

* https://expeditions-mrsfugbio.now.sh
* https://expeditions.now.sh
* https://expeditions.shoppre.com
* https://expeditions.shoppre.now.sh
* https://expeditions-git-master.shoppre.now.sh


My third program


@mastacontrola Which version was used here?


Successfully deployed to following URLs:

* https://bloggeographerfr-ga759zodu.now.sh
* https://blog.geographer.fr
* https://geoblog.now.sh


I just upgrade our forum to phpBB 3.3.0 and now it won't come up :(

I did contact @MastaG hope he could help me soon to bring it back again.


TeamCity Identity and Access Management / identity-hostedpages [Build 1213](https://teamcity.nice.org.uk/viewLog.html?buildId=64844&buildTypeId=IdentityandAccessManagement_IdentityHostedpages) is now running


TeamCity Identity and Access Management / identity-hostedpages [Build 1212-r1F890B9](https://teamcity.nice.org.uk/viewLog.html?buildId=64843&buildTypeId=IdentityandAccessManagement_IdentityHostedpages) outcome was **SUCCESS**
Summary: Tests passed: 59 Build time: 00:02:50


TeamCity Identity and Access Management / identity-hostedpages [Build 1211-r67DDC82](https://teamcity.nice.org.uk/viewLog.html?buildId=64842&buildTypeId=IdentityandAccessManagement_IdentityHostedpages) outcome was **SUCCESS**
Summary: Tests passed: 59 Build time: 00:02:57


It seems that while doing the helm deploy now with version `0.17.0` Loki-chart I am not Able to lint my charts as `Chart.yaml` requires `apiVersion` to be set. This is breaking the workflow , Can anyone please let us know it's the backward compatibility isn't maintained, How do I fix this now ?

> Linting release=loki, chart=/var/folders/3q/9k97mz5s7dj90kwxx58ntfdm0000gn/T/743631397/loki/0.17.0/loki/loki-stack/loki-stack
==> Linting /var/folders/3q/9k97mz5s7dj90kwxx58ntfdm0000gn/T/743631397/loki/0.17.0/loki/loki-stack/loki-stack
[ERROR] Chart.yaml: apiVersion is required
in ./helmfile.yaml: helm exited with status 1:
  Error: 1 chart(s) linted, 1 chart(s) failed


Successfully deployed to following URLs:

* https://alehatsmancom-mwrcgqk1m.now.sh
* https://alehatsman.com
* https://alehatsmancom.alehatsman.now.sh
* https://alehatsmancom-git-master.alehatsman.now.sh


Successfully deployed to following URLs:

* https://typing-game-3gsv7c2qj.now.sh
* https://typing-app.now.sh
* https://typing-game.pashatay.now.sh
* https://typing-game-git-master.pashatay.now.sh


hello world


Successfully deployed to following URLs:

* https://that-website-cp41oj8g2.now.sh
* https://www.thatconference.com
* https://thatconferfence.now.sh
* https://that-website.that-conference.now.sh
* https://that-website-git-master.that-conference.now.sh


Hi Mark

Thanks a lot.
What I've been told is that fda files contains OCT images. On Monday I will be able to handle a Topcon 3D Maestro in order to find out the way it storages the images.
I'm so interested in develop your code to adapt it to fda files if it was necessary.
I've created a repository in my GitHub account. There you will find two fda samples. As I've said before, on Monday maybe I'll have new samples.
Thank a lot!

github : antoniohupa / OCT


Does your config have cuda enabled?  Or is this without cuda enabled?

Sent from my iPhone

> On Jan 25, 2020, at 10:46 AM, Daniel Povey <notifications@github.com> wrote:
>
> OK I am reverting that PR, hopefully @luitjens will find the issue.
>
>
> On Sat, Jan 25, 2020 at 11:49 PM Georgios Vidalakis <
> notifications@github.com> wrote:
>
> > Hello,
> >
> > When I install kaldi and run "make depend -j 8" in kaldi/src/ I get the
> > following error:
> >
> > apply-batched-cmvn-online-cuda.cc:20:10: fatal error: cuda_profiler_api.h:
> > No such file or directory
> > #include <cuda_profiler_api.h>
> > ^~~~~~~~~~~~~~~~~~~~~
> > compilation terminated.
> > ../makefiles/default_rules.mk:149: recipe for target 'depend' failed
> > make[1]: *** [depend] Error 1
> >
> > All the previous installation steps have been followed. I have Ubuntu
> > 18.04.3.
> >
> > —
> > You are receiving this because you authored the thread.
> > Reply to this email directly, view it on GitHub
> > <https://github.com/kaldi-asr/kaldi/commit/216c5181e72defe471a516250b0047d4062eee4f?email_source=notifications&email_token=AAZFLO2W3GCCW4RMRH4NQQ3Q7RUSXA5CNFSM4KLRYPTKYY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBDIBJ5#commitcomment-36963645>,
> > or unsubscribe
> > <https://github.com/notifications/unsubscribe-auth/AAZFLOZC5SNP6GKCQ6WJXGDQ7RUSXANCNFSM4KLRYPTA>
> > .
> >
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or unsubscribe.


добавила наставника


teste


Successfully deployed to following URLs:

* https://crypto-price-3vd3jcjkr.now.sh
* https://crypto-price.now.sh
* https://crypto-price.robertjudson.now.sh
* https://crypto-price-git-master.robertjudson.now.sh


Successfully deployed to following URLs:

* https://resume-q1hx39aka.now.sh
* https://resume-pi.now.sh
* https://resume.grifstuf.com
* https://resume.gpolonus.now.sh
* https://resume-git-master.gpolonus.now.sh


Successfully deployed to following URLs:

* https://pblog-maaa507d8.now.sh
* https://pblog.now.sh
* https://pblog.argumentativeyouth.now.sh
* https://pblog-git-master.argumentativeyouth.now.sh


Successfully deployed to following URLs:

* https://grimp-website-sh4thck80.now.sh
* https://grimp.io
* https://grimp.co
* https://grimp.app
* https://www.grimp.io
* https://www.grimp.app
* https://www.grimp.co
* https://ws-admin.grimp.io
* https://grimp-website.grimp.now.sh
* https://grimp-website-git-master.grimp.now.sh


It brokes translations.


remove_objexx_gio__3 (lefticus) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-UnitTestsCoverage-Debug: OK (1268 of 1268 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.png) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.png) ![Coverage Badge](http://img.shields.io/badge/coverage%20status-43.61%25-green.png)


Successfully deployed to following URLs:

* https://blog-ihpbihzqx.now.sh
* https://blog-nu-rust.now.sh
* https://rppld.com
* https://blog.rppld.now.sh
* https://blog-git-master.rppld.now.sh


Deployment failed with the following error:

~~~
The property `routes` is only allowed on Now 2.0 — please upgrade: https://zeit.co/upgrade
~~~


Successfully deployed to following URLs:

* https://zpie-ifzr45oug.now.sh
* https://zpie.now.sh
* https://zpie.brucegne.now.sh
* https://zpie-git-master.brucegne.now.sh


Successfully deployed to following URLs:

* https://7io-3ob9s16t5.now.sh
* https://7io.now.sh
* https://www.7io.eu
* https://7io.eu
* https://7io.net
* https://7io.wevisualizeit.now.sh
* https://7io-git-master.wevisualizeit.now.sh


Successfully deployed to following URLs:

* https://pablopink-bj58rufun.now.sh
* https://pablo.pink
* https://pablovarela.es
* https://pablo.life
* https://www.pablo.pink
* https://pablopink.pablopunk.now.sh
* https://pablopink-git-master.pablopunk.now.sh


Successfully deployed to following URLs:

* https://ludoteca-react-gw9kqivdp.now.sh
* https://ludoteca-react.now.sh
* https://ludoteca-react.r4ncid.now.sh
* https://ludoteca-react-git-master.r4ncid.now.sh


Successfully deployed to following URLs:

* https://project-travel-to-russia--dsblpxixq.now.sh
* https://project-travel-to-russia--sooty.now.sh
* https://project-travel-to-russia.gdi1999.now.sh
* https://project-travel-to-russia-git-master.gdi1999.now.sh


У меня чуть мозг не вытек, когда я пытался осознать задачу. Для меня владение гитом это почти как уверенное владение скриптовым языком. Нужно очень точно представлять что ты делаешь и как. Создал бранч, залил, через rebase сжал все в один коммит, залил на remote. Сделал pr между ветками. PR нужно подтвердить, чтобы ты посмотрел?


- Can't be **cursed** by **Basilisks** on **Farron Keep**
Tested Without armor and ring...


Ha, I didn't even check the logic, but I guess that's another issue to fix
too.  I just noticed the undefined by my feels like temp

On Sat, Jan 25, 2020, 11:03 AM hangorazvan <notifications@github.com> wrote:

> The effect is inversed. When hideTemp: false the temp is hidden.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/MichMich/MagicMirror/commit/6ba5056c960ea62408e2e12f37be7cf5e793e49e?email_source=notifications&email_token=AACCGR3VMCOYHBE6MO76Z6TQ7RPFNA5CNFSM4KLRRSCKYY3PNVWWK3TUL52HS4DFVVBW63LNNF2EG33NNVSW45FKMNXW23LFNZ2F62LEZYBDIBCV#commitcomment-36963413>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AACCGRZG5L4MEO7FJ2GYSLDQ7RPFNANCNFSM4KLRRSCA>
> .
>


Correct. Reverted those changes in https://github.com/mamedev/mame/commit/6251391508e1bf6186b47694622c33c3000254f0


Deployment failed with the following error:

~~~
Your `package.json` file is missing a `build` property inside the `scripts` property.
~~~


Successfully deployed to following URLs:

* https://ready-roofer-next-a65wau2hs.now.sh
* https://ready-roofer-next.now.sh
* https://ready-roofer-next.undefinedindustries.now.sh
* https://ready-roofer-next-git-master.undefinedindustries.now.sh


斜線，可以保持原半形斜線，或用「或」字取代。


Successfully deployed to following URLs:

* https://b-tournaments-ijzi1b5tl.now.sh
* https://adm-gochamps.lairjr.now.sh
* https://b-tournaments.lairjr.now.sh
* https://b-tournaments-git-master.lairjr.now.sh


Successfully deployed to following URLs:

* https://tuukkaonet-8q690k0kp.now.sh
* https://tuukkao.net
* https://www.tuukkao.net
* https://tuukkaonet.tuukkao.now.sh
* https://tuukkaonet-git-master.tuukkao.now.sh


IBM Cloud [toolchain](https://cloud.ibm.com/devops/toolchains/b6493755-3248-4ee7-8242-0a0b91de810d?env_id=ibm%3Ayp%3Aus-south "helm-toolchain-20200123180954368"): [Delivery Pipeline](https://cloud.ibm.com/devops/pipelines/af62ca81-c78b-428b-961f-59d18747d4ff "hello-helm-20200123180954368") deployed [hello-helm-20200123180954368](https://github.com/raghugr2170/hello-helm-20200123180954368/releases/tag/deploy-mycluster-20200124-064539 "deploy-mycluster-20200124-064539") to [mycluster](https://console.bluemix.net/kubernetes/clusters/bo7gku5d0gftlbfhhd1g/overview "There was a problem retrieving the space name"), including this commit


執行中的


電量吧


Successfully deployed to following URLs:

* https://zeit-routes-3wsrq8bjt.now.sh
* https://zeit-routes.now.sh
* https://zeit-routes.ivan-kleshnin.now.sh
* https://zeit-routes-git-master.ivan-kleshnin.now.sh


同樣斜線問題


Emissivity-in-WindowMaterial-ComplexShade (LipingWang) - x86_64-Linux-Ubuntu-18.04-gcc-7.4-IntegrationCoverage-Debug: OK (677 of 678 tests passed, 0 test warnings)

Failures:\n

integration Test Summary
 * Passed: 677
 * Timeout: 1

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.png) ![Test Badge](http://img.shields.io/badge/tests%20passed-99.85%25-yellow.png) ![Coverage Badge](http://img.shields.io/badge/coverage%20status-68.35%25-yellow.png)


Successfully deployed to following URLs:

* https://b-tournaments-5yfqyocet.now.sh
* https://adm-gochamps.lairjr.now.sh
* https://b-tournaments.lairjr.now.sh
* https://b-tournaments-git-master.lairjr.now.sh


Successfully deployed to following URLs:

* https://zeit-routes-ld7hs7qj9.now.sh
* https://zeit-routes.now.sh
* https://zeit-routes.ivan-kleshnin.now.sh
* https://zeit-routes-git-master.ivan-kleshnin.now.sh


Successfully deployed to following URLs:

* https://workshop-bqwrz15uu.now.sh
* https://workshop-eight.now.sh
* https://workshop.dalmaueric29.now.sh
* https://workshop-git-master.dalmaueric29.now.sh


This commit has been mentioned on **Discourse Meta**. There might be relevant details there:

https://meta.discourse.org/t/error-cant-notify-admin-while-restoring-backup-during-a-migration-to-a-fresh-install/139606/10


Successfully deployed to following URLs:

* https://screencss-5f5hvsjjv.now.sh
* https://screencss.com
* https://www.screencss.com
* https://screencss.gduverger.now.sh
* https://screencss-git-master.gduverger.now.sh


Failed to assign a domain to your deployment due to the following error:

~~~
The domain jsnkng.com is not verfied and cannot be used as an alias.
~~~

([Learn more](https://zeit.co/jsnkng/jsnkng/r3lzob78k) or [visit](https://jsnkng-r3lzob78k.now.sh) the non-aliased deployment)


Any news ?

I need it to git to "XSS for superadmin too" feature


Ok. It doesn't matter.


Successfully deployed to following URLs:

* https://turing-hw-2-56wd716of.now.sh
* https://turing-hw-2.now.sh
* https://turing-hw-2.filipobsivac.now.sh
* https://turing-hw-2-git-master.filipobsivac.now.sh


Successfully deployed to following URLs:

* https://shorts-react-ionic-rgibzezyq.now.sh
* https://shorts.now.sh
* https://shorts-react-ionic.nrgapple.now.sh
* https://shorts-react-ionic-git-master.nrgapple.now.sh


Eventually also add a line in the header explaining update. ;)


Successfully deployed to following URLs:

* https://roman-numerals-app-eyfcp38df.now.sh
* https://roman-numerals-app.now.sh
* https://roman-numerals-app.shalanazim.now.sh
* https://roman-numerals-app-git-master.shalanazim.now.sh


Successfully deployed to following URLs:

* https://open-sorcerers-1ct7f5xrx.now.sh
* https://open-sorcerers.now.sh
* https://open.sorcerers.dev
* https://open-sorcerers.brekk.now.sh
* https://open-sorcerers-git-master.brekk.now.sh


Successfully deployed to following URLs:

* https://retreatsite-3za8s3ui7.now.sh
* https://retreatsite.now.sh
* https://retreat.now.sh
* https://retreatsite.ansarirayyan.now.sh
* https://retreatsite-git-master.ansarirayyan.now.sh


quq


Successfully deployed to following URLs:

* https://turing-hw-2-d46do2fug.now.sh
* https://turing-hw-2.now.sh
* https://turing-hw-2.filipobsivac.now.sh
* https://turing-hw-2-git-master.filipobsivac.now.sh


good coding.....


good


Thanks


@@ -3934,44 +3934,38 @@
Identity Provider Interaction

WebRTC offers and answers (and hence the channels established by
      RTCPeerConnection objects) can be authenticated by
      using a web-based Identity Provider (IdP). The idea is that the entity
      sending the offer/answer acts as the Authenticating Party (AP) and
      sending an offer or answer acts as the Authenticating Party (AP) and
      obtains an identity assertion from the IdP which it attaches to the
      offer/answer. The consumer of the offer/answer (i.e., the
      session description. The consumer of the session description (i.e., the
      RTCPeerConnection on which
      setRemoteDescription() is called) acts as the Relying Party
      (RP) and verifies the assertion.

The interaction with the IdP is designed to decouple the browser from
      any particular identity provider; the browser need only know how to load
      the IdP's JavaScript, which is deterministic from the IdP's identity, and
      the generic protocol for requesting and verifying assertions. The IdP
      the generic interface to generating and validating assertions. The IdP
      provides whatever logic is necessary to bridge the generic protocol to
      the IdP's specific requirements. Thus, a single browser can support any
      number of identity protocols, including being forward compatible with
      IdPs which did not exist at the time the browser was written. The generic
      protocol details are described in [[!RTCWEB-SECURITY-ARCH]]. This
      document specifies the procedures required to instantiate the IdP proxy,
      request identity assertions, and consume the results.

      IdPs which did not exist at the time the browser was written.

Identity Provider
        Selection

In order to communicate with the IdP, the browser instantiates an
        isolated interpreted context, effectively an invisible IFRAME. The
        initial contents of the context are loaded from a URI derived from the
        IdP's domain name, as described in [[!RTCWEB-SECURITY-ARCH]].

For purposes of generating assertions, the IdP shall be chosen as

An IdP is used to generate an identity assertion as
        follows:

If the setIdentityProvider() method has been called,
          the IdP provided shall be used.

If the setIdentityProvider() method has not been
          called, then the browser can use an IdP configured into the
          browser.

          called, then the user agent MAY use an IdP configured into the
          browser.  However, a user agent-provided IdP MUST NOT cause the
          createOffer or createAnswer invocation to
          fail.

In order to verify assertions, the IdP domain name and protocol are
@@ -3982,100 +3976,239 @@
Identity Provider

Instantiating an IdP Proxy

The browser creates an IdP proxy by loading an isolated, invisible
        IFRAME with HTML content from the IdP URI. The URI for the IdP is a

In order to communicate with the IdP, the user agent loads the IdP
        JavaScript from the IdP.   The URI for the IdP script is a
        well-known URI formed from the <q>domain</q> and <q>protocol</q>
        fields, as specified in [[!RTCWEB-SECURITY-ARCH]].

When an IdP proxy is requiured, the browser performs the following
        steps:

The IdP MAY generate an HTTP redirect to another "https" origin, the
        browser MUST treat a redirect to any other scheme as a fatal error.

The user agent instantiates an isolated interpreted context, a
        JavaScript <dfn>realm</dfn>
        that operates in the origin of the loaded JavaScript. Note that a
        redirect will change the origin of the loaded script.

The realm is populated with a global that implements
        WorkerGlobalScope [[!WEBWORKERS]].

The user agent provides instance of
        RTCIdentityProviderRegistrar named
        <var>rtcIdentityProvider</var> in the global scope of the realm.
        This object is used by the IdP to interact with the user agent.

Since it is an essential security property of the web sandbox that a
        page is unable to insert objects into content from another origin, using
        the global <var>rtcIdentityProvider</var> instance ensures that the IdP
        proxy can trust that invocations originate either from
        RTCPeerConnection or its origin. This protection ensures
        that other origins are unable to instantiate IdP proxies and impersonate
        this API in order obtain identity assertions.

readonly attribute RTCIdentityProviderRegistrar rtcIdentityProvider

            This object is used by the IdP to register an
            RTCIdentityProvider instance with the browser.

An invisible, sandboxed IFRAME is created within the browser
          context. The IFRAME sandbox attribute is set to
          "allow-forms allow-scripts allow-same-origin" to limit the
          capabilities available to the IdP. The browser MUST prevent the IdP
          proxy from navigating the browsing context to a different location.
          The browser MUST prevent the IdP proxy from interacting with the user
          (this includes, in particular, popup windows and user dialogs).

Once the IdP proxy is created, the browser creates a
          MessageChannel [[!webmessaging]] within the context of
          the IdP proxy and assigns one port from the channel to a variable
          named <var>rtcwebIdentityPort</var> on the <var>window</var>. This
          message channel forms the basis of communication between the browser
          and the IdP proxy. Since it is an essential security property of the
          web sandbox that a page is unable to insert objects into content from
          another origin, this ensures that the IdP proxy can trust that
          messages originating from <var>window.rtcwebIdentityPort</var> are
          from RTCPeerConnection and not some other page. This
          protection ensures that pages from other origins are unable to
          instantiate IdP proxies and obtain identity assertions.

The IdP proxy completes loading and informs the
          RTCPeerConnection that it is ready by sending a "READY"
          message to the message channel port [[!RTCWEB-SECURITY-ARCH]]. Once
          this message is received by the RTCPeerConnection, the
          IdP is considered ready to receive requests to generate or verify
          identity assertions.

Registering an IdP Proxy

An IdP proxy implements the RTCIdentityProvider
      callback interface, which is the means by which the user agent is able to
      request that an identity assertion be generated or validated.

Once instantiated, the IdP script is executed.  The IdP MUST call the
      register() function on the
      <var>RTCIdentityProviderRegistrar instance during script
      execution.  If an IdP is not registered during this script execution, the
      user agent cannot use the IdP proxy and MUST fail any attempt to interact
      with the IdP.

void register(RTCIdentityProvider idp)

This method is invoked by the IdP when its script is first
          executed.  This registers an instance of
          RTCIdentityProvider with the user agent.

Promise<RTCIdentityAssertionResult>
        generateAssertion(DOMString contents, DOMString origin,
        optional DOMString usernameHint)

A user agent invokes this method on the IdP to request the
          generation of an identity assertion.

The <var>contents</var> parameter includes the information that the
          user agent wants covered by the identity assertion.  A successful
          validation of the provided assertion MUST produce this string.

The <var>origin</var> parameter identifies the origin of the
          RTCPeerConnection that triggered this request.  An
          IdP can use this information as input to policy decisions about
          use.

The IdP selects the identity to assert.  The optional
          <var>usernameHint</var> parameter is the same value that was pass to
          setIdentityProvider.

The IdP provides a promise that resolves to an
          RTCIdentityAssertionResult to successfully
          generate an identity assertion. Any other value, or a rejected
          promise, is treated as an error.

Promise<RTCIdentityValidationResult>
        validateAssertion(DOMString assertion, DOMString origin)

A user agent invokes this method on the IdP to request the
          validation of an identity assertion.

The <var>assertion</var> parameter includes the assertion that was
          recovered from an a=identity in the session description;
          that is, the value that was part of the
          RTCIdentityAssertionResult provided by the IdP
          that generated the assertion.

The <var>origin</var> parameter identifies the origin of the
          RTCPeerConnection that triggered this request.  An
          IdP can use this information as input to policy decisions about
          use.

The IdP returns a Promise that resolves to an
          RTCIdentityValidationResult to successfully
          validate an identity assertion and to provide the actual identity.
          Any other value, or a rejected promise, is treated as an error.

Identity Assertion and Validation Results

required RTCIdentityProviderDetails idp

An IdP provides these details to identify the IdP that validates
            the identity assertion.  This struct contains the same information
            that is provided to setIdentityProvider.

required DOMString assertion

An identity assertion.  This is an opaque string that SHOULD
            contain all information necessary to assert identity.  This value is
            consumed by the validating IdP.

required DOMString domain

The domain name of the IdP that validates the associated identity
            assertion.

DOMString protocol = "default"

The protocol parameter used for the IdP.

required DOMString identity

The validated identity of the peer.

required DOMString contents

The payload of the identity assertion.  An IdP that validates an
            identity assertion MUST return the same string that was provided to
            the original IdP that generated the assertion.

[TODO: This is not sufficient unless we expect the IdP to protect
        this information. Otherwise, the a=identity information can be copied
        from a session with "good" properties to any other session with the
        same fingerprint information. Since we want to reuse credentials, that
        would be bad.]

The identity mechanism MUST provide an indication to the
        remote side of whether it requires the stream contents to be protected.
        Implementations MUST have an user interface that indicates the
        different cases and identity for these.

The user agent uses the <var>contents</var> string to determine if
            the identity assertion matches the session description.

Requesting Identity
      Assertions

The identity assertion request process involves the following
      steps:

The identity assertion request process is triggered by a call to
      createOffer, createAnswer, or
      getIdentityAssertion.  When these calls are invoked and an
      identity provider has been set, the following steps are executed:

The RTCPeerConnection instantiates an IdP proxy as
        described in Identity
        Provider Selection section and waits for the IdP to signal that it
        is ready.

The RTCPeerConnection instantiates an IdP as described
          in  and .  If the IdP cannot be loaded,
          instantiated or the IdP proxy is not registered, this process
          fails.

The RTCPeerConnection sends a "SIGN" message to the IdP
        proxy. This message includes the material
        the RTCPeerConnection desires to be bound to the user's
        identity.

If the user has been authenticated by the IdP, and the IdP is
        willing to generate an identity assertion, the IdP generates an
        identity assertion. This step depends entirely on the IdP. The methods
        by which an IdP authenticates users or generates assertions is not
        specified, though this could involve interacting with the IdP server or
        other servers.

The RTCPeerConnection invokes the generateAssertion
          method on the RTCIdentityProvider instance
          registered by the IdP.

The RTCPeerConnection generates the
          <var>contents</var> parameter to this method as described in
          [[!RTCWEB-SECURITY-ARCH]].  The <var>origin</var> parameter contains
          the origin of the script that calls the RTCPeerConnection
          method that triggers this behavior.  The <var>usernameHint</var> value
          is the same value that is provided to
          setIdentityProvider, if any such value was provided.

The IdP proxy sends a response containing the identity assertion to
        the RTCPeerConnection over the message channel.

The IdP returns a Promise to the RTCPeerConnection.
          If the user has been authenticated by the IdP, and the IdP is willing
          to generate an identity assertion, the IdP resolves the promise with
          an identity assertion in the form of an
          RTCIdentityAssertionResult.

This step depends entirely on the IdP. The methods by which an IdP
          authenticates users or generates assertions is not specified, though
          this could involve interacting with the IdP server or other
          servers.

The RTCPeerConnection MAY store the identity assertion
        for use with future offers or answers.

The RTCPeerConnection MAY store the identity assertion
          for use with future offers or answers.

If the identity request was triggered by a
        createOffer() or createAnswer(), then the
        assertion is inserted in the offer/answer SDP.

If the identity request was triggered by a
          createOffer() or createAnswer(), then the
          assertion is converted to a JSON string, base64-encoded and inserted
          into an a=identity attribute in the session
          description.

The format and contents of the messages that are exchanged are
      described in detail in [[!RTCWEB-SECURITY-ARCH]].

The IdP proxy can return an "ERROR" response. If an error is
      encountered, the browser MUST generate an idpassertionerror event. No
      "a=identity" attribute is added to SDP as a result.

This process can fail.  The IdP proxy MAY reject the promise, or the
      process of loading and registering the IdP could fail.  If assertion
      generation fails, then the promise for the corresponding function call is
      rejected.

The browser SHOULD limit the time that it will allow for this process.
      This includes both the loading of the <a href=
@@ -4088,6 +4221,8 @@
Requesting Identity

User Login Procedure

This needs a new rejection process

An IdP could respond to a request to generate an identity assertion
        with a "LOGINNEEDED" error. This indicates that the site does not have
        the necessary information available to it (such as cookies) to
@@ -4125,90 +4260,123 @@
Verifying Identity Assertions

Identity assertion validation happens when setRemoteDescription
      is invoked on RTCPeerConnection. The process runs
      asynchronously, meaning that validation of an identity assertion does not
      asynchronously, meaning that validation of an identity assertion might not
      block the completion of setRemoteDescription.

The identity assertion request process involves the following
      steps:

      asynchronous steps:

The RTCPeerConnection instantiates an IdP proxy as
        described in Identity
        Provider Selection section and waits for the IdP to signal that it
        is ready.

Only one identity validation can run at a time for an
          RTCPeerConnection.  If there is an outstanding identity
          validation in progress, await its completion.  This can happen because
          the resolution of setRemoteDescription is not blocked by
          identity validation unless there is a target peer identity.

The RTCPeerConnection loads the identity assertion
          from the session description and decodes the base64 value, then parses
          the resulting JSON.  The <var>idp</var> paramter of the resulting
          dictionary contains a <var>domain</var> and an optional
          <var>protocol</var> value that identifies the IdP, as described in
          [[!RTCWEB-SECURITY-ARCH]].

The RTCPeerConnection instantiates the identified IdP
          as described in  and
          .  If the IdP cannot be loaded,
          instantiated or the IdP proxy is not registered, this process
          fails.

The RTCPeerConnection sends a "VERIFY" message to the
        IdP proxy. This message includes the assertion from the offer/answer
        which is to be verified.

The IdP proxy verifies the identity assertion (depending on the
        authentication protocol this could involve interacting with the IDP
        server).

The RTCPeerConnection invokes the validateAssertion
          method on the RTCIdentityProvider instance
          registered by the IdP.

The <var>assertion</var> parameter is taken from the decoded
          identity assertion.  The <var>origin</var> parameter contains the
          origin of the script that calls the RTCPeerConnection
          method that triggers this behavior.

Once the assertion is verified, the IdP proxy sends a response
        containing the verified assertion results to the
        RTCPeerConnection over the message channel.

The IdP proxy returns a promise and performs the validation process
          asynchronously.

The IdP proxy verifies the identity assertion using whatever means
          necessary.  Depending on the authentication protocol this could
          involve interacting with the IDP server.

The RTCPeerConnection validates that the fingerprint
        provided by the IdP in the validation response matches the certificate
        fingerprint that is, or will be, used for communications. This is
        either by:

Once the assertion is successfully verified, the IdP proxy resolves
          the promise with an RTCIdentityValidationResult
          containing the validated identity and the original contents that are
          the payload of the assertion.

Ensuring that there is only a single a=fingerprint value across
            all media sections in the SDP that matches the fingerprint provided
            by the IdP.

The RTCPeerConnection decodes the contents and
          validates that it contains at least one fingerprint value for each
          a=fingerprint attribute in the session description.  This
          ensures that the certificate that is, or will be, used by the remote
          peer for communications is covered by the identity assertion.

A user agent MUST NOT permit communication with a peer, if that
          peer offers a certificate that doesn't match an
          a=fingerprint line in the negotiated session
          description.

Waiting for all DTLS connections to be establishes and checking
            that the certificate fingerprints on all connections matches the
            one provided by the IdP.

The RTCPeerConnection validates that the domain
          portion of the identity matches the domain of the IdP as described in
          [[!RTCWEB-SECURITY-ARCH]].

The RTCPeerConnection validates that the domain
        portion of the identity matches the domain of the IdP as described in
        [[!RTCWEB-SECURITY-ARCH]].

The RTCPeerConnection stores the assertion in the
        peerIdentity
        attribute and raises a simple event named peeridentity at itself. The assertion information to be
        displayed MUST contain the domain name of the IdP as provided in the
        assertion.

The RTCPeerConnection resolves the peerIdentity
          attribute with a new instance of RTCIdentityAssertion
          that includes the IdP domain and peer identity.

The browser MAY display identity information to a user in browser
        UI. Any user identity information that is displayed in this fashion
        MUST use a mechanism that cannot be spoofed by content.

The browser MAY display identity information to a user in browser
          UI. Any user identity information that is displayed in this fashion
          MUST use a mechanism that cannot be spoofed by content.

The IdP might fail to validate the identity assertion by providing an
      "ERROR" response to the validation request. Validation can also fail due
      to the additional checks performed by the browser. In both cases, the
      process terminates and no identity information is exposed to the
      application or the user.

This process can fail at almost every step of the above process.  If
      the process fails, the peerIdentity promise is
      rejected with a DOMError that has a name of
      IdpError.

The browser MUST raise an idpvalidationerror event if
      validation of an identity assertion fails for any reason.

If this process fails and there is a target peer identity for the
      RTCPeerConnection, the promise returned by
      setRemoteDescription is also rejected.

If the "peerIdentity" constraint is applied to the
      RTCPeerConnection, any error MUST cause setRemoteDescription
      to fail.

If this process fails and there is not a target peer identity, the value of the
      peerIdentity MUST be set
      to a new, unresolved promise instance.  This permits the use of
      renegotiation (or a subsequent answer, if the session description was a
      provisional answer) to resolve or reject the identity.

The browser SHOULD limit the time that it will allow for this process.
      This includes both the loading of the IdP proxy and the identity
      assertion validation. Failure to do so potentially causes the
      corresponding operation to take an indefinite amount of time. This timer
      can be cancelled when the IdP produces a response. The timer running to
      completion can be treated as equivalent to an error from the IdP.

The format and contents of the messages that are exchanged are
      described in detail in [[!RTCWEB-SECURITY-ARCH]].

      assertion validation. Failure to do so potentially causes the operation to
      take an indefinite amount of time. This timer can be cancelled when the
      IdP produces a response. The timer running to completion can be treated as
      equivalent to an error from the IdP.

@@ -4219,16 +4387,16 @@
RTCPeerConnection Interface Extensions

void setIdentityProvider(DOMString provider, optional DOMString
        protocol, optional DOMString username)

        protocol, optional DOMString usernameHint)

Sets the identity provider to be used for a given
          RTCPeerConnection object. Applications need not make
          this call; if the browser is already configured for an IdP, then that
          configured IdP will be used to get an assertion.

          RTCPeerConnection object. Applications need not make this
          call; if the browser is already configured for an IdP, then that
          configured IdP might be used to get an assertion.

When the <dfn id=
          "dom-peerconnection-setidentityprovider">setIdentityProvider()</dfn>

When the <dfn
          id="dom-peerconnection-setidentityprovider">setIdentityProvider()</dfn>
          method is invoked, the user agent MUST run the following steps:

@@ -4243,7 +4411,7 @@
RTCPeerConnection Interface Extensions

Set the current identity provider values to the triplet
              (provider, protocol,
              username).

              usernameHint).

@@ -4254,11 +4422,12 @@
RTCPeerConnection Interface Extensions

Identity provider information is not used until an identity
          assertion is required, either in response to a call to
          getIdentityAssertion, or the need to generate SDP with
          either createOffer or createAnswer.

          getIdentityAssertion, or a session description is
          requested with a call to either createOffer or
          createAnswer.

void getIdentityAssertion()

Promise<DOMString> getIdentityAssertion()

Initiates the process of obtaining an identity assertion.
@@ -4278,119 +4447,52 @@
RTCPeerConnection Interface Extensions

If the <var>connection</var>'s RTCPeerConnection
              signalingState is closed, abort these steps.

Request an
              identity assertion from the IdP.

Resolve the promise with the base64 and JSON encoded
              assertion.

readonly attribute RTCIdentityAssertion? peerIdentity

readonly attribute Promise<RTCIdentityAssertion> peerIdentity

Contains the peer identity assertion information if an identity
          assertion was provided and verified. Once this value is set to a
          non-<var>null</var> value, it cannot change.

A promise that resolves with the identity of the peer if the
          identity is successfully validated.

This promise is rejected if an identity assertion is present in a
          remote session description and validation of that assertion fails for
          any reason.  If the promise is rejected, a new unresolved value is
          created, unless there a target peer
          identity has been established.  If this promise successfully
          resolves, the value will not change.

attribute EventHandler onidentityresult

This event handler, of event handler event type identityresult, MUST be fired by
        all objects implementing the RTCPeerConnection
        interface. This event is fired when an identity assertion is
        successfully generated. Note: this event is fired when an identity
        assertion is generated during the creation of an offer or answer.

attribute EventHandler onpeeridentity

This simple event handler of type peeridentity MUST be fired when a peer
        identity from a peer is successfully validated.

attribute EventHandler onidpassertionerror

This event handler of type idpassertionerror MUST be fired
        when an IdP encounters an error in generating an identity
        assertion.

attribute EventHandler onidpvalidationerror

This event handler of type idvalidationperror MUST be fired
        when an IdP encounters an error in validating an identity
        assertion.

RTCIdentityAssertion Type

DOMString idp

attribute DOMString idp

A domain name representing the identity provider.

The domain name of the identity provider that validated this identity.

DOMString name

attribute DOMString name

An RFC5322-conformant [[RFC5322]] representation of the verified
          peer identity. This identity will have been verified via the
          procedures described in [RTCWEB-SECURITY-ARCH].

          procedures described in [[!RTCWEB-SECURITY-ARCH]].

RTCIdentityEvent Type

The <dfn>RTCIdentiytEvent</dfn> is raised when an IdP
      produces an identity assertion.

attribute DOMString assertion

A string containing the encoded identity assertion (the
          information that would be added to the "a=identity" line in SDP
          [[!RTCWEB-SECURITY-ARCH]]).

RTCIdentityErrorEvent Type

The <dfn>RTCIdentityErrorEvent</dfn> is raised when an
      IdP fails to successfully produce an identity assertion.

attribute DOMString idp

The domain name of the identity provider that is providing the
        error response.

attribute DOMString protocol

The IdP protocol that is in use.

attribute DOMString? loginUrl

An IdP that is unable to generate an identity assertion due to a
        lack of sufficient user authentication information can provide a <dfn title='loginUrl'>URL</dfn> to
        a page where the user can complete authentication. If the IdP provides
        this URL, this attribute includes the value provided by the IdP.

Examples

 @@ -4414,10 +4516,8 @@
Examples

This example shows how to consume identity assertions inside a Web
        application.

  pc.onpeeridentity = function(e) {
    console.log("IdP= " + e.target.peerIdentity.idp +
                " identity=" + e.target.peerIdentity.name);
  };
  pc.peerIdentity.then(identity =>
    console.log("IdP= " + identity.idp + " identity=" + identity.name));

@@ -5369,49 +5469,6 @@
Event summary

          the <var>isolated</var> attribute on a MediaStreamTrack
          changes.

          <dfn id=
          "event-identityresult">identityresult</dfn>

           RTCIdentityEvent

           A new RTCIdentityEvent is dispatched to the
          script when an identity assertion is successfully generated by an
          IdP.

          peeridentity

           Event

           A new Event is dispatched to the script when
          an identity assertion provided by a peer is successfully
          validated.

          <dfn id=
          "event-idpassertionerror">idpassertionerror</dfn>

           RTCIdentityErrorEvent

           A new RTCIdentityErrorEvent is dispatched to
          the script when an IdP encounters an error while generating an
          identity assertion.

          <dfn id=
          "event-idpvalidationerror">idpvalidationerror</dfn>

           RTCIdentityErrorEvent

           A new RTCIdentityErrorEvent is dispatched to
          the script when an IdP encounters an error while validating an
          identity assertion.

 @@ -5593,7 +5650,9 @@
Changes since December 5, 2014

      replaced by same-named overloads using Promises instead.

[PR #194] Added first version of Security Considerations (more work
      needed)

        needed)

Updated identity provider structure.


Используй понятные название, am -> amount


Registration pull request created: [JuliaRegistries/General/8434](https://github.com/JuliaRegistries/General/pull/8434)

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if [Julia TagBot](https://github.com/apps/julia-tagbot) is installed, or can be done manually through the github interface, or via:
```
git tag -a v0.2.1 -m "<description of version>" 2ea0ffe11046331637eb2e7b813ba674afeb7509
git push origin v0.2.1
```


Successfully deployed to following URLs:

* https://airballs-next-k426z2epg.now.sh
* https://airballs-next.now.sh
* https://airballs-next.yummyairballs.now.sh
* https://airballs-next-git-master.yummyairballs.now.sh


Successfully deployed to following URLs:

* https://schemeapp-nd39lzhgu.now.sh
* https://*.schemeapp.cloud
* https://schemeapp.adenaikeyomi.now.sh
* https://schemeapp-git-master.adenaikeyomi.now.sh


Successfully deployed to following URLs:

* https://personal-website-7frcpz1hn.now.sh
* https://anthony.codes
* https://antifa.sh
* https://antifa.app
* https://www.anthony.codes
* https://anthony.app
* https://www.anthony.app
* https://www.antifa.sh
* https://www.antifa.app
* https://antifa.dev
* https://www.antifa.dev
* https://personal-website.4cm4k1.now.sh
* https://personal-website-git-master.4cm4k1.now.sh


Думаю так будет поизящнее: interest.forEach { stringArray.append($0.name ?? "") }


Successfully deployed to following URLs:

* https://wanders-drc4crmtr.now.sh
* https://wanders.now.sh
* https://vadrouilles.co
* https://wanders.ys1.now.sh
* https://wanders-git-master.ys1.now.sh


❌ Status for 'xamarin-macios - sample testing (build)': [failure](https://dev.azure.com/xamarin//internal/_build/results?buildId=13065).

* ❌ Debug_iPhone_AF: Canceled
* ✅ Debug_iPhone_GR: Succeeded
* ❌ Debug_iPhone_SZ: Failed
* ✅ Debug_iPhoneSimulator: Succeeded
* ✅ Release_iPhone_AF: Succeeded
* ✅ Release_iPhone_GR: Succeeded
* ❌ Release_iPhone_SZ: Failed
* ✅ Release_iPhoneSimulator: Succeeded
* ✅ Debug_Mac: Succeeded
* ✅ Release_Mac: Succeeded
* ✅ PublishPerformanceData: Succeeded


Successfully deployed to following URLs:

* https://airballs-next-a3tuhpal2.now.sh
* https://airballs-next.now.sh
* https://airballs-next.yummyairballs.now.sh
* https://airballs-next-git-master.yummyairballs.now.sh


Successfully deployed to following URLs:

* https://gloomkit-lqb3ke7wr.now.sh
* https://gloomkit.now.sh
* https://gloomkit.tripphamm.now.sh
* https://gloomkit-git-master.tripphamm.now.sh


@LukeSmithxyz in line 343 "--no-startup-id" is redundant


Successfully deployed to following URLs:

* https://airballs-next-qrv74tfz7.now.sh
* https://airballs-next.now.sh
* https://airballs-next.yummyairballs.now.sh
* https://airballs-next-git-master.yummyairballs.now.sh


Successfully deployed to following URLs:

* https://zpie-dep5zlphw.now.sh
* https://zpie.now.sh
* https://zpie.brucegne.now.sh
* https://zpie-git-master.brucegne.now.sh