Hi Andreas, Hi Paul,

Paul Gevers, on 2020-12-10 13:50:59 +0100:
> On 10-12-2020 13:10, Andreas Tille wrote:
> > My guess is that kmc was developed under and designed for amd64 and it
> > runs there.  That's explicitly the case for the latest upstream version
> > which will not support any arm* out of the box (if I understand Étienne
> > correctly).  I do not see any need to stress test our hardware with
> > some software that will be outdated soonish.

I'm merging my changes for the kmc 3.1.1 amd64-only update; will
push very soon.

> I couldn't resist. I started it up and it hangs.
> 
> Paul
[...]
> # In the end, default options should, ideally, work on any configuration.
> echo 'Running kmc (default thread count)'
> Running kmc (default thread count)
> rm -f 1.kmc_suf 1.kmc_pre
> kmc -ci1 -m1 -k28 $ORIGDIR/debian/tests/sample_6.fastq.gz 1 .
> *

Thank you very much for the full log!  :)

I was hoping to see it on the ci logs during my lunch hour, but
as I understand now, it was not accessible from the web page (or
rather well hidden).  Looks like I either screwed my patch or
the general issue is way more intricate than I first thought.
Looks like I'll have to locate again that RoM removal procedure.

Have a nice evening,
-- 
Étienne Mollier <etienne.moll...@mailoo.org>
Fingerprint:  8f91 b227 c7d6 f2b1 948c  8236 793c f67e 8f0d 11da
Sent from /dev/pts/1, please excuse my verbosity.

Attachment: signature.asc
Description: PGP signature

Reply via email to