-
Notifications
You must be signed in to change notification settings - Fork 97
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.
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
Crash in FrameBufferAllocator #2
Comments
Surprisingly, it's FrameBufferAllocatorTest, that's leaving Singleton in an invalid state... The next test in the same run crashes miserably with bus error. |
I was able to figure this problem out in fbsource, but it looks like it happens again with the GH folly. I suggest that we disable the test for now and also disable the singleton and open an issue for that. I can separately work on this later on. This should unblock us in getting the code to compile. |
Misuse of make_mock in frame serialisation tests. Details can be found on the PR. |
It has never worked for the yarpl tests, so I'm confused as to why it was enabled. Here's what I get 100% of the time when running yarpl/yarpl-tests: $ ./yarpl/yarpl-tests [==========] Running 51 tests from 7 test cases. [----------] Global test environment set-up. [----------] 17 tests from Observable [ RUN ] Observable.SingleOnNext [ OK ] Observable.SingleOnNext (98 ms) [ RUN ] Observable.MultiOnNext [ OK ] Observable.MultiOnNext (0 ms) [ RUN ] Observable.OnError [ OK ] Observable.OnError (0 ms) ASAN:DEADLYSIGNAL ================================================================= ==69355==ERROR: AddressSanitizer: SEGV on unknown address 0x61100007f740 (pc 0x000100b2c207 bp 0x7fff5f4fe260 sp 0x7fff5f4fe230 T0) #0 0x100b2c206 in testing::TestCase::GetMutableTestInfo(int) (yarpl-tests:x86_64+0x10042b206) #1 0x100b2c57e in testing::TestCase::Run() (yarpl-tests:x86_64+0x10042b57e) #2 0x100b3ab5b in testing::internal::UnitTestImpl::RunAllTests() (yarpl-tests:x86_64+0x100439b5b) #3 0x100b6a5f9 in bool testing::internal::HandleSehExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool>(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) (yarpl-tests:x86_64+0x1004695f9) #4 0x100b3a566 in bool testing::internal::HandleExceptionsInMethodIfSupported<testing::internal::UnitTestImpl, bool>(testing::internal::UnitTestImpl*, bool (testing::internal::UnitTestImpl::*)(), char const*) (yarpl-tests:x86_64+0x100439566) #5 0x100b3a417 in testing::UnitTest::Run() (yarpl-tests:x86_64+0x100439417) #6 0x10070344e in RUN_ALL_TESTS() (yarpl-tests:x86_64+0x10000244e) #7 0x10070321f in main (yarpl-tests:x86_64+0x10000221f) #8 0x7fffc67b8234 in start (libdyld.dylib:x86_64+0x5234) ==69355==Register values: rax = 0x00006110000098c0 rbx = 0x00007fff5f4fe840 rcx = 0x000000000000ebd0 rdx = 0x000000000000ebd0 rdi = 0x000061200000b000 rsi = 0x0000000000000012 rbp = 0x00007fff5f4fe260 rsp = 0x00007fff5f4fe230 r8 = 0x0000000000000000 r9 = 0x000000010298b760 r10 = 0x0000000000000000 r11 = 0x0000000000012068 r12 = 0x0000000000000000 r13 = 0x0000000000000000 r14 = 0x0000000000000000 r15 = 0x0000000000000000 AddressSanitizer can not provide additional info. SUMMARY: AddressSanitizer: SEGV (yarpl-tests:x86_64+0x10042b206) in testing::TestCase::GetMutableTestInfo(int) ==69355==ABORTING [1] 69355 abort ./yarpl/yarpl-tests
…t (attempt #2) Summary: The file descriptor API here needs to go away, so switch this API to NetworkSocket It is expected that this commit will cause a number of Open Source projects to temporarily show up as broken. This is due to the fact that not all projects get synced to Github at the exact same time, so the builds may temporarily be fetching an older version of it's dependencies than it needs to :) It should fix itself quickly. Reviewed By: yfeldblum Differential Revision: D14673328 fbshipit-source-id: c5842fa5dc383d50043e0d8228e35d03b10a1c6b
The text was updated successfully, but these errors were encountered: