Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Automated report: NetBSD-current/i386 build failure



> On Mon, Jul 19, 2021 at 01:28:06AM +0000, David Holland wrote:
>  > that is... less than helpful :-(

>  > it looks like CVS randomly didn't commit some of my changes,
>  > investigating...

> Yeah, not sure what happened; something caused it to, apparently,
> think a few of the files in the second changeset still had the
> original checkout timestamps. This makes it completely blind to any
> changes in them (even if you run cvs diff explicitly) until you touch
> the files.

> Not sure how this happened. The affected files were all ones also
> committed in the first changeset, which is probably not an accident,
> but it wasn't all those files, just an arbitrary subset of them.
> Doesn't make much sense.

> High time we moved away from CVS.

> Anyway, I am pretty sure I've found all the offending files and
> committed them for real. If anything's still bust, holler...

> On Mon, Jul 19, 2021 at 10:32:20AM +0900, Rin Okuyama wrote:
>  > Logs below are usually more helpful.

> Right... I wonder what happened to bracket's error-matching script; it
> usually does better than that.

> David A. Holland
> dholland%netbsd.org@localhost

I too would like to move away from CVS.  What is happening on the switch to Mercurial?

Last night, I was hit by a bug for the second time on NetBSD-9.99.82 amd64, when running
cvs up -dP -A
from /usr/src

I was running in a root window in Xorg (native) with icewm 1.4.2.

cvs download stopped, keyboard was not recognized though the mouse pointer could move, though clicks had no effect.

I later found a message in the Xorg log file about GPU hang: only the second time this has happened, and only when running
cvs up -dP -A 
from /usr/src in NetBSD 9.99.82 

Not sure if GPU hang is a hardware problem or a software problem.

Strangely, I could read the /home partition by NFS from the other computer.

I had to hit the Reset button.

On the second time, last night, part of the src tree was messed up, with messages about invalid CVS root in some package subdiretories, looked to be within external/bsd

I ran rm -Rf external/bsd, then again cvs up -dP -A, but was stopped in src/external by a broken pipe from the server.

So the src tree is partly messed up, and I don't know what to do.

I could try again from non-X console, or possibly from root xterm with a quick switch to another window.

Or should I try with hg?  I have devel/mercurial built and installed.

Now to find a tutorial for Mercurial for git users: There was one, but I can no longer find it.

Tom



Home | Main Index | Thread Index | Old Index