[Stackless] Fwd: Stackless 2.5 branch updated for Python 2.5.1c1

Santiago Gala sgala at apache.org
Sun Apr 15 14:20:22 CEST 2007


---------- Forwarded message ----------
From: Richard Tew <richard.m.tew at gmail.com>
Date: Apr 15, 2007 1:55 PM
Subject: Re: [Stackless] Stackless 2.5 branch updated for Python 2.5.1c1
To: Santiago Gala <sgala at apache.org>
Cc: stackless <stackless at stackless.com>

On 4/15/07, Santiago Gala <sgala at apache.org> wrote:
> linux amd64 (Core 2 Duo) results:
> $ ../../python runAll.py
> ..........E......F.E..............
> ...................EF.............

My suspicion was that the amd64 hard switching support was not working
correctly for Hieu's setup.  This reinforces that belief.  Given that
it obviously has worked for someone in the past, based on past
experience, I would assume the problem lies with gcc.

So for either Hieu or yourself: What version of gcc did you compile
with?  Can you switch to an older gcc version and recompile and then
run the Stackless tests again?  If so, do they pass or fail still?

Oops, I forgot to paste:

$ ./python
Python 2.5.1c1 Stackless 3.1b3 060516 (release25-maint, Apr 15 2007,
13:23:04)
[GCC 4.1.2 (Gentoo 4.1.2)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>

I have around just an old gcc-3.4.6, but I would not recommend using gcc-3
to anybody currently, the quality of the generated code pales in the
comparison.

The python2.5 regressions are the same. Stackless unittests work like:

$ ../../python runAll.py
.................F................
======================================================================
FAIL: testXrange (test_pickle.TestConcretePickledTasklets)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "./test_pickle.py", line 197, in testXrange
    self.run_pickled(xrangetest, 20, 13)
  File "./test_pickle.py", line 164, in run_pickled
    self.assertEquals(new_rval, old_rval)
AssertionError: 9159019261958553619 != 19

----------------------------------------------------------------------
Ran 34 tests in 1.400s

FAILED (failures=1)
(and then the process stays forever at 100% CPU until I kill it:

FAILED (failures=1)
Traceback (most recent call last):
  File "runAll.py", line 55, in <module>
    unittest.TextTestRunner().run(testSuite)
  File "/home/sgala/newcode/stackless/Lib/unittest.py", line 705, in run
    test(result)
  File "/home/sgala/newcode/stackless/Lib/unittest.py", line 437, in
__call__
    return self.run(*args, **kwds)
)

Now:

$ ../../python
Python 2.5.1c1 Stackless 3.1b3 060516 (release25-maint, Apr 15 2007,
14:09:48)
[GCC 3.4.6 (Gentoo 3.4.6-r2, ssp-3.4.6-1.0, pie-8.7.10)] on linux2
Type "help", "copyright", "credits" or "license" for more information.


One of the most useful pieces of information I could have when people
paste test output (and I should have asked for this) is the header
when you run the interpreter.

e.g. Python 2.5 Stackless 3.1b3 060516 (python-2.5:53557:53567, Jan 25
2007, 22:01:46) [MSC v.1310 32 bit (Intel)] on win32

Thanks,
Richard.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.stackless.com/pipermail/stackless/attachments/20070415/e52bd2e9/attachment.htm>
-------------- next part --------------
_______________________________________________
Stackless mailing list
Stackless at stackless.com
http://www.stackless.com/mailman/listinfo/stackless


More information about the Stackless mailing list