Re: Testing for stabliity (was [Zope-dev] Re: large files and --pymalloc on the new release? (was Re: no more SIG11 ...))
A while back, someone was able to provide an Python Script that *always* crashed Zope.That's how Evan was able to determine that there was a stack size computation bug in the compiler module. I *think* he may have turned it in to a unit test. The current Zope test suite is the first line of defense. It can be run by using utilities/testrunner. If you do notice problems, the second best line of defense is an ability to narrow the problem down to a small, reproducible test case that has as few "external" dependencies (database adapters, products, etc.) as possible. If you can make it happen predictably, and it crashes Zope, we can (and will) fix it. - C > Is there a way to perform some tests or is there a testsuite that can be > used to stress test these issues? I too got bitten by these bugs + assorted > thread related errors, which has cost us very dearly in our project in terms > of both time, additional costs and unexpected hardware investments due to > change of deployment platform, so I *really* would like to have some way of > being able to confirm if these bugs are dealt with or no. I am not sure > there are any consistent tests for this, though, so hints on what to look > out for are equally appreciated. -- Chris McDonoughZope Corporation http://www.zope.org http://www.zope.com "Killing hundreds of birds with thousands of stones" ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: large files and --pymalloc on the new release? (was Re: no more SIG11 ...)
From: "Chris McDonough" <[EMAIL PROTECTED]> > Leonardo Rochael Almeida wrote: > > > Also, what about the --pymalloc? Is the binary Zope Python going to be > > compiled with it? should I still fear it? > > Dunno. Was it compiled in before? Isn't this an issue that is solved > in a roundabout way by not having stack pointer computation bugs in the > first place? I'm not sure how all of these bugs interact with each other. > > > We almost lost a big client and almost got a lawsuit because we were > > bitten by both (or would that be three: RestrictedCompiler, ceval and > > --pymalloc?) bugs at the same time and took a long time to figure out > > how to work around them. > > Sorry to hear that. > Is there a way to perform some tests or is there a testsuite that can be used to stress test these issues? I too got bitten by these bugs + assorted thread related errors, which has cost us very dearly in our project in terms of both time, additional costs and unexpected hardware investments due to change of deployment platform, so I *really* would like to have some way of being able to confirm if these bugs are dealt with or no. I am not sure there are any consistent tests for this, though, so hints on what to look out for are equally appreciated. thnks, /dario - Dario Lopez-Kästen Systems Developer Chalmers Univ. of Technology [EMAIL PROTECTED] ICQ will yield no hitsIT Systems & Services ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: large files and --pymalloc on the new release? (was Re: no more SIG11 ...)
Leonardo Rochael Almeida wrote: > Will the binary Linux release include large file support? > In other words, can I have a > 2G Data.fs? Hmmm.. I dont think the Zope 2.5b4 Linux binary is built this way, but in both Zope 2.4.4 and 2.5.0 it probably should be. We'd probably need someone to confirm that this doesn't cause problems on older (2.0, 2.2) Linux systems. FWIW, I built Python 2.1.2 with large file support on Linux 2.4 using the instructions on the posix-largefiles doc page in the Python docs without a problem. > Also, what about the --pymalloc? Is the binary Zope Python going to be > compiled with it? should I still fear it? Dunno. Was it compiled in before? Isn't this an issue that is solved in a roundabout way by not having stack pointer computation bugs in the first place? I'm not sure how all of these bugs interact with each other. > We almost lost a big client and almost got a lawsuit because we were > bitten by both (or would that be three: RestrictedCompiler, ceval and > --pymalloc?) bugs at the same time and took a long time to figure out > how to work around them. Sorry to hear that. - C ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
