You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stdcxx.apache.org by Martin Sebor <se...@roguewave.com> on 2008/02/06 17:00:50 UTC
MSVC 8 build failures on Vista/EM64T
Looks like we're having all kinds of trouble here:
http://people.apache.org/~sebor/stdcxx/results/win_vista_0-em64t-msvc-8.0.html
The builds are over two weeks old and all failing with the same
error:
### Building solution / Creating HTML log
Building 12d Optimized Thread-safe Dll...
Solution build script
Checking arguments...
Loading solution...
Build:
Closing the VisualStudio...
d:\bman5\builds\34438072\source-buildspace\etc\config\windows\build.wsf(515,
6) (null): Call was rejected by callee.
Summary log was generated in
file://D:/bman5/builds/34438072/source-buildspace/build/msvc-8.0-12d.html
Build complete
Martin
Re: MSVC 8 build failures on Vista/EM64T
Posted by Andrew Black <ab...@roguewave.com>.
Martin Sebor wrote:
> Farid Zaripov wrote:
[snip]
>> But anyway maybe it makes sense to schedule the builds on the same
>> machine to not run at the same time?
The scheduling system doesn't allow for the concept of mutually
exclusive requests/runs, meaning only one build of X can be running at a
given time.
>
> Most of our machines are set up to run N or N + 1 builds in parallel
> (where N is the number of CPUs). We might be able to throttle one
> down now but eventually it'll get cranked up again otherwise we
> wouldn't get the kind of throughput we need. Se we might as well
> figure out what's causing it now. If you can't reproduce it maybe
> it's an installation problem again.
>
> Btw., another interesting thing to note is that the links to the
> same build logs on the result page are unavailable:
> http://people.apache.org/~sebor/stdcxx/results/
>
> Andrew, any idea if that's relevant and what it might mean?
Looking at the date of the runs (nearly a month old), I think what
happened is the build log attachment aged out of the backend database,
so the exporter script didn't generate a link to them - even if they
might exist on disk at Apache. Given the backlog of requests on the
operating system, I suspect the workers may have glitched, so I'll be
taking a look at them.
>
> Martin
Re: MSVC 8 build failures on Vista/EM64T
Posted by Martin Sebor <se...@roguewave.com>.
Farid Zaripov wrote:
>> -----Original Message-----
>> From: Martin Sebor [mailto:sebor@roguewave.com]
>> Sent: Friday, February 08, 2008 12:45 AM
>> To: dev@stdcxx.apache.org
>> Subject: Re: MSVC 8 build failures on Vista/EM64T
>>
>> Travis, can you reproduce this in your environment? If not,
>> does it look similar to the problem we ran into late last
>> year that we finally fixed by getting the compiler reinstalled?
>
> I see that all Vista/EMP64T builds are runs on the same machine
> HOPPER, and it seems that 12D config is built in parallel to the
> 12d config (here http://people.apache.org/~sebor/stdcxx/results/
> specified the same time 01-14 21:58). The 15S config is build
> some later (01-14 22:12) and succeeded 15s config is built at
> 01-14 22:23.
>
> I've tried to reproduce the problem by running the 12d and 12D builds
> in parallel, but I've no problems detected.
>
> But anyway maybe it makes sense to schedule the builds on the same
> machine to not run at the same time?
Most of our machines are set up to run N or N + 1 builds in parallel
(where N is the number of CPUs). We might be able to throttle one
down now but eventually it'll get cranked up again otherwise we
wouldn't get the kind of throughput we need. Se we might as well
figure out what's causing it now. If you can't reproduce it maybe
it's an installation problem again.
Btw., another interesting thing to note is that the links to the
same build logs on the result page are unavailable:
http://people.apache.org/~sebor/stdcxx/results/
Andrew, any idea if that's relevant and what it might mean?
Martin
RE: MSVC 8 build failures on Vista/EM64T
Posted by Farid Zaripov <Fa...@epam.com>.
> -----Original Message-----
> From: Martin Sebor [mailto:sebor@roguewave.com]
> Sent: Friday, February 08, 2008 12:45 AM
> To: dev@stdcxx.apache.org
> Subject: Re: MSVC 8 build failures on Vista/EM64T
>
> Travis, can you reproduce this in your environment? If not,
> does it look similar to the problem we ran into late last
> year that we finally fixed by getting the compiler reinstalled?
I see that all Vista/EMP64T builds are runs on the same machine
HOPPER, and it seems that 12D config is built in parallel to the
12d config (here http://people.apache.org/~sebor/stdcxx/results/
specified the same time 01-14 21:58). The 15S config is build
some later (01-14 22:12) and succeeded 15s config is built at
01-14 22:23.
I've tried to reproduce the problem by running the 12d and 12D builds
in parallel, but I've no problems detected.
But anyway maybe it makes sense to schedule the builds on the same
machine to not run at the same time?
Farid.
Re: MSVC 8 build failures on Vista/EM64T
Posted by Martin Sebor <se...@roguewave.com>.
Travis, can you reproduce this in your environment? If not, does
it look similar to the problem we ran into late last year that we
finally fixed by getting the compiler reinstalled?
Martin
Martin Sebor wrote:
> Looks like we're having all kinds of trouble here:
> http://people.apache.org/~sebor/stdcxx/results/win_vista_0-em64t-msvc-8.0.html
>
>
> The builds are over two weeks old and all failing with the same
> error:
>
> ### Building solution / Creating HTML log
> Building 12d Optimized Thread-safe Dll...
> Solution build script
> Checking arguments...
> Loading solution...
> Build:
> Closing the VisualStudio...
> d:\bman5\builds\34438072\source-buildspace\etc\config\windows\build.wsf(515,
> 6) (null): Call was rejected by callee.
>
> Summary log was generated in
> file://D:/bman5/builds/34438072/source-buildspace/build/msvc-8.0-12d.html
> Build complete
>
> Martin