Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[wasm][tests][aot] System.IO.Pipelines.Tests - failing tests #50959

Closed
radical opened this issue Apr 8, 2021 · 7 comments
Closed

[wasm][tests][aot] System.IO.Pipelines.Tests - failing tests #50959

radical opened this issue Apr 8, 2021 · 7 comments
Labels
arch-wasm WebAssembly architecture area-Codegen-AOT-mono disabled-test The test is disabled in source code against the issue untriaged New issue has not been triaged by the area owner wasm-aot-test WebAssembly AOT Test
Milestone
6.0.0

Comments

@radical
Copy link
Member

radical commented Apr 8, 2021 •
edited
Loading

This can be reproduced on main.

Logs

[19:45:14] fail: [FAIL] System.IO.Pipelines.Tests.PipelineReaderWriterFacts.ReadAsync_ThrowsIfWriterCompletedWithException
[19:45:14] info: Assert.Contains() Failure
[19:45:14] info: Not found: ThrowTestException
[19:45:14] info: In value:
[19:45:14] info: 
[19:45:14] fail: [FAIL] System.IO.Pipelines.Tests.PipelineReaderWriterFacts.WriteAsync_ThrowsIfReaderCompletedWithException
[19:45:14] info: Assert.Contains() Failure
[19:45:14] info: Not found: ThrowTestException
[19:45:14] info: In value:
[19:45:14] info: 
[19:45:14] fail: [FAIL] System.IO.Pipelines.Tests.FlushAsyncTests.FlushAsync_ThrowsIfWriterReaderWithException
[19:45:14] info: Assert.Contains() Failure
[19:45:14] info: Not found: ThrowTestException
[19:45:14] info: In value:
[19:45:14] info: 
[19:45:15] info: Finished:    System.IO.Pipelines.Tests.dll
@radical radical added arch-wasm WebAssembly architecture area-Codegen-AOT-mono wasm-aot-test WebAssembly AOT Test labels Apr 8, 2021
@ghost
Copy link

ghost commented Apr 8, 2021

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

Logs

[19:45:14] fail: [FAIL] System.IO.Pipelines.Tests.PipelineReaderWriterFacts.ReadAsync_ThrowsIfWriterCompletedWithException
[19:45:14] info: Assert.Contains() Failure
[19:45:14] info: Not found: ThrowTestException
[19:45:14] info: In value:
[19:45:14] info: 
[19:45:14] fail: [FAIL] System.IO.Pipelines.Tests.PipelineReaderWriterFacts.WriteAsync_ThrowsIfReaderCompletedWithException
[19:45:14] info: Assert.Contains() Failure
[19:45:14] info: Not found: ThrowTestException
[19:45:14] info: In value:
[19:45:14] info: 
[19:45:14] fail: [FAIL] System.IO.Pipelines.Tests.FlushAsyncTests.FlushAsync_ThrowsIfWriterReaderWithException
[19:45:14] info: Assert.Contains() Failure
[19:45:14] info: Not found: ThrowTestException
[19:45:14] info: In value:
[19:45:14] info: 
[19:45:15] info: Finished:    System.IO.Pipelines.Tests.dll
Author: radical
Assignees: -
Labels:

arch-wasm, area-Codegen-AOT-mono, wasm-aot-test
Milestone: -

@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Apr 8, 2021
@SamMonoRT SamMonoRT added this to the 6.0.0 milestone Apr 9, 2021
@radical radical added the disabled-test The test is disabled in source code against the issue label Apr 23, 2021
@radical radical mentioned this issue Apr 28, 2021
Closed
@radical
Copy link
Member Author

radical commented May 6, 2021

This seems to be timing out now:

[10:39:45] info: Starting:    System.IO.Pipelines.Tests.dll
[10:40:15] fail: [FAIL] System.IO.Pipelines.Tests.FlushAsyncTests.FlushAsync_ThrowsIfWriterReaderWithException
[10:40:15] info: Assert.Contains() Failure
[10:40:15] info: Not found: ThrowTestException
[10:40:15] info: In value:
[10:40:15] info: 
[10:40:15] fail: console.error: ThreadPool Callback threw an unhandled exception of type System.InvalidOperationException
                 
[10:54:43] info: Process 4113 didn't exit within 00:15:00 and will be killed
                 
[10:54:43] info: Killing process tree of 4113...
                 
[10:54:43] info: Pids to kill: 4113, 4114
                 
[10:54:43] info: Running lldb diagnostics for pid 4113
                 
[10:54:43] info: Printing backtrace for pid=4113
                 
[10:54:43] info: lldb was not found, skipping diagnosis..
                 
[10:54:43] info: Running lldb diagnostics for pid 4114
                 
[10:54:43] info: Printing backtrace for pid=4114
                 
[10:54:43] info: lldb was not found, skipping diagnosis..
                 
[10:54:43] info: 4113 Execution timed out after 900 seconds and the process was killed.
                 
[10:54:43] info: Process v8 exited with 137

@radical radical changed the title [wasm][tests][aot] System.IO.Pipelines.Tests failures [wasm][tests][aot] System.IO.Pipelines.Tests - timing out May 6, 2021
radical added a commit to radical/runtime that referenced this issue May 6, 2021
@radical
Disable Microsoft.Extensions.Logging.Generators, and System.IO.Pipelines
6d81589 
Issue: dotnet#52384
Issue: dotnet#50959
lewing pushed a commit that referenced this issue May 7, 2021
@radical
[wasm][aot] Update disabled tests to track new fixes on main (#52396)
d36313d 
* [wasm][aot] System.Runtime.Tests failing with a different issue now

The earlier one (#51960) was
fixed.
New: #52393

* Enable Common.Tests test tracked in #50955, already fixed on main

* [wasm] System.Reflection.Tests - update to track change from crash to a

.. test failure.
Issue: #51673

* Re-enable System.Collections.Tests, issue: #51037

* Disable Microsoft.Extensions.Logging.Generators, and System.IO.Pipelines

Issue: #52384
Issue: #50959

* Enable two System.Reflection.Metadata* tests

Issue: #51958

* Fix path for Microsoft.Extensions.Logging.Generators.Tests
@radical
Copy link
Member Author

radical commented Jun 10, 2021

3 failing tests

[22:24:27] fail: [FAIL] System.IO.Pipelines.Tests.PipelineReaderWriterFacts.ReadAsync_ThrowsIfWriterCompletedWithException
[22:24:27] info: The collection was expected to contain a single element, but it was empty.
[22:24:27] info:    at System.IO.Pipelines.Tests.PipelineReaderWriterFacts.ReadAsync_ThrowsIfWriterCompletedWithException()
[22:24:27] info: --- End of stack trace from previous location ---
[22:24:28] fail: [FAIL] System.IO.Pipelines.Tests.FlushAsyncTests.FlushAsync_ThrowsIfWriterReaderWithException
[22:24:28] info: The collection was expected to contain a single element, but it was empty.
[22:24:28] info:    at System.IO.Pipelines.Tests.FlushAsyncTests.FlushAsync_ThrowsIfWriterReaderWithException()
[22:24:28] info: --- End of stack trace from previous location ---

@radical radical changed the title [wasm][tests][aot] System.IO.Pipelines.Tests - timing out [wasm][tests][aot] System.IO.Pipelines.Tests - failing tests Jun 10, 2021
@lewing
Copy link
Member

lewing commented Jun 15, 2021

These are all AOT stack trace issues

@radical
Copy link
Member Author

radical commented Jun 16, 2021

Closing this in favor of #50957, because as Larry said the failures are all AOT stack trace issues.

@radical radical mentioned this issue Jun 16, 2021
Open
@radical radical closed this as completed Jun 16, 2021
@VincentBu
Copy link
Contributor

Failed again in runtime 20210701.106

Failed test:

net6.0-Linux-Release-x64-CoreCLR_release-SLES.12.Amd64.Open

- System.IO.Pipelines.Tests.FlushAsyncTests.FlushAsync_ThrowsIfWriterReaderWithException

Error message:

The collection was expected to contain a single element, but it was empty.


Stack trace
   at System.IO.Pipelines.Tests.FlushAsyncTests.FlushAsync_ThrowsIfWriterReaderWithException() in /_/src/libraries/System.IO.Pipelines/tests/FlushAsyncTests.cs:line 52
--- End of stack trace from previous location ---

@lewing
Copy link
Member

lewing commented Jul 2, 2021 •
edited
Loading

@VincentBu that is the not a wasm lane looks like
net6.0-Linux-Release-x64-CoreCLR_release-SLES.12.Amd64.Open so perhaps there is a race, definitely not this issue though

@ghost ghost locked as resolved and limited conversation to collaborators Aug 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
arch-wasm WebAssembly architecture area-Codegen-AOT-mono disabled-test The test is disabled in source code against the issue untriaged New issue has not been triaged by the area owner wasm-aot-test WebAssembly AOT Test
Projects
None yet
Milestone
6.0.0
Development

No branches or pull requests
4 participants
@radical @lewing @VincentBu @SamMonoRT