-
Notifications
You must be signed in to change notification settings - Fork 5.2k
Closed
Labels
area-System.Threadingtest-bugProblem in test source code (most likely)Problem in test source code (most likely)
Milestone
Description
Saw this on this job.
MESSAGE:
Return code: 1
Raw output file: D:\j\workspace\x64_release_w---0575cb46\bin\tests\Windows_NT.x64.Releaseeports\baseservices\threading\mutex\misc\waitone2\waitone2.output.txt
Raw output:
BEGIN EXECUTION
"D:\j\workspace\x64_release_w---0575cb46\tests\..\bin\tests\Windows_NT.x64.Release\Tests\Core_Root\corerun.exe" waitone2.exe
Beginning test case MutexWaitOne2 at 7/21/2016 9:07:52 AM
Random seed: 20010415; set environment variable CORECLR_SEED to this value to repro
[Positive]
Beginning scenario: PosTest1: Wait Infinite
Beginning scenario: PosTest2: Wait some finite time
ERROR!!!-003: Unexpected exception: System.Exception: Object synchronization method was called from an unsynchronized block of code.
at System.Threading.Mutex.ReleaseMutex()
at MutexWaitOne2.PosTest2() in D:\j\workspace\x64_release_w---0575cb46\tests\src\baseservices\threading\mutex\misc\WaitOne2.cs:line 127
at System.Threading.Mutex.ReleaseMutex()
at MutexWaitOne2.PosTest2() in D:\j\workspace\x64_release_w---0575cb46\tests\src\baseservices\threading\mutex\misc\WaitOne2.cs:line 127
Beginning scenario: PosTest3: Wait some finite time will quit for timeout
Beginning scenario: PosTest4: Wait some finite time will quit for timeout when another thread is in nondefault managed context
Beginning scenario: PosTest5: Wait some finite time will quit for timeout when another thread is in nondefault managed context
Beginning scenario: PosTest6: Wait infinite time when another thread is in nondefault managed context
Beginning scenario: PosTest7: Wait infinite time when another thread is in nondefault managed context
[Negative]
Beginning scenario: NegTest1: AbandonedMutexException should be thrown if a thread exited without releasing a mutex
Beginning scenario: NegTest2: ObjectDisposedException should be thrown if current instance has already been disposed
Beginning scenario: NegTest3: Check ArgumentOutOfRangeException will be thrown if millisecondsTimeout is a negative number other than -1
Ending test case at 7/21/2016 9:08:25 AM
FAIL
Expected: 100
Actual: 0
END EXECUTION - FAILED
FAILED
Test Harness Exitcode is : 1
To run the test:
> set CORE_ROOT=D:\j\workspace\x64_release_w---0575cb46\bin\tests\Windows_NT.x64.Release\Tests\Core_Root
> D:\j\workspace\x64_release_w---0575cb46\bin\tests\Windows_NT.x64.Release\baseservices\threading\mutex\misc\waitone2\waitone2.cmd
Expected: True
Actual: False
+++++++++++++++++++
STACK TRACE:
at baseservices._threading_mutex_misc_waitone2_waitone2_._threading_mutex_misc_waitone2_waitone2_cmd() in D:\j\workspace\x64_release_w---0575cb46\bin\tests\Windows_NT.x64.Release\TestWrappers\baseservices\baseservices.XUnitWrapper.cs:line 27222
Metadata
Metadata
Assignees
Labels
area-System.Threadingtest-bugProblem in test source code (most likely)Problem in test source code (most likely)