Hi Paul,
I recently had a look at deepnano and bug #921566, about the
test crashing in timeout. I modified the test script to cap the
total number of OpenMP threads, in hope this helps in case this
is an improper handling of very large cores count, and I also
enforced a ten minutes timeout on
Hi Andreas,
On 13-12-2019 17:24, Andreas Tille wrote:
> However, even
>
> https://ci.debian.net/packages/p/deepnano
>
> does not exist any more. Am I missing something?
A typo: https://ci.debian.net/packages/d/deepnano/
However, because of the shear amount of tests and size of the logs,
Hi Paul,
in our advent bug squashing party I wanted to have another look into
this.
On Sat, Feb 09, 2019 at 01:23:22PM +0100, Paul Gevers wrote:
> > I admit I see no better solution than to deactivate the autopkgtest.
>
> That would really be a shame. There is really a regression in you
>
Hi Andreas,
On 08-02-2019 21:17, Andreas Tille wrote:
> I admit I see no better solution than to deactivate the autopkgtest.
That would really be a shame. There is really a regression in you
package, as the test used to finish in within two minutes and now times
out after 2:47 hours. So
Hi Paul,
On Fri, Feb 08, 2019 at 09:02:23PM +0100, Paul Gevers wrote:
> Control: reopen -1
>
> On 07-02-2019 09:45, Debian Bug Tracking System wrote:
> > deepnano (0.0+git20170813.e8a621e-3) unstable; urgency=medium
> > .
> >* Use less data for autopkgtest
> > Closes: #921566
>
>
Control: reopen -1
On 07-02-2019 09:45, Debian Bug Tracking System wrote:
> deepnano (0.0+git20170813.e8a621e-3) unstable; urgency=medium
> .
>* Use less data for autopkgtest
> Closes: #921566
This seems to be not enough to fix this issue. I didn't lift the ban,
but trigger one run on
6 matches
Mail list logo
