When I make a click in the option show dependency graph, I can´t see any graph, Is any thing wrong?

This CGI may well have been disabled temporarily on bugzilla.mozilla.org. CCing Myk for confirmation. Gerv

No, graphs don't work on bmo because its set up to use webdot, and webdot doesn't work with vhosting. Theres a bug on having bmo use a local dot, somewhere...

I am assigning all the bugs I am not working on in the immediate future to nobody@bugzilla.org. This means: - I will be able to search for bugs assigned to me as a list of bugs I'm going to fix (which is as it should be), and - people won't falsely assume I might be about to fix a bug when I'm not. Gerv

ATTOW I just get ERROR The requested URL could not be retrieved [...] Zero Sized Reply What's a webdot, for that matter?

As written this is a bug against mozilla.org, not Bugzilla itself, and it's a dupe. *** This bug has been marked as a duplicate of 140498 ***

At this time, I can only see it working in the trivial case of a bug (such as this one at the moment) that doesn't depend on or block anything. Otherwise, it's still just the same error. It appears that the operation times out; indeed the W3C validator gives the error "500 read timeout" on any bug I can find that has dependencies. I consider whether graphviz is installed and whether it actually works to be two separate issues. On these grounds and the absence of any response to my comment on bug 140498, I'm reopening this one.

Due to the proliferation of metabugs, any bug that has a dependency is probably going to have a HUGE graph, so I wouldn't put it past it to be timing out trying to create it. Perhaps this will be alleviated some when we move to the new server in the next couple weeks, which has 4 x 2.8 GHz CPUs (current server is 2 x 450 MHz).

I think I've found the root cause of the problem: bug 102622. Adding as dependency.

*** Bug 239471 has been marked as a duplicate of this bug. ***

Since this has turned out to be a bug in the Bugzilla software and not our setup on bmo there's really nothing I can do here until Bugzilla is fixed and having this in my buglist is just taking up space, so having this bug around has very little point to it. Resolving as a dupe of the Bugzilla bug causing this. *** This bug has been marked as a duplicate of 102622 ***

I wouldn't call it a dupe - this is why I put it in as a dependency. Rather, I considered it effectively a tracker for issues that are rendering the dependency graph feature practically useless on b.m.o., even if only one such issue is listed at the moment. And that once once bug 102622 is fixed, we'd wait for b.m.o to be upgraded and then to see it working for real before ticking this one off. Still, let's see what people think. Moreover, if it's cluttering your bug list then can't you just reassign it?