Closed gitlab-importer closed 4 months ago
gitlab-importer
commented
19 years ago In Heptapod by bitbucket_importer on May 16, 2005, 16:22
Created originally on Bitbucket by hpk
I guess it does make sense in the longer run to know which revision exactly
broke long-running translation processes. We need to define which
goals/scripts we want to run and how to invoke/check them.In Heptapod by bitbucket_importer on May 16, 2005, 16:58
Created originally on Bitbucket by ctismer (Christian Tismer)
Holger Krekel wrote:
> New submission from Holger Krekel <hpk@trillke.net>:
>
> I guess it does make sense in the longer run to know which revision exactly
> broke long-running translation processes. We need to define which
> goals/scripts we want to run and how to invoke/check them.
This is a good idea.
The effect I just had that I saw a terrible SomeObjectness
increase on targetpypymain.
I suggest that targetpypymain should be such a candidate.
btw.: why did I get this message twice? Triggered by some
nosiness?
--
Christian Tismer :^) <mailto:tismer@stackless.com>
tismerysoft GmbH : Have a break! Take a ride on Python's
Johannes-Niemeyer-Weg 9A : *Starship* http://starship.python.net/
14109 Berlin : PGP key -> http://wwwkeys.pgp.net/
work +49 30 802 86 56 mobile +49 173 24 18 776 fax +49 30 80 90 57 05
PGP 0x57F3BF04 9064 F4E1 D754 C2FF 1619 305B C09C 5A3B 57F3 BF04
whom do you want to sponsor today? http://www.stackless.com/In Heptapod by @arigo on May 16, 2005, 18:01
On Mon, May 16, 2005 at 07:58:29PM +0200, Christian Tismer wrote:
> I suggest that targetpypymain should be such a candidate.
Yes, that would be very helpful. We need to figure out a policy for
re-running this, though, because a full targetpypymain after each
check-in is probably too wasteful...In Heptapod by bitbucket_importer on Apr 3, 2006, 08:12
Created originally on Bitbucket by hpk
we need more translation tests with 0.9.In Heptapod by bitbucket_importer on Jun 12, 2006, 14:35
Created originally on Bitbucket by mwh (Marcius Herbert)
I'm unsure what this issue needs before we can close it.
Practically speaking, the pypytester builds are an effective tool for finding translation problems.
issue205 is about running the tests with a built binary. "we need more translation tests with 0.9." is a
bit ambiguous, py.test translator/ already takes around an hour on my machine, that's long enough :-)
So I'm going to close this. Feel free to disagree, but think about not assigning it to 0.9 :)
In Heptapod by bitbucket_importer on May 16, 2005, 16:22
Created originally on Bitbucket by hpk
From (bugs.pypy.org)