[
https://issues.apache.org/jira/browse/PROTON-2508?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497787#comment-17497787
]
Andrew Stitcher commented on PROTON-2508:
-----------------------------------------
The compiler bug doesn't seem to happen using Debug or MinSizeRel build
configuration so these can be used as workarounds to the bug.
We should set up our VS2017 CI instances to use one of these flags for as long
as we support this compiler.
We should also disable the python tox test as it will use this compiler with
the Release build setting when it compiles the python extension.
This will also means that we can't support the python extension on any windows
machine that will install the extension using the VS2017 compiler.
> Visual Studio 2017 seems to optimise proton-core library wrongly
> ----------------------------------------------------------------
>
> Key: PROTON-2508
> URL: https://issues.apache.org/jira/browse/PROTON-2508
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: proton-c-0.36.0, proton-c-0.37.0
> Environment: Windows; Visual Studio 2017 with RelWithDebInfo, Release
> build configurations
> Reporter: Andrew Stitcher
> Assignee: Andrew Stitcher
> Priority: Major
>
> It appears that if you build proton with VS2017 in the RelWithDebInfo or
> Release configure then a number of the tests fail specifically the
> cpp-container_test fails and also hangs.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
