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.

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

[SR-5067] TestNSDecimal.test_Maths - build-script-impl: line 260: 17061 Segmentation fault "$@" #47643

Closed
benlangmuir opened this issue Jun 1, 2017 · 10 comments
Assignees
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior.

Comments

@benlangmuir
Copy link
Member

Previous ID SR-5067
Radar rdar://problem/32513582
Original Reporter @benlangmuir
Type Bug
Status Resolved
Resolution Done
Additional Detail from JIRA
Votes 0
Component/s
Labels Bug
Assignee @benlangmuir
Priority Medium

md5: 38f36721ebe2f30826f5e1692897db9a

Issue Description:

https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-16_10/3998/console#console-section-6

Happened a few times recently, but not every build.

/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-16_10/swift/utils/build-script-impl: line 260: 17061 Segmentation fault      "$@"
/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-16_10/swift/utils/build-script: fatal error: command terminated with a non-zero exit status 139, aborting
/home/buildnode/jenkins/workspace/oss-swift-incremental-RA-linux-ubuntu-16_10/swift/utils/build-script: fatal error: command terminated with a non-zero exit status 1, aborting
Build step 'Execute shell' marked build as failure

#​0  __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:159
#​1  0x00007ffff583cda6 in __atomic_load () from /usr/lib/x86_64-linux-gnu/libatomic.so.1
#&#8203;2  0x00007ffff7c56716 in swift::RefCounts<swift::RefCountBitsT<(swift::RefCountInlinedness)1> >::incrementSlow(swift::RefCountBitsT<(swift::RefCountInlinedness)1>, unsigned int) () from swift/linux/libswiftCore.so
#&#8203;3  0x00000000006ab87e in _T0s9CharacterV14RepresentationOWy ()
#&#8203;4  0x00000000006cb157 in _T014TestFoundation0A9NSDecimalC10test_MathsyyF ()
#&#8203;5  0x00000000006f3228 in _T0TA.2439 ()
#&#8203;6  0x000000000044ac86 in _T0s5Error_pIxzo_ytytsAA_pIxirzo_TR ()
#&#8203;7  0x00000000006f349b in _T0s5Error_pIxzo_ytytsAA_pIxirzo_TRTA ()
#&#8203;8  0x00007ffff7f5b4ff in _T0ytyts5Error_pIxirzo_sAA_pIxzo_TRTA () from Foundation/libXCTest.so
#&#8203;9  0x00007ffff7f505c2 in _T06XCTest4test33_3BE257A46ADB477C7BF2D39968B39F9DLLyAA0A4CaseCKcyyKcxcAERbzlFyAEKcfU_Tf4gg_n () from Foundation/libXCTest.so
#&#8203;10 0x00007ffff7f5b21f in _T06XCTest4test33_3BE257A46ADB477C7BF2D39968B39F9DLLyAA0A4CaseCKcyyKcxcAERbzlFyAEKcfU_TA () from Foundation/libXCTest.so
#&#8203;11 0x00007ffff7f5b17b in _T06XCTest0A4CaseCs5Error_pIxxzo_ACytsAD_pIxirzo_TRTA () from Foundation/libXCTest.so
#&#8203;12 0x00007ffff7f5bfe9 in _T06XCTest0A4CaseCs5Error_pIxxzo_ACytsAD_pIxirzo_TRTA.182 () from Foundation/libXCTest.so
#&#8203;13 0x00007ffff7f5a780 in _T06XCTest0A4CaseCyts5Error_pIxirzo_ACsAD_pIxxzo_TRTA () from Foundation/libXCTest.so
#&#8203;14 0x00007ffff7f357b6 in _T06XCTest0A4CaseC10invokeTestyyF () from Foundation/libXCTest.so
#&#8203;15 0x00007ffff7f4db92 in _T06XCTest0A4CaseC7performyAA0A3RunCFTf4gn_n () from Foundation/libXCTest.so
#&#8203;16 0x00007ffff7f3569e in _T06XCTest0A4CaseC7performyAA0A3RunCF () from Foundation/libXCTest.so
#&#8203;17 0x00007ffff7f31c85 in _T06XCTestAAC3runyyF () from Foundation/libXCTest.so
#&#8203;18 0x00007ffff7f4e29c in _T06XCTest0A5SuiteC7performyAA0A3RunCFTf4gn_n () from Foundation/libXCTest.so
#&#8203;19 0x00007ffff7f4e512 in _T06XCTest0A5SuiteC7performyAA0A3RunCFTf4gn_n () from Foundation/libXCTest.so
#&#8203;20 0x00007ffff7f38a59 in _T06XCTest7XCTMains5NeverOSayAA0A4CaseCm04testD5Class_SaySS_yAFKctG8allTeststGF () from Foundation/libXCTest.so
#&#8203;21 0x00000000004398c5 in main ()
@parkera
Copy link
Member

parkera commented Jun 1, 2017

Is it possible to get a crash log out of the CI system so we can see a backtrace?

@benlangmuir
Copy link
Member Author

CC @shahmishal

@parkera
Copy link
Member

parkera commented Jun 1, 2017

Is this a recent regression? Do you have any historical info on when it started failing?

@benlangmuir
Copy link
Member Author

The first failure I see is https://ci.swift.org/job/oss-swift-incremental-RA-linux-ubuntu-16_10/3997/

But it hasn't failed every time since then.

@parkera
Copy link
Member

parkera commented Jun 1, 2017

No SCL-foundation changes there...

@benlangmuir
Copy link
Member Author

See description for backtrace.

@benlangmuir
Copy link
Member Author

I'm going to disable this test on Linux for now: #10039

@parkera
Copy link
Member

parkera commented Jun 1, 2017

It looks like this should go to the Swift runtime.

@benlangmuir
Copy link
Member Author

Dave tells me that the representation of Character changed very recently in the stdlib, and that we don't have the correct dependencies in our build system where the stdlib is concerned. That would also be consistent with the fact that we're only seeing this on one machine so far, although I'm a bit surprised it wouldn't be more deterministic.

I'm going to try cleaning our CI workspace to see if that resolves the issue.

@benlangmuir
Copy link
Member Author

Okay, after the clean we've had 3 successful runs in a row. I'm tentatively closing this, but will keep an eye on it.

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A deviation from expected or documented behavior. Also: expected but undesirable behavior.
Projects
None yet
Development

No branches or pull requests

2 participants