[go: up one dir, main page]
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

alarm_test is flaky #12245

Closed
dgquintas opened this issue Aug 22, 2017 · 2 comments
Closed

alarm_test is flaky #12245

dgquintas opened this issue Aug 22, 2017 · 2 comments
Assignees
@yang-g
Labels
disposition/to close

Comments

@dgquintas
Copy link
Contributor

https://kokoro.corp.google.com/job/grpc/job/ubuntu/job/sanitizer/job/grpc_c_tsan/527/

I0821 20:30:27.194039199   11950 alarm_test.c:45]            test_alarm
E0821 20:30:32.241409092   11950 alarm_test.c:38]            assertion failed: ev.type == GRPC_QUEUE_SHUTDOWN



*******************************
Caught signal SIGABRT
==================
WARNING: ThreadSanitizer: signal-unsafe call inside of a signal (pid=11950)
    #0 malloc /llvm/projects/compiler-rt/lib/tsan/rtl/tsan_interceptors.cc:595 (alarm_test+0x000000442cc8)
    #1 <null> <null> (ld-linux-x86-64.so.2+0x00000000c87d)
    #2 crash_handler /var/local/git/grpc/test/core/util/test_config.c:245:13 (alarm_test+0x000000895f78)
    #3 __tsan::CallUserSignalHandler(__tsan::ThreadState*, bool, bool, bool, int, my_siginfo_t*, void*) /llvm/projects/compiler-rt/lib/tsan/rtl/tsan_interceptors.cc:1951 (alarm_test+0x000000423a46)
    #4 shutdown_and_destroy /var/local/git/grpc/test/core/surface/alarm_test.c:38:178 (alarm_test+0x0000004afc01)
    #5 test_alarm /var/local/git/grpc/test/core/surface/alarm_test.c:91:3 (alarm_test+0x0000004afae3)
    #6 main /var/local/git/grpc/test/core/surface/alarm_test.c:97:3 (alarm_test+0x0000004af5d5)

SUMMARY: ThreadSanitizer: signal-unsafe call inside of a signal (/lib64/ld-linux-x86-64.so.2+0xc87d) 
==================
Command exited with non-zero status 66
real 5.52
user 0.00
sys 0.09

Note that the TSAN stacktrace happens due to the assert firing.
@y-zeng
Copy link
Contributor
y-zeng commented Aug 29, 2017

Seen again in asan: https://grpc-testing.appspot.com/job/gRPC_pull_requests_asan_c/6660/testReport/junit/(root)/c_linux_asan_native/bins_asan_alarm_test_GRPC_POLL_STRATEGY_poll_cv/

@yashykt yashykt mentioned this issue Sep 7, 2017
Merged
@dgquintas dgquintas changed the title alarm_test is flaky under tsan alarm_test is flaky Sep 15, 2017
@dgquintas
Copy link
Contributor Author

again: https://grpc-testing.appspot.com/job/gRPC_pull_requests_asan_c/7121/testReport/junit/(root)/c_linux_asan_native/bins_asan_alarm_test_GRPC_POLL_STRATEGY_poll/

D0915 05:20:24.436923691   16507 test_config.c:388]          test slowdown factor: sanitizer=3, fixture=1, poller=1, total=3
D0915 05:20:24.437686023   16507 ev_posix.c:107]             Using polling engine: poll
D0915 05:20:24.437810595   16507 dns_resolver.c:301]         Using native dns resolver
I0915 05:20:24.438050041   16507 alarm_test.c:45]            test_alarm
E0915 05:20:27.449407283   16507 alarm_test.c:38]            assertion failed: ev.type == GRPC_QUEUE_SHUTDOWN

@dgquintas dgquintas mentioned this issue Sep 15, 2017
Merged
This was referenced Sep 18, 2017
Merged
Merged
This was referenced Sep 22, 2017
Merged
Merged
This was referenced Sep 26, 2017
Merged
Merged
@yang-g yang-g mentioned this issue Sep 28, 2017
Merged
@markdroth markdroth mentioned this issue Sep 29, 2017
Merged
@ctiller ctiller closed this as completed Dec 11, 2017
@lock lock bot locked as resolved and limited conversation to collaborators Sep 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@yang-g yang-g

Labels
disposition/to close
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@dgquintas @ctiller @yang-g @y-zeng