On 2019/10/30 23:11, Rafael Sadowski wrote:
> On Mon Oct 28, 2019 at 09:11:46PM +0000, Stuart Henderson wrote:
> > On 2019/10/27 17:04, Stuart Henderson wrote:
> > > On 2019/10/25 17:27, Stuart Henderson wrote:
> > > > > It is possible for you to go into the build directory and run
> > > > > "ninja -d explain"?
> > > > > Maybe the output can help me to find the issue.
> > > >
> > > > I'll try to get that next time it happens. I can't keep all the failed
> > > > build work directories from my bulks because I have failures, often in
> > > > big ports, in nearly every bulk build (I do approx 20 per month)..
> > >
> > > Rerunning with "ninja -d explain" the build completes without an error,
> > > so this doesn't help.
> > >
> > > I've now set -d explain in cmake.port.mk and will have to hope it doesn't
> > > result in ridiculously large logs in some of the bigger ports!
> > >
> >
> > Attached 2 logs.
> >
>
> ninja explain: output build.ninja older than most recent input /usr/local/lib/cmake/PolkitQt5-1/PolkitQt5-1Config.cmake (1572263732445520827 vs 1572263852000000000)
What a crazy level of precision on those timestamps!
> That causes the infinite loop. The build.ninja (Is the "Makefile" for
> ninja and CMake generates it) is older then
> /usr/local/lib/cmake/PolkitQt5-1/PolkitQt5-1Config.cmake. Of course it
> shouldn't be. NTPd issues? Any idea?
Aha. There was a bit of variation between the clocks on the machines,
120s or so spread. I guess dpb will have been waiting for one port to
build then immediately scheduling a port that depends on it.
I've synced the clocks, let's see how it goes now.
No comments:
Post a Comment