> Martin Sebor wrote: > >Have you guys compared the environment from the nightly builds >with yours to see if there are any interesting differences? >Travis, it might be worthwhile to try to set yours up to match >and re-running the build on one of the build servers.
Yeah, I'm already pulling a build now. I'll let you know what I find. > >If that doesn't reveal anything, would instrumenting exec and/or >one of the failing tests to produce some useful output in the next >nightly build on Windows help solve this mystery? > >Martin > >Farid Zaripov wrote: > >> From: Travis Vitek [mailto:[EMAIL PROTECTED] >> To: [email protected] >> Subject: RE: Exit code 3 on MSVC and ICC/Windows >> >>> Yes, but unfortunately I can't reproduce most of those exit >>> 3 failures locally. Here are a list of programs that fail >>> with code 3 in nightly builds... >> >>> 22.locale.codecvt.length >>> 22.locale.codecvt.out >>> 22.locale.ctype.is >>> 22.locale.ctype.scan >>> 22.locale.ctype.tolower >>> 22.locale.ctype.toupper >>> 22.locale.ctype >>> 22.locale.moneypunct.mt >>> 22.locale.time.get.mt >>> 22.locale.time.get >>> 22.locale.time.put >> >
