Failing Tests

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Failing Tests

Neale Ferguson
Running the tests on my s390x 5.8 build show numerous failures with messages like below. The confusing bit is that isn’t SIG37 used by GC? There also errors relating to SIG36 being received (which is also GC related).

threadpool-exceptions2.exe

=============== threadpool-exceptions2.exe.stdout ===============


"Finalizer" tid=0x0x3ff8767b910 this=0x0x3ff876ec278 , thread handle : 0x3ff800010b0, state : not waiting


[New LWP 52103]

[New LWP 52101]

[New LWP 52100]

[New LWP 52099]

[New LWP 52098]

[Thread debugging using libthread_db enabled]

Using host libthread_db library "/lib64/libthread_db.so.1".

0x000003ff8df0c222 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0

  Id   Target Id         Frame 

  6    Thread 0x3ff86fff910 (LWP 52098) "SGen worker" 0x000003ff8df0c222 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0

  5    Thread 0x3ff8767b910 (LWP 52099) "Finalizer" 0x000003ff8df092ac in pthread_join () from /lib64/libpthread.so.0

  4    Thread 0x3ff853ff910 (LWP 52100) "mono" 0x000003ff8df0c222 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0

  3    Thread 0x3ff851ff910 (LWP 52101) "Threadpool work" 0x000003ff8df0e70c in do_futex_wait () from /lib64/libpthread.so.0

  2    Thread 0x3ff84dff910 (LWP 52103) "Threadpool work" 0x000003ff8df0ec4e in sem_post@@GLIBC_2.2 () from /lib64/libpthread.so.0

* 1    Thread 0x3ff8e277740 (LWP 52087) "mono" 0x000003ff8df0c222 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0


Thread 6 (Thread 0x3ff86fff910 (LWP 52098)):

$1 = void


Thread 5 (Thread 0x3ff8767b910 (LWP 52099)):


Program received signal SIG37, Real-time event 37.

[Switching to Thread 0x3ff84dff910 (LWP 52103)]

0x000003ff8df0f376 in __lll_lock_wait () from /lib64/libpthread.so.0


I am also seeing this error repeated (also preceded by the SIG37 message):


you are registering the same counter address twice: Discarded method code at 0x140d2a8

you are registering the same counter address twice: Time spent JITting discarded code at 0x140d2a0

you are registering the same counter address twice: Dynamic code allocs at 0x145f9d8

you are registering the same counter address twice: Dynamic code bytes at 0x145f9d0

you are registering the same counter address twice: Dynamic code frees at 0x145f9c8

you are registering the same counter address twice: Unwind info size at 0x140c190

you are registering the same counter address twice: Calls to trampolines at 0x140bf6c

you are registering the same counter address twice: JIT trampolines at 0x140bf68

you are registering the same counter address twice: Unbox trampolines at 0x140bf64

you are registering the same counter address twice: Static rgctx trampolines at 0x140bf60

you are registering the same counter address twice: RGCTX unmanaged lookups at 0x140bf5c

you are registering the same counter address twice: RGCTX num lazy fetch trampolines at 0x140bf58

you are registering the same counter address twice: Async JIT info size at 0x140bd60

* Assertion: should not be reached at domain.c:474


_______________________________________________
Mono-devel-list mailing list
[hidden email]
http://lists.dot.net/mailman/listinfo/mono-devel-list