> On 18 Jan 2018, at 23:40, SZEDER Gábor <szeder.dev@xxxxxxxxx> wrote: > > On Thu, Jan 18, 2018 at 10:40 PM, René Scharfe <l.s.r@xxxxxx> wrote: >> Am 16.01.2018 um 18:11 schrieb SZEDER Gábor: >>> Unfortunately, most of the changes coming from 'strbuf.cocci' don't >>> make any sense, they appear to be the mis-application of the "use >>> strbuf_addstr() instead of strbuf_addf() to add a single string" rule: >>> >>> - strbuf_addf(&sb_repo, "%d", counter); >>> + strbuf_addstr(&sb_repo, counter); >>> >>> It seems that those rules need some refinement, but I have no idea >>> about Coccinelle and this is not the time for me to dig deeper. >>> >>> What makes all this weird is that running 'make coccicheck' on my own >>> machine doesn't produce any of these additional proposed changes, just >>> like at René's. Can it be related to differing Coccinelle versions? >>> Travis CI installs 1.0.0~rc19.deb-3; I have 1.0.4.deb-2. >> >> The version difference may explain it, but I couldn't find a matching >> bugfix in http://coccinelle.lip6.fr/distrib/changes.html when I just >> skimmed it. I wonder if the following patch could make a difference: > > Yes, it does, now all those nonsense suggestions are gone on Travis CI. > > https://travis-ci.org/szeder/git/jobs/330572425#L713 > > Those "memmove() -> MOVE_ARRAY" suggestions are still there, of course. Nice! Travis CI runs Ubuntu Trusty as current base image with Coccinelle version "1.0.0~rc19.deb-3": https://packages.ubuntu.com/trusty/coccinelle I was experimenting with a docker container that has the latest stable version of Coccinelle installed ("1.0.4.deb-2"). We could run this docker container inside of the Travis CI job similar to the 32-bit job. But with René's changes that doesn't seem to be necessary anymore! - Lars PS: Thanks a lot Gábor for recognizing and fixing the invalid Travis CI Coccinelle build!
