Go into ntoskrnl and svn up -r 45013 should take care of it.......
On Wed, Jan 13, 2010 at 3:31 AM, Ged Murphy gedmurphy@gmail.com wrote:
sir_richard,
Trunk is still broken and is causing issues for some of the dev team.
You can see the problems in our buildbot test machine:
- Go to the following address : http://build.reactos.org:8010
- under the x86_(Test) machine, click on the stdio for the 'test' stage.
- You'll see stage 1 complete, the stage 2 bugchecks.
Could you please address this problem before continuing your work as it's ruining the test system. The problem is that because our test machine can't run we aren't able to monitor other commits in other areas, meaning we're potentially introducing other bugs that we're now missing. According to our policy, failure to fix this soon (it's normally 24 hours) will result in us having to freeze development on trunk until the bug is fixed. If we're unable to fix it in a reasonable amount of time then the changes need to be reverted until we have a bootable OS again.
Regards, Ged Murphy.
James Tabor wrote:
Go into ntoskrnl and svn up -r 45013 should take care of it.......
That only fixes building on local machines. It doesn't avoid the fact that trunk is now completely untested by our regression testing engine. This opens us up to missed bug introduction whilst people continue to commit. IMO, we should now consider locking trunk until this is fixed.
Ged.