new chararray test fails on Mac OS X
From the svn log it looks like the tests are intended to fail? However I would prefer tests that are designed only to fail when problems occur. Otherwise we end up with problems with our automatic build and test scripts. Thanks, Chris ====================================================================== FAIL: test_mul (test_defchararray.TestOperations) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/chanley/dev/site-packages/lib/python/numpy/core/tests/test_defcha rarray.py", line 49, in test_mul assert all(Ar == (self.A * r)) AssertionError ====================================================================== FAIL: test_rmul (test_defchararray.TestOperations) ---------------------------------------------------------------------- Traceback (most recent call last): File "/Users/chanley/dev/site-packages/lib/python/numpy/core/tests/test_defcha rarray.py", line 65, in test_rmul assert all(Ar == (r * self.A)) AssertionError ---------------------------------------------------------------------- Ran 1930 tests in 13.130s FAILED (failures=2) <nose.result.TextTestResult run=1930 errors=0 failures=2>
n.__version__ '1.2.0.dev5385'
-- Christopher Hanley Systems Software Engineer Space Telescope Science Institute 3700 San Martin Drive Baltimore MD, 21218 (410) 338-4338
On Thu, Jul 10, 2008 at 10:06 AM, Christopher Hanley <chanley@stsci.edu> wrote:
From the svn log it looks like the tests are intended to fail? However I would prefer tests that are designed only to fail when problems occur. Otherwise we end up with problems with our automatic build and test scripts.
Sorry about that, I just wanted to make sure the tests would actually fail on all the builders before the bug in chararray is fixed. I just checked in a change that disables the failing portions of the test.
On Thu, Jul 10, 2008 at 09:26, Alan McIntyre <alan.mcintyre@gmail.com> wrote:
On Thu, Jul 10, 2008 at 10:06 AM, Christopher Hanley <chanley@stsci.edu> wrote:
From the svn log it looks like the tests are intended to fail? However I would prefer tests that are designed only to fail when problems occur. Otherwise we end up with problems with our automatic build and test scripts.
Sorry about that, I just wanted to make sure the tests would actually fail on all the builders before the bug in chararray is fixed. I just checked in a change that disables the failing portions of the test.
For things that you don't expect to be platform specific, there is no need. For things that you do expect to be platform specific on platforms that you cannot access, please ask for volunteers. Make an SVN branch if the changes are extensive. I would like to keep to the rule of not checking in unit tests (on trunk or a 1.1.x branch, etc.) that you expect to fail. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
On Thu, Jul 10, 2008 at 8:14 PM, Robert Kern <robert.kern@gmail.com> wrote:
For things that you don't expect to be platform specific, there is no need. For things that you do expect to be platform specific on platforms that you cannot access, please ask for volunteers. Make an SVN branch if the changes are extensive. I would like to keep to the rule of not checking in unit tests (on trunk or a 1.1.x branch, etc.) that you expect to fail.
Ok.
On Thu, Jul 10, 2008 at 19:20, Alan McIntyre <alan.mcintyre@gmail.com> wrote:
On Thu, Jul 10, 2008 at 8:14 PM, Robert Kern <robert.kern@gmail.com> wrote:
For things that you don't expect to be platform specific, there is no need. For things that you do expect to be platform specific on platforms that you cannot access, please ask for volunteers. Make an SVN branch if the changes are extensive. I would like to keep to the rule of not checking in unit tests (on trunk or a 1.1.x branch, etc.) that you expect to fail.
Ok.
Thanks. -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
2008/7/11 Robert Kern <robert.kern@gmail.com>:
On Thu, Jul 10, 2008 at 09:26, Alan McIntyre <alan.mcintyre@gmail.com> wrote:
On Thu, Jul 10, 2008 at 10:06 AM, Christopher Hanley <chanley@stsci.edu> wrote:
From the svn log it looks like the tests are intended to fail? However I would prefer tests that are designed only to fail when problems occur. Otherwise we end up with problems with our automatic build and test scripts.
Sorry about that, I just wanted to make sure the tests would actually fail on all the builders before the bug in chararray is fixed. I just checked in a change that disables the failing portions of the test.
For things that you don't expect to be platform specific, there is no need. For things that you do expect to be platform specific on platforms that you cannot access, please ask for volunteers. Make an SVN branch if the changes are extensive.
Branches may also be built using the buildbot. Stéfan
On Fri, Jul 11, 2008 at 02:06, Stéfan van der Walt <stefan@sun.ac.za> wrote:
2008/7/11 Robert Kern <robert.kern@gmail.com>:
On Thu, Jul 10, 2008 at 09:26, Alan McIntyre <alan.mcintyre@gmail.com> wrote:
On Thu, Jul 10, 2008 at 10:06 AM, Christopher Hanley <chanley@stsci.edu> wrote:
From the svn log it looks like the tests are intended to fail? However I would prefer tests that are designed only to fail when problems occur. Otherwise we end up with problems with our automatic build and test scripts.
Sorry about that, I just wanted to make sure the tests would actually fail on all the builders before the bug in chararray is fixed. I just checked in a change that disables the failing portions of the test.
For things that you don't expect to be platform specific, there is no need. For things that you do expect to be platform specific on platforms that you cannot access, please ask for volunteers. Make an SVN branch if the changes are extensive.
Branches may also be built using the buildbot.
What is the procedure for requesting this? Do we just email you and ask for the buildbots to build a particular branch? -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
2008/7/11 Robert Kern <robert.kern@gmail.com>:
Branches may also be built using the buildbot.
What is the procedure for requesting this? Do we just email you and ask for the buildbots to build a particular branch?
Go to the waterfall display and click on a build-slave name at the top. Use "Force build", and type the branch name in the appropriate field. By default it is 'trunk', so I think you'll have to use 'branches/branchname'. Stéfan
On Fri, Jul 11, 2008 at 02:39, Stéfan van der Walt <stefan@sun.ac.za> wrote:
2008/7/11 Robert Kern <robert.kern@gmail.com>:
Branches may also be built using the buildbot.
What is the procedure for requesting this? Do we just email you and ask for the buildbots to build a particular branch?
Go to the waterfall display and click on a build-slave name at the top. Use "Force build", and type the branch name in the appropriate field. By default it is 'trunk', so I think you'll have to use 'branches/branchname'.
Excellent! Thank you! -- Robert Kern "I have come to believe that the whole world is an enigma, a harmless enigma that is made terrible by our own mad attempt to interpret it as though it had an underlying truth." -- Umberto Eco
participants (4)
-
Alan McIntyre -
Christopher Hanley -
Robert Kern -
Stéfan van der Walt