Skip to content
This repository was archived by the owner on Dec 18, 2018. It is now read-only.

Test failure #8

Closed
davidfowl opened this issue Jun 28, 2014 · 11 comments
Closed

Test failure #8

davidfowl opened this issue Jun 28, 2014 · 11 comments
Assignees
Labels
Milestone

Comments

@davidfowl
Copy link
Member

count 10 ABCDEABCDE
   Microsoft.AspNet.Server.KestralTests.EngineTests.Http10 [FAIL]
count 0 
      Assert.Equal() Failure\n          ↓ (pos 0)\nExpected: HTTP/1.0 200 OK\r\n\r\nHello World\nActual:   \n          ↑ (pos 0)
      Stack Trace:
           at Microsoft.AspNet.Server.KestralTests.TestConnection+<Receive>d__1.MoveNext () [0x00000] in <filename unknown>:0 
         --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0 
           at System.Runtime.CompilerServices.TaskAwaiter.GetResult () [0x00000] in <filename unknown>:0 
           at Microsoft.AspNet.Server.KestralTests.TestConnection+<ReceiveEnd>d__1.MoveNext () [0x00000] in <filename unknown>:0 
         --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0 
           at System.Runtime.CompilerServices.TaskAwaiter.GetResult () [0x00000] in <filename unknown>:0 
           at Microsoft.AspNet.Server.KestralTests.EngineTests+<Http10>d__1.MoveNext () [0x00000] in <filename unknown>:0 
         --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0 
           at System.Runtime.CompilerServices.TaskAwaiter.GetResult () [0x00000] in <filename unknown>:0 
         --- End of stack trace from previous location where exception was thrown ---
           at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw () [0x00000] in <filename unknown>:0 
           at System.Runtime.CompilerServices.TaskAwaiter.GetResult () [0x00000] in <filename unknown>:0 
Started
Finished: Microsoft.AspNet.Server.KestralTests, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null

=== TEST EXECUTION SUMMARY ===
   Microsoft.AspNet.Server.KestralTests, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null  Total: 24, Failed: 1, Skipped: 0, Time: 4.196s
warn: Exit code 1 from k
@davidfowl davidfowl changed the title Test failure on mono Test failure Jun 28, 2014
@davidfowl davidfowl added the bug label Jun 29, 2014
@davidfowl
Copy link
Member Author

This is blocking the CI so I'm going to disable it temporarily.

@davidfowl davidfowl added this to the 0.1-alpha3 milestone Jun 29, 2014
@davidfowl
Copy link
Member Author

This failure isn't consistent. It fails and passes randomly, here's another one:

   Microsoft.AspNet.Server.KestralTests.EngineTests.Http11 [FAIL]
      System.IO.IOException : Unable to write data to the transport connection: An established connection was aborted by
 the software in your host machine.\r\n---- System.Net.Sockets.SocketException : An established connection was aborted b
y the software iStarted
n your host machine
      Stack Trace:
            at System.Net.Sockets.NetworkStream.BeginWrite(Byte[] buffer, Int32 offset, Int32 size, AsyncCallback callba
ck, Object state)
            at System.IO.Stream.<BeginEndWriteAsync>b__16(Stream stream, ReadWriteParameters args, AsyncCallback callbac
k, Object state)
            at System.Threading.Tasks.TaskFactory`1.FromAsyncTrim[TInstance,TArgs](TInstance thisRef, TArgs args, Func`5
 beginMethod, Func`3 endMethod)
            at System.IO.Stream.BeginEndWriteAsync(Byte[] buffer, Int32 offset, Int32 count)
            at System.IO.Stream.WriteAsync(Byte[] buffer, Int32 offset, Int32 count, CancellationToken cancellationToken
)
            at System.IO.Stream.WriteAsync(Byte[] buffer, Int32 offset, Int32 count)
            at System.IO.StreamWriter.<FlushAsyncInternal>d__1e.MoveNext()
         --- End of stack trace from previous location where exception was thrown ---
            at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
            at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
            at Microsoft.AspNet.Server.KestralTests.TestConnection.<Send>d__1.MoveNext() in C:\dev\git\ProjectK\KestrelH
ttpServer\test\Microsoft.AspNet.Server.KestralTests\TestConnection.cs:line 48
         --- End of stack trace from previous location where exception was thrown ---
            at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
            at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
            at Microsoft.AspNet.Server.KestralTests.TestConnection.<SendEnd>d__1.MoveNext() in C:\dev\git\ProjectK\Kestr
elHttpServer\test\Microsoft.AspNet.Server.KestralTests\TestConnection.cs:line 57
         --- End of stack trace from previous location where exception was thrown ---
            at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
            at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
            at Microsoft.AspNet.Server.KestralTests.EngineTests.<Http11>d__1.MoveNext() in C:\dev\git\ProjectK\KestrelHt
tpServer\test\Microsoft.AspNet.Server.KestralTests\EngineTests.cs:line 143
         --- End of stack trace from previous location where exception was thrown ---
            at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         --- End of stack trace from previous location where exception was thrown ---
            at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
            at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
         ----- Inner Stack Trace -----
            at System.Net.Sockets.Socket.BeginSend(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags, Asy
ncCallback callback, Object state)
            at System.Net.Sockets.NetworkStream.BeginWrite(Byte[] buffer, Int32 offset, Int32 size, AsyncCallback callba
ck, Object state)
Finished: Microsoft.AspNet.Server.KestralTests, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null

=== TEST EXECUTION SUMMARY ===
   Microsoft.AspNet.Server.KestralTests, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null  Total: 23, Failed: 1, Sk
ipped: 0, Time: 8.876s

@davidfowl
Copy link
Member Author

And another:

   Microsoft.AspNet.Server.KestralTests.EngineTests.Expect100ContinueForBody [FAIL]
      Assert.Equal() Failure\r\n          ↓ (pos 0)\r\nExpected: HTTP/1.1 100 Continue\r\n\r\n\r\nActual:   ABCDEABCDEAB
CDEABCDEABCDE\r\n          ↑ (pos 0)

@davidfowl
Copy link
Member Author

@davidfowl davidfowl modified the milestones: 1.0.0-alpha3, 1.0.0-alpha4 Aug 17, 2014
@Eilon Eilon modified the milestones: 1.0.0-alpha4, 1.0.0-rc1 Oct 6, 2015
@Eilon
Copy link
Contributor

Eilon commented Oct 6, 2015

This is a super old bug but it was in the alpha4 milestone, so moving to RC1 to reevaluate.

@muratg muratg modified the milestones: 1.0.0-rc2, 1.0.0-rc1 Oct 26, 2015
@muratg
Copy link
Contributor

muratg commented Oct 26, 2015

Just talked to @lodejard. Moving is issues to RC2.

@lodejard lodejard assigned halter73 and unassigned lodejard Nov 24, 2015
@lodejard
Copy link
Contributor

Reassigning to @halter73 for investigation or closing if needed

@halter73
Copy link
Member

halter73 commented Dec 3, 2015

I've been running these tests a lot the last couple days on various platforms, and I haven't seen this issue. In fact, I haven't seen any of the EngineTests fail with an Assert.Equal failure or an IOException in well over a month.

The EngineTests hanging on Mono are another story of course...

@muratg
Copy link
Contributor

muratg commented Dec 3, 2015

We'll reactivate if this is still an issue.

@muratg muratg reopened this Dec 3, 2015
@halter73
Copy link
Member

halter73 commented Dec 3, 2015

@muratg Do you want me to continue investigating this? Should I remove the Done label?

@muratg muratg removed the 3 - Done label Dec 3, 2015
@muratg muratg modified the milestones: 1.0.0 backlog, 1.0.0-rc2 Dec 3, 2015
@muratg
Copy link
Contributor

muratg commented Dec 3, 2015

I had an exception a couple days ago but later passed fine, though I'm not sure if it works fine now or not. Keeping open for now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants