Skip to content

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

Closed
Closed
[wasm][tests][aot] System.IO.Pipelines.Tests - failing tests#50959
Labels
arch-wasmWebAssembly architecturearea-Codegen-AOT-monodisabled-testThe test is disabled in source code against the issueuntriagedNew issue has not been triaged by the area ownerwasm-aot-testWebAssembly AOT Test
Milestone
6.0.0

Description

@radical
radical
opened on Apr 8, 2021

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

Activity

  1. radical
    added
    arch-wasmWebAssembly architecture
    area-Codegen-AOT-mono
    wasm-aot-testWebAssembly AOT Test
    on Apr 8, 2021
  3. ghost added
    untriagedNew issue has not been triaged by the area owner
    on Apr 8, 2021
  4. SamMonoRT
    added this to the 6.0.0 milestone on Apr 9, 2021
  5. radical
    added
    disabled-testThe test is disabled in source code against the issue
    on Apr 23, 2021

  6. radical commented on May 6, 2021

    @radical
    radical
    on May 6, 2021
    MemberAuthor

    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
  7. radical
    changed the title [-][wasm][tests][aot] System.IO.Pipelines.Tests failures[/-] [+][wasm][tests][aot] System.IO.Pipelines.Tests - timing out[/+] on May 6, 2021
  8. radical
    added a commit that references this issue on May 6, 2021

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

    6d81589
  9. lewing
    added a commit that references this issue on May 7, 2021

    [wasm][aot] Update disabled tests to track new fixes on `main` (#52396)

    d36313d

  10. radical commented on Jun 10, 2021

    @radical
    radical
    on Jun 10, 2021
    MemberAuthor

    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 ---
  11. radical
    changed the title [-][wasm][tests][aot] System.IO.Pipelines.Tests - timing out[/-] [+][wasm][tests][aot] System.IO.Pipelines.Tests - failing tests[/+] on Jun 10, 2021
  12. radical
    added
    blocking-aot-tracking-pr
    on Jun 15, 2021

  13. lewing commented on Jun 15, 2021

    @lewing
    lewing
    on Jun 15, 2021
    Member

    These are all AOT stack trace issues

  14. radical commented on Jun 16, 2021

    @radical
    radical
    on Jun 16, 2021
    MemberAuthor

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

  15. radical
    closed this as completedon Jun 16, 2021

  16. VincentBu commented on Jul 2, 2021

    @VincentBu
    VincentBu
    on Jul 2, 2021
    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 ---

  17. lewing commented on Jul 2, 2021

    @lewing
    lewing
    on Jul 2, 2021
    Member

    @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

  18. ghost locked as resolved and limited conversation to collaborators on Aug 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    arch-wasmWebAssembly architecturearea-Codegen-AOT-monodisabled-testThe test is disabled in source code against the issueuntriagedNew issue has not been triaged by the area ownerwasm-aot-testWebAssembly AOT Test

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions