Re: Bug Triage Day - Dec 27/28th - roundup

> > To be honest I had no idea we were having a bug triage this weekend - > it was mostly just me clearing of my TODO list that caused this fix > ups :) SShh, I'll claim it as progress anyhow! > > > I have a question tho - Have asked it before but I think we got > segwayed into another discussion, those skipped tests, it's a bit > high, can we see what is being skipped ? Sure; I can do a one off in verbose mode (performance is the only thing stopping me from doing it by default) if you like. Majority of these would be tests which need special configuration, which used to fail or error. An example of the kind of thing: http://pear.php.net/bugs/bug.php?id=14884 My long term plan is to slowly see the uptake of HTTP_Request2 in a lot of places, which makes simulating HTTP trivial, and then delving into more specialized packages and simulating results there too. Unfortunately, this often means significant refactoring, and sometimes a BC break - Services_ExchangeRates, for instance, took a lot of effort to get simulated responses happening (a whole day?) And can we somehow get it > down granted that it isn't some win only tests, and if they are win > tests, should we try to get a win box to handle that and setup CI > which can merge with your results (I can obtain a box I'm told) - Unfortunately, the unit test suite uses symlinks to simulate packages being installed, so its not so windows friendly :( > > Having a page with results from individual box runs and then a merged > page would be awesome :-) Agreed! However, there's a lot of customised differences ( http://lauken.com/doconnor/customised.diff) to get tests running, and I'm taking it one bug at a time at the moment, so getting another box up might be a bit... uh ... challenging :D Certainly worth doing; as it will highlight differences or rough edges or places I've forgotten. > > Regards > Helgi >