Skip to content

[Bcl][Tests] Ignore the ssl related bcl tests that block.#6228

Closed
mandel-macaque wants to merge 1 commit intodotnet:mono-2019-06from
mandel-macaque:ignore-blocking-tests
Closed

[Bcl][Tests] Ignore the ssl related bcl tests that block.#6228
mandel-macaque wants to merge 1 commit intodotnet:mono-2019-06from
mandel-macaque:ignore-blocking-tests

Conversation

@mandel-macaque
Copy link
Copy Markdown
Contributor

There are a number of tests that block in the BCL relatd to ssl, mono
issue mono/mono#14938 was added to track them.

There are a number of tests that block in the BCL relatd to ssl, mono
issue mono/mono#14938 was added to track them.
@marek-safar marek-safar modified the milestone: 2019-06 Jun 10, 2019
@mandel-macaque
Copy link
Copy Markdown
Contributor Author

Closing since we can push to the monthly branch directly.

@monojenkins
Copy link
Copy Markdown
Contributor

Build failure
Build succeeded
API Diff (from stable)
🔥 Failed to compare API and create generator diff 🔥
    ** Error: Working directory isn't clean:
    HEAD detached at b8dba0e
    Untracked files:
    (use "git add ..." to include in what will be committed)
    
    tests/bcl-test/BCL tests group 1.csproj
    tests/bcl-test/BCL tests group 2.csproj
    tests/bcl-test/BCL tests group 3.csproj
    tests/bcl-test/BCL tests group 4.csproj
    tests/bcl-test/BCL tests group 6.csproj
    tests/bcl-test/Mac OS X BCL tests group 1-mac-full.csproj
    tests/bcl-test/Mac OS X BCL tests group 1-mac-modern.csproj
    tests/bcl-test/Mac OS X BCL tests group 2-mac-full.csproj
    tests/bcl-test/Mac OS X BCL tests group 2-mac-modern.csproj
    tests/bcl-test/Mac OS X BCL tests group 3-mac-full.csproj
    tests/bcl-test/Mac OS X BCL tests group 3-mac-modern.csproj
    tests/bcl-test/Mac OS X BCL tests group 4-mac-full.csproj
    tests/bcl-test/Mac OS X BCL tests group 4-mac-modern.csproj
    tests/bcl-test/generated/
    tests/bcl-test/mscorlib-mac-full.csproj
    tests/bcl-test/mscorlib-mac-modern.csproj
    tests/bcl-test/mscorlib.csproj
    
    nothing added to commit but untracked files present (use "git add" to track)
    Search for Comparing API & creating generator diff in the log to view the complete log.
🔥 Test run failed 🔥

Test results

43 tests failed, 112 tests passed.

Failed tests

  • apitest/Mac Classic/NonSystem: BuildFailure
  • dont link/Mac Classic/All: BuildFailure
  • introspection/Mac Classic/Modern: BuildFailure
  • [xUnit] Mono Mac OS X BCL tests group 4/Mac/Full: TimedOut (Execution timed out after 1200 seconds.)
  • [xUnit] Mono Mac OS X BCL tests group 4/Mac/Modern: TimedOut (Execution timed out after 1200 seconds.)
  • [xUnit] Mono BCL tests group 4/iOS Unified 32-bits - simulator/Debug: Failed
  • [xUnit] Mono BCL tests group 4/iOS Unified 64-bits - simulator/Debug: Failed
  • monotouch-test/tvOS - simulator/Debug: Failed
  • [xUnit] Mono BCL tests group 4/tvOS - simulator/Debug: Failed
  • monotouch-test/tvOS - simulator/Debug (LinkSdk): Failed
  • monotouch-test/tvOS - simulator/Debug (static registrar): Failed
  • monotouch-test/tvOS - simulator/Release (all optimizations): Failed
  • [NUnit] Mono SystemCoreTests/watchOS 32-bits - simulator/Debug: Crashed
  • [NUnit] Mono SystemRuntimeSerializationTests/watchOS 32-bits - simulator/Debug: Crashed
  • [NUnit] Mono SystemTransactionsTests/watchOS 32-bits - simulator/Debug: Crashed
  • [NUnit] Mono SystemXmlTests/watchOS 32-bits - simulator/Debug: Crashed
  • [NUnit] Mono SystemXmlLinqTests/watchOS 32-bits - simulator/Debug: Crashed
  • [NUnit] Mono SystemComponentModelDataAnnotationsTests/watchOS 32-bits - simulator/Debug: Crashed
  • [NUnit] Mono SystemJsonTests/watchOS 32-bits - simulator/Debug: Crashed
  • [NUnit] Mono SystemServiceModelWebTests/watchOS 32-bits - simulator/Debug: Crashed
  • [NUnit] Mono SystemIOCompressionTests/watchOS 32-bits - simulator/Debug: Crashed
  • [NUnit] Mono MonoDataSqliteTests/watchOS 32-bits - simulator/Debug: Crashed
  • [NUnit] Mono MonoRuntimeTests/watchOS 32-bits - simulator/Debug: Crashed
  • [NUnit] Mono SystemTests/watchOS 32-bits - simulator/Debug: Crashed
  • [NUnit] Mono SystemDataTests/watchOS 32-bits - simulator/Debug: Crashed
  • [NUnit] Mono SystemNetHttpTests/watchOS 32-bits - simulator/Debug: Crashed
  • [NUnit] Mono SystemServiceModelTests/watchOS 32-bits - simulator/Debug: Crashed
  • [NUnit] Mono CorlibTests/watchOS 32-bits - simulator/Debug: Crashed
  • [NUnit] Mono SystemWebServicesTests/watchOS 32-bits - simulator/Debug: Crashed
  • [xUnit] Mono SystemDataXunit/watchOS 32-bits - simulator/Debug: Crashed
  • [xUnit] Mono SystemSecurityXunit/watchOS 32-bits - simulator/Debug: Crashed
  • [xUnit] Mono SystemLinqXunit/watchOS 32-bits - simulator/Debug: Crashed
  • [xUnit] Mono SystemXmlXunit/watchOS 32-bits - simulator/Debug: Crashed
  • [xUnit] Mono SystemRuntimeCompilerServicesUnsafeXunit/watchOS 32-bits - simulator/Debug: Crashed
  • [xUnit] Mono SystemNumericsXunit/watchOS 32-bits - simulator/Debug: Crashed
  • [xUnit] Mono SystemCoreXunit/watchOS 32-bits - simulator/Debug: Crashed
  • [xUnit] Mono SystemXunit/watchOS 32-bits - simulator/Debug: Crashed
  • [xUnit] Mono MicrosoftCSharpXunit/watchOS 32-bits - simulator/Debug: Crashed
  • [xUnit] Mono SystemNetHttpUnitTestsXunit/watchOS 32-bits - simulator/Debug: Crashed
  • monotouch-test/watchOS 32-bits - simulator/Debug (LinkSdk): Crashed
  • monotouch-test/watchOS 32-bits - simulator/Debug (static registrar): Crashed
  • monotouch-test/watchOS 32-bits - simulator/Release (all optimizations): Crashed
  • MSBuild tests/iOS: Failed (Execution failed with exit code 1)

jonpryor added a commit to dotnet/android that referenced this pull request Jun 17, 2019
radekdoulik pushed a commit to dotnet/android that referenced this pull request Jul 15, 2019
Bump to mono/2019-06 branch and set mono required versions.

[cecil] Fix the cecil build by reverting "Add a solution file for remap-assembly-ref (#3248)"

Using the solution instead of csproj broke the cecil build. I didn't
traced all the details, but we ended up with compiling
`Mono.Cecil.dll` without any references.

Use 7z when downloading Mono Archives 

[xaprepare] Drop llvm32 cross compilers

Mono has just dropped the llvm32 cross compilers because it is now possible to
cross compile to 32-bit using the 64-bit compiler.

Remove requirement for 32-bit llvm runtime in preparation stage.

[tests] Updated Xamarin.Android.Net tests

Update Properties_Invalid test to reflect current implementation

This was testing part of our old HttpClientHandler implementation
introduced here:
mono/mono@f97e03f

The current corefx implementation doesn't throw when `UseProxy` is
false. The documentation doesn't specify such behavior, so I assume it
was specific for our old implementaion.

Context:
https://docs.microsoft.com/en-us/dotnet/api/system.net.http.httpclienthandler.proxy?view=netframework-4.8
https://docs.microsoft.com/en-us/dotnet/api/system.net.http.httpclienthandler.useproxy?view=netframework-4.8
https://github.com/mono/corefx/blob/9354dfd8d3cd4af62592bee9d8fe434e5694788a/src/System.Net.Http/src/System/Net/Http/HttpClientHandler.Unix.cs#L242
https://github.com/mono/corefx/blob/9354dfd8d3cd4af62592bee9d8fe434e5694788a/src/System.Net.Http/src/System/Net/Http/SocketsHttpHandler/SocketsHttpHandler.cs#L75
https://github.com/mono/corefx/blob/9354dfd8d3cd4af62592bee9d8fe434e5694788a/src/System.Net.Http/src/System/Net/Http/CurlHandler/CurlHandler.cs#L234

Remove broken HttpClient test

Context: #3155 (comment)

[linker] Disable linker's UnreachableBodies optimization

Disable it for now til we find out a fix.

Context: #3202

[jnimarshalmethod-gen] Introduce MonoAndroidLibDirectory property

As we have switched to dynamically linker mono recently, we need to have
libmonosgen in dyld path. So we set `DYLD_LIBRARY_PATH` for `mono`
when running `jnimarshalmethod-gen`

[tests] Exclude network tests which hang.

Context: mono/mono#14938
Context: dotnet/macios#6228

[xamarin-android-api-compatibility] API changes

System.IO.Enumeration.FileSystemName and
System.Security.Cryptography.CryptographicOperations classes were
removed from System.xml as they were duplicates of mscorlib ones. They
were removed as part of NS2.1 work in mono.

They were added by mistake and removed later. Because they were
already present in 16.1 and 16.2 respectively, mono team added type
forwarders to `System.dll` to avoid/lessen API breakage.

System.dll now contains:

	.class extern forwarder System.IO.Enumeration.FileSystemName
	{
	  .assembly extern mscorlib
	}
	.class extern forwarder System.Security.Cryptography.CryptographicOperations
	{
	  .assembly extern mscorlib
	}

Context:
mono/mono@ba719ac
#3155 (comment)

3 extension methods extracted from
`System.Threading.Tasks.TaskExtensions` to a new
`System.Threading.Tasks.TaskAsyncEnumerableExtensions` class.

They stay in the same namespace and being extension methods, they
should not break anything.

	public static System.Runtime.CompilerServices.ConfiguredCancelableAsyncEnumerable<T> ConfigureAwait<T> (this System.Collections.Generic.IAsyncEnumerable<T>, bool);
	public static System.Runtime.CompilerServices.ConfiguredAsyncDisposable ConfigureAwait (this System.IAsyncDisposable, bool);
	public static System.Runtime.CompilerServices.ConfiguredCancelableAsyncEnumerable<T> WithCancellation<T> (this System.Collections.Generic.IAsyncEnumerable<T>, System.Threading.CancellationToken);

Context:
dotnet/standard@ebeec50#diff-93ef3714cd10edf17d6d8045cf3406b8
#3155 (comment)
radekdoulik pushed a commit to dotnet/android that referenced this pull request Jul 16, 2019
Bump to mono/2019-06 branch and set mono required versions.

[cecil] Fix the cecil build by reverting "Add a solution file for remap-assembly-ref (#3248)"

Using the solution instead of csproj broke the cecil build. I didn't
traced all the details, but we ended up with compiling
`Mono.Cecil.dll` without any references.

Use 7z when downloading Mono Archives

[xaprepare] Drop llvm32 cross compilers

Mono has just dropped the llvm32 cross compilers because it is now possible to
cross compile to 32-bit using the 64-bit compiler.

Remove requirement for 32-bit llvm runtime in preparation stage.

[tests] Updated Xamarin.Android.Net tests

Update Properties_Invalid test to reflect current implementation

This was testing part of our old HttpClientHandler implementation
introduced here:
mono/mono@f97e03f

The current corefx implementation doesn't throw when `UseProxy` is
false. The documentation doesn't specify such behavior, so I assume it
was specific for our old implementaion.

Context:
https://docs.microsoft.com/en-us/dotnet/api/system.net.http.httpclienthandler.proxy?view=netframework-4.8
https://docs.microsoft.com/en-us/dotnet/api/system.net.http.httpclienthandler.useproxy?view=netframework-4.8
https://github.com/mono/corefx/blob/9354dfd8d3cd4af62592bee9d8fe434e5694788a/src/System.Net.Http/src/System/Net/Http/HttpClientHandler.Unix.cs#L242
https://github.com/mono/corefx/blob/9354dfd8d3cd4af62592bee9d8fe434e5694788a/src/System.Net.Http/src/System/Net/Http/SocketsHttpHandler/SocketsHttpHandler.cs#L75
https://github.com/mono/corefx/blob/9354dfd8d3cd4af62592bee9d8fe434e5694788a/src/System.Net.Http/src/System/Net/Http/CurlHandler/CurlHandler.cs#L234

Remove broken HttpClient test

Context: #3155 (comment)

[linker] Disable linker's UnreachableBodies optimization

Disable it for now til we find out a fix.

Context: #3202

[jnimarshalmethod-gen] Introduce MonoAndroidLibDirectory property

As we have switched to dynamically linker mono recently, we need to have
libmonosgen in dyld path. So we set `DYLD_LIBRARY_PATH` for `mono`
when running `jnimarshalmethod-gen`

[tests] Exclude network tests which hang.

Context: mono/mono#14938
Context: dotnet/macios#6228

[xamarin-android-api-compatibility] API changes

System.IO.Enumeration.FileSystemName and
System.Security.Cryptography.CryptographicOperations classes were
removed from System.xml as they were duplicates of mscorlib ones. They
were removed as part of NS2.1 work in mono.

They were added by mistake and removed later. Because they were
already present in 16.1 and 16.2 respectively, mono team added type
forwarders to `System.dll` to avoid/lessen API breakage.

System.dll now contains:

	.class extern forwarder System.IO.Enumeration.FileSystemName
	{
	  .assembly extern mscorlib
	}
	.class extern forwarder System.Security.Cryptography.CryptographicOperations
	{
	  .assembly extern mscorlib
	}

Context:
mono/mono@ba719ac
#3155 (comment)

3 extension methods extracted from
`System.Threading.Tasks.TaskExtensions` to a new
`System.Threading.Tasks.TaskAsyncEnumerableExtensions` class.

They stay in the same namespace and being extension methods, they
should not break anything.

	public static System.Runtime.CompilerServices.ConfiguredCancelableAsyncEnumerable<T> ConfigureAwait<T> (this System.Collections.Generic.IAsyncEnumerable<T>, bool);
	public static System.Runtime.CompilerServices.ConfiguredAsyncDisposable ConfigureAwait (this System.IAsyncDisposable, bool);
	public static System.Runtime.CompilerServices.ConfiguredCancelableAsyncEnumerable<T> WithCancellation<T> (this System.Collections.Generic.IAsyncEnumerable<T>, System.Threading.CancellationToken);

Context:
dotnet/standard@ebeec50#diff-93ef3714cd10edf17d6d8045cf3406b8
#3155 (comment)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants