HI, > At Adobe, if new failures appeared and it was in tests that could have > been affected by code you changed, you had to revert or fix immediately.
We are not at Adobe, other committers should be willing to help out on bug fixing and testing in a collaborative way. We want to encourage people to put forward or commit fixes, not scare them away with if all tests don't pass you have to revert. I don't want to add the extra burden on people of having to run ALL of the mustella tests before submitting a fix, let the CI system do that for them. > If so, Justin, can you revert some of your recent checkins in those areas? Sorry but I'm not going to revert a checkin that actually fixes a bug and when is it most likely that the test is now not working. If the fix had introduced an obvious error then yes reverting or changing the fix would be the way to go. We have a trunk and a develop branch, the whole point of the develop branch is for it to be a work in progress. As I said before the DG test is failing due to a correct out of range RTE, the test needs changing, has anyone actually looked at the test? > I use FDB, but there is supposedly a way to launch a SWF in the FB > debugger without having to build a process around it. I've never been able to get either to work on OSX/my environment. Thanks, Justin
