Hi, I posted the following message to mozilla.dev.builds newsgroup, but I wonder if there is a mozilla-wide change to nsITreeView lately? I noticed this while testing a patch to C-C TB locally.
(Considering that COMM-CENTRAL may have a slight delay in getting M-C changes, it may be that nsITreeView change may have happened a few weeks earlier or something). [Exception... "Failure arg 0 [nsITreeView.setTree]" nsresult: "0x80004005 (NS_ERROR_FAILURE) The error is fairly new. I did not see it on local PC until I updated the local source to build local DEBUG BUILD of TB. I thought initially it was my local patch that was causing the error, but upon investigation, it was hardly likely, and when I checked TBPL I realized it was causing trouble for everybody's compilation job. Any pointers? [I searched for nsITreeView.setTree in bugzilla but nothing came up. Is the simple search too simplistic?] TIA --- begin quote --- I think about 1/4 of 1000+ tests in |make mozmill| are failing now See https://tbpl.mozilla.org/?tree=Thunderbird-Trunk This is pretty bad, and looks to me that something about nsITreeView.setTree are the cause of major malfunctions. [Exception... "Failure arg 0 [nsITreeView.setTree]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" It is called in many places and resulted in this failure. Any idea which has caused this new regression? Simply stated, no would-be contributor can work on any patches in this state of affairs. TIA --- end quote _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
