#689 closed defect (invalid)
[MapServer]"testSetExtent" in "testMapScript.py" generates error
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | high | Milestone: | |
Component: | MapScript-SWIG | Version: | 4.3 |
Severity: | normal | Keywords: | |
Cc: |
Description
Running the test "testMapScript.py" and generates the error message below. I checked the scale value and I got "14.244422" which almost the same as you get "14.173236". Do you have an idea of what is causing this error? Fedora Core 1 ----------------------- Error: [nsavard@localhost python]$ python tests/testMapScript.py ..................................................................................F................................... ====================================================================== FAIL: testSetExtent (__main__.SetExtentTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "tests/testMapScript.py", line 616, in testSetExtent assert result == mapscript.MS_SUCCESS AssertionError ---------------------------------------------------------------------- Ran 118 tests in 14.321s FAILED (failures=1)
Change History (10)
comment:2 by , 20 years ago
I updated MapServer source code June 2th 2004 7h54 from CVS and the error is still there but at a different line number (see below). ====================================================================== FAIL: testSetExtent (__main__.SetExtentTestCase) ---------------------------------------------------------------------- Traceback (most recent call last): File "tests/testMapScript.py", line 431, in testSetExtent assert result == mapscript.MS_SUCCESS, result AssertionError: 1 ---------------------------------------------------------------------- Ran 116 tests in 6.993s
comment:3 by , 20 years ago
Have you done a 'make clean'? There has been a recent change to msMapSetExtent and msAdjustExtent.
comment:5 by , 20 years ago
Hmmm. Puzzling. Here is what goes on when we call mapObj's setExtent: mapObj.setExtent mapobject.c:msMapSetExtent Up to May 31, in revision 1.1 of mapobject.c, msSetExtent was returning a value of 1 on success. This was contrary to our exception of mapscript.MS_SUCCESS (0) hence the failure in the test that you noted in comment #2. since May 31, revision 1.2 of mapobject.c, msSetExtent returns MS_SUCCESS as we expect. So I am no longer getting the failure. Additionally, I am not getting any failure with respect to the expected extent values. The recent work to msAdjustExtent must have fixed that. Do you have revision 1.2 (or better yet 1.3) of mapobject.c? If not, maybe we have some makefile problem.
comment:6 by , 20 years ago
I have mapobjectc revision 1.3 (see below). * $Id: mapobject.c,v 1.3 2004/05/31 20:20:56 frank Exp $ *
comment:7 by , 20 years ago
Normand, how are you? Does this bug still occur for you? I do not see it in mapserver 4.2 or 4.3 (CVS). Howard Butler can also not reproduce the bug in his nightly builds.
comment:9 by , 20 years ago
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
Verified on Fedora Core 2 and this bug could be reproduce.
comment:10 by , 20 years ago
I meant verified on Fedora Core 2 and this bug could NOT be reproduce. Tht's a big difference. Sorry for that.
Note:
See TracTickets
for help on using tickets.