Closed Bug 64137 Opened 24 years ago Closed 24 years ago

Cannot review code changes for up to 24 hours after checkins

Categories

(Webtools Graveyard :: Bonsai, defect)

Product:
Webtools Graveyard
Component:
Bonsai
Platform:
All
Windows NT
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: nelson, Assigned: tara)

References

(
URL
)

Details

I need to review checkins to NSS this week as quickly as possible 
after they're made.  There's a newsgroup n.p.m.crypto.checkins
which receives a message right after every checkin.  But I find
that the links to bonsai in those messages do not work for up to
24 hours after the checkin is made. 

The problem is that it seems that the act of checking in a change 
causes the bonsai system to break immediately and stay broken for
up to a whole day.  I've seen this over and over.  In the past this
has been caused by "broken mirrors", but I don't know what the cause
of the present behavior is.

As of this writing, a visit to 
http://bonsai.mozilla.org/cvsview2.cgi?command=DIRECTORY?subdir=mozilla/security
/nss/cmd/selfserv?files=selfserv.c?root=/cvsroot
(one of today's checkins) returns the response:

> Content-type: text/html 
>
> Software error:
>
> bogus characters in options at /opt/webtools/bonsai/cvsview2.cgi line 404. 
>
> Please send mail to this site's webmaster for help.
I'm "resolving" this bug myself.  It seems that, in this case,
the browser I was using was at fault.  
It substituted "?" for "&" in the link, that is, it did not 
faithfully ask for the URL as it appeared in the posted message.
So, in this case, bonsai is not at fault.
The next time I run into the checkin-breaks-the-mirror problem, 
I will reopen this bug.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
V.
Status: RESOLVED → VERIFIED
This is actually an ongoing problem.  
The trouble is that if one waits 24 hours, the servers get updated
and the problem appears to have been solved.  So, if someone looks
into any report the next day after it is reported, they will not
see the problem.  When we can get someone to look into this problem
when it is happening (not the next day), then we'll make progress 
on this bug.
Product: Webtools → Webtools Graveyard
You need to log in before you can comment on or make changes to this bug.