[Swift-devel] swift builds on my machiens but not at nmi build&test, with dependency problems
Mihael Hategan
hategan at mcs.anl.gov
Mon Oct 13 23:13:41 CDT 2008
I made a commit today that should have fixed it.
It was my attempt at automatically building coasters, which caused a
circular dependency. It may work if you have a previous build.
On Tue, 2008-10-14 at 04:02 +0000, Ben Clifford wrote:
> When I run a build either on my laptop or communicado (my usual build
> directory on my laptop, two separate fresh checkouts on communicado) I can
> build ok.
>
> When the nmi b&t machines run builds they have been failing since cog r
>
> One example failure is here:
> http://nmi-s005.cs.wisc.edu:80/nmi/index.php?page=results/runDetails&runid=109313&opt_project=swift
>
> The output of my build is in
> http://www.ci.uchicago.edu/~benc/tmp/depfail-benc.out
>
> The output of the nmi build (in addition to being linked from the above
> nmi-s005 link) is in
> http://www.ci.uchicago.edu/~benc/tmp/depfail-nmi.out
>
> A diff of those two is in
> http://www.ci.uchicago.edu/~benc/tmp/depfail.diff
>
> So it looks like in the nmi case, coasters are getting built before
> karajan is attempted (or perhaps karajan is not attempted at all). In my
> case, karajan is built first.
>
> Not sure what is causing that.
>
More information about the Swift-devel
mailing list