Failure in the gcov processing find command, whose test is AWOL

[fish2000]

The gcov processing command issued by codecov contains malformed find predicates, and always fails. The failure looks like this:

… this is on macOS, which offers BSD find as the default. I verified the failure by installing GNU findutils with Homebrew and changing a local clone of codecov to use that (as /usr/local/bin/gfind) – the error message is slightly more helpful:

`/usr/local/bin/gfind /Users/fish/Dropbox/CLU/clu -not -path './bower_components/**' -not -path './node_modules/**' -not -path './vendor/**' -type f -name *.gcno  -exec gcov -pb  {} +` exited with status 1, error: “gfind: paths must precede expression: `'”

… the relevant gcov-related test is, I think, the only test in the codecov suite that is completely commented out and skipped:

    def test_gcov(self):
        self.skipTest("Need to fix this test...")
        # if self._env.get('TRAVIS') == 'true':
        #     self.write_c()
        #     output = self.run_cli(token='a', branch='b', commit='c')
        #     self.assertEqual(os.path.exists('hello.c.gcov'), True)
        #     report = output['reports'].split('<<<<<< network\n')[1].splitlines()
        #     self.assertIn('hello.c.gcov', report[0])
        # else:
        #     self.skipTest("Skipped, works on Travis only.")

… which suggests at least an acknowledgement of the problem, if not a genesis of same.

[Luttik]

I also have the gcov find issue on github actions.

[sineverba]

I can confirm this bug and with v2.0.15 it works. Related also to this issue: #249.

[nmoinvaz]

In PR #217 I have replaced the calls to find with a python function that does the same thing.

[thomasrockhu]

We recently released 2.1.3 which pulls in #217.