Daniel Jakots writes:
> On Sat, 16 Apr 2016 16:24:43 +0200, Jeremie Courreges-Anglas
> wrote:
>
>> Those tests are supposed to be run against a copy of upstream's git
>> repo. All tests succeed on 0.6.4.
>>
>> I'm not sure how useful it is to "enable" tests here. Someone
>> updating to a newe
On Sat, 16 Apr 2016 16:24:43 +0200, Jeremie Courreges-Anglas
wrote:
> Those tests are supposed to be run against a copy of upstream's git
> repo. All tests succeed on 0.6.4.
>
> I'm not sure how useful it is to "enable" tests here. Someone
> updating to a newer version should probably run the
Daniel Jakots writes:
> Hi,
>
> Here's an update for py-gitdb.
>
> While there I add some tests. Not all of them are passing but it looks
> like again a build env problem. I tried to fiddle with
> "GITDB_TEST_GIT_REPO_BASE" but no luck.
Those tests are supposed to be run against a copy of upstre
On Sat, 9 Apr 2016 22:23:56 +0500, Alexandr Shadchin
wrote:
> For coverage need add py-coverage or simplify test to "cd ${WRKSRC}
> && nosetests"
>
> Otherwise ok shadchin@
Thanks. New diff:
Index: Makefile
===
RCS file: /cvs/port
On Tue, Apr 05, 2016 at 07:26:26PM +0200, Daniel Jakots wrote:
> Hi,
>
> Here's an update for py-gitdb.
>
> While there I add some tests. Not all of them are passing but it looks
> like again a build env problem. I tried to fiddle with
> "GITDB_TEST_GIT_REPO_BASE" but no luck.
>
> Cheers,
> Dani
Hi,
Here's an update for py-gitdb.
While there I add some tests. Not all of them are passing but it looks
like again a build env problem. I tried to fiddle with
"GITDB_TEST_GIT_REPO_BASE" but no luck.
Cheers,
Daniel
Index: Makefile
===