Closed Bug 7091 Opened 26 years ago Closed 26 years ago

sidebar does tinderbox query every minute

Categories

(Core Graveyard :: RDF, defect, P1)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: endico, Assigned: slamm)

References

()

Details

Don't let m6 ship with this. The sidebar is set to run a tinderbox query every minute. If m6 is released with this it will be a big load on our server (which runs tinderbox, bonsai and cvs). Suggested changes: 1) make this fire less frequently. (every 5 minutes?) 2) Change the url so it that instead of running the tinderbox script directly, it merely looks at an rdf file. The rdf file is created by a cron job on cvs-mirror every 5 minutes. Serving this text file should be a lot faster than running a perl script. The suggested new url is: http://cvs-mirror.mozilla.org/webtools/tinderbox/SeaMonkeyFlash.rdf Check in a script to mozilla/webtools/tinderbox and I'll set up crontab to run it. Sound good?
Priority: P3 → P1
Target Milestone: M6
I wouldn't mind seeing 1) happen just because it does some blocking and bad focus things on the mac on every query. For example, if you're typing in the URL bar and a query starts, you lose focus and have to click back in to continue typing.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → FIXED
I fixed both problems: 1. Flash item and tinderbox panel reload every 5 minutes. 2. The documents pull from tinderbox are now static pages: http://cvs-mirror.mozilla.org/webtools/tinderbox/SeaMonkey/flash.rdf http://cvs-mirror.mozilla.org/webtools/tinderbox/SeaMonkey/panel.html The pages are updated whenever tinderbox receives mail updating the status of builds. Also note that the pages are generated for any other trees on tinderbox. For instance, http://cvs-mirror.mozilla.org/webtools/tinderbox/SeaMonkey-Ports/flash.rdf http://cvs-mirror.mozilla.org/webtools/tinderbox/SeaMonkey-Ports/panel.html Marking fixed.
Status: RESOLVED → VERIFIED
verified, the query is now every 300 seconds also, the pages look static so 2) is also verified
Status: VERIFIED → REOPENED
So who reopened this, and why?
Status: REOPENED → RESOLVED
Closed: 26 years ago26 years ago
ramar@cnet.com seems to be going on a minor rampage. This isn't the only bug he has REOPENED without comment, and he randomly tweaked several fields on yet another bug. His Bugzilla account has been disabled until he can explain his actions. I am returning this bug back to its VERIFIED state.
Status: RESOLVED → VERIFIED
Also recreated the same problem on ninoschka's machine.
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.