231570 - (bz-warnings) tracking bug for "uninitialized value" messages

Status: RESOLVED FIXED

(Bugzilla :: Bugzilla-General, defect, P3)

Description

[Max Kanat-Alexander]

I want to stamp all these things out -- they fill up my error log, and make it
tough to do valid debugging of bugs that may hide between these messages. 

This is a tracking bug, file other bugs as blocking this one.

I'm going to file a bug for every darn message in my error log. :-)

-M

Comment 1

[Dave Miller [:justdave]]

Any of these that exist on the 2.18 branch should be killed there as well.

Comment 2

[Max Kanat-Alexander]

I think what we need, for 2.18, is for somebody who actually runs a cvs-tip
installation locally to confirm or INVALID the bugs blocking this.

Comment 3

[Dave Miller [:justdave]]

These should still be fixed on the 2.18 branch when we find them, but I'm not
going to hold the release for them.

Comment 4

[Dave Miller [:justdave]]

There should be zero in the error log when we ship aside from complaints about
favicon.ico not existing. :)
(and other user mistyped urls and so forth)

Comment 5

[Myk Melez [:myk] [@mykmelez]]

"If it's not a regression from 2.18 and it's not a critical problem with
something that's already landed, let's push it off." - Dave

Comment 6

[Frédéric Buclin]

Only security and dataloss fixes will be accepted on the 2.20 branch. Retargetting to 2.22. The problem with these meta bugs is that we can almost never close them. :)

Comment 7

[Frédéric Buclin]

We did a great job in fixing all these warnings. There is no need to keep this meta bug open. We will fix remaining warnings as they come.