Could you please add a nagios check to like we have for the win32 nightly builds? http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central/firefox-4.0b10pre.en-US.win64-x86_64.installer.exe Only for mozilla-central and tracemonkey branches for now (or do all branches if it is easier and we will ACK to a bug) Thanks!

We can do this ourselves. It's a change to mozilla/tools/tinderbox-configs/monitoring/Firefox_mozilla-central.txt and Firefox_tracemonkey.txt in cvs.mozilla.org/cvsroot. I'd question whether we should until we have a finalised refplatform and machines connected to production buildbot masters.

Right now, nightly builds is the only way to catch a compilation regression. We have caught already 2 of them on January.

looks like 3 in janurary now no builds are available for download

True. Yesterday's nightly failed. I will get to it and to this bug this week. My hands are full right now.

Currently a lot of people rely on the win64 nightly builds and I get poked about it every time they fail. I am planning on having a win64 nightly builds running on the real production masters rather than on staging.

Comment on attachment 509781 [details] [diff] [review] [CVS/tools/tinderbox-configs] add nagios checks for win64 nightly builds I don't think we should add these lines, even if we were to s/win64/win64-x86_64/ so they worked. We should continue to treat any win64 issues as a very low priority, and work on getting production machines up on production masters. Both of those are lower priority than any Fx4 work. Otherwise we will end up with nagios complaining about win64 for more than one day, and someone will ack the nagios alert. If any of the files we really care about get stale then nagios won't complain again, and we don't want to be in that state. If you really want some sort of automated check you can ask IT to set up a new check using a different control file, and only add the win64 files (or just hack up something temporary using cron).

I will hack a cronjob. No worries.

Indiscriminate ack'ing needs to stop, anyway!

Is there anything for IT to do on this bug, or should it go back to releng? If there is a request for IT, can someone please clarify what it is?

Nothing for IT to do here, and it's in our component already.

Nothing to be done until bug 647287 is fixed.

(In reply to Armen Zambrano G. [:armenzg] from comment #11) > Nothing to be done until bug 647287 is fixed. Bug you've mentioned is fixed now.

We actually did away with this type of nagios check.