[
https://issues.apache.org/jira/browse/PROTON-1805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16413980#comment-16413980
]
Andrew Stitcher commented on PROTON-1805:
-----------------------------------------
[~rkieley] I think your testing environment must be significantly different
from the CI environments this fails in:
For one thing by default the proactor fuzz tests will not be built or run
unless the FUZZ_LONG_TESTS option is set and it is off by default. If you
turned it on in your build - don't do that!
So if you build from scratch with a clean build space for shouldn't see these
warnings - so this makes me think you must be doing something else.
However I'm intrigued that your environment which is like (but seemingly not
identical) with one of the build environments does not segv.
> [MacOS] Fuzzer issues in fuzz-connection-driver & fuzz-message-decode
> ---------------------------------------------------------------------
>
> Key: PROTON-1805
> URL: https://issues.apache.org/jira/browse/PROTON-1805
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Reporter: Andrew Stitcher
> Priority: Major
> Labels: fuzzer, mac-os-x, osx
>
> Introducing the fuzz tester has shown up a couple of segvs in the MacOS port.
> for fuzz-connection-driver:
> {noformat}
> 26: Running:
> /Users/travis/build/astitcher/qpid-proton/proton-c/src/tests/fuzz/fuzz-connection-driver/corpus/7e51d07e16f84d001a8be4a1dedf556b3b16720c
> 26/34 Test #26: fuzz-connection-driver ...........***Exception: SegFault
> 1.76 sec{noformat}
> and for fuzz-message-decode:
> {noformat}
> 27: Running:
> /Users/travis/build/astitcher/qpid-proton/proton-c/src/tests/fuzz/fuzz-message-decode/corpus/d5143aaeea6897d4264440017cd47ebc874f4440
> 27/34 Test #27: fuzz-message-decode ..............***Exception: SegFault
> 1.97 sec{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
