16 Aug
2011
16 Aug
'11
8:35 p.m.
ACPI does work on VirtualBox. I performed the majority of my testing on VirtualBox. Also,
I need a stack trace from that crash to have any clue where the corruption is (still not
much of one). I have had indications of a pool corruption bug in ACPI and I need as many
logs as possible to try to track it down.
Regards,
Cameron
On Aug 16, 2011, at 4:04 PM, caemyr(a)myopera.com wrote:
Yet another regression. Revision
http://svn.reactos.org/svn/reactos?view=rev&revision=53257 breaks up VBox testcd
runtime, due to pool corruption bugchecks. Its been 37h since it started. Can we have it
fixed or reverted? This is our sole working testbot, so it could be important.
I know that introducing new features to ReactOS is cool, but unfortunately, once again
we, the testers, are left alone with the bugs introduced by them. Its kinda hard to me, as
I often feel as some kind of oppressor, pointing out that something fails, only to hear
back that its my or no one's problem.
Yes, i am aware that i could probably avert it by disabling ACPI in testbot's VM. I
am not going to do this for at least two reasons:
- if i do so, everyone will feel contempt once more and forget about this, until it crops
up sometime in the future, requiring a regtesting then. Now guess who will be asked to do
so, and why that person is going to be a tester;
- if this ACPI implementation is mature enough to be ENABLED by DEFAULT, it should at
least work in VBOX. This is why i did patchbot for, but unfortunately, too many prefer to
commit to trunk (and not fix it up then);
No testman's results? Anyone cares? Naah, lets have a few more features. Just when
would you like to have a new release? Until end of the year? Forget it...
Best regards
_______________________________________________
Ros-dev mailing list
Ros-dev(a)reactos.org
http://www.reactos.org/mailman/listinfo/ros-dev