On 04/29/2015 05:23 PM, Andrew Johnson wrote:
> Oh, and with this new version of Cygwin:
>
>> src/libCom/test/O.cygwin-x86_64/blockingSockTest.tap .........
>> Failed 1/13 subtests
>
> That failure being:
>
> # This OS behaves like "esscimqi_socketBothShutdownRequired".
> not ok 13 - Declared mechanism works
> # epicsSocketSystemCallInterruptMechanismQuery returned
> "esscimqi_socketCloseRequired"
>
> So Cygwin has changed its socket shutdown behaviour again...
Wrong, the major version number changed from 1007 to 2000 and the #if
test that we had in libCom/osi/os/cygwin32/systemCallIntMech.cpp to fix
the time when it did change was wrong. In 3.14 we have #if 0 instead,
which is why the test passed. If we're lucky this commit might also fix
the hangup.
- Andrew
--
Light thinks it travels faster than anything but it is wrong.
No matter how fast light travels, it finds the darkness has
always got there first, and is waiting for it.
-- Terry Pratchett, Reaper Man
- References:
- Build failed in Jenkins: epics-base-3.15-cyg64 #198 APS Jenkins
- Build failed in Jenkins: epics-base-3.15-cyg64 #199 APS Jenkins
- Re: Build failed in Jenkins: epics-base-3.15-cyg64 #199 Andrew Johnson
- Navigate by Date:
- Prev:
Re: Cygnus support Michael Davidsaver
- Next:
Jenkins build is still unstable: epics-base-3.15-win64s #158 APS Jenkins
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
<2015>
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: Build failed in Jenkins: epics-base-3.15-cyg64 #199 Andrew Johnson
- Next:
Jenkins build is back to normal : epics-base-3.15-cyg64 #200 APS Jenkins
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
<2015>
2016
2017
2018
2019
2020
2021
2022
2023
2024
|