Another item from my 'automated testing' list: use travis-ci to run coccinelle scripts. This series is more of a PoC. The idea would be to run it once a day only on /master.
Patch 1 is here only to speedup travis testing. Patch 3 add a script which run each cocci script sequencially. If the script modified any file from the repo, changes are commited. If the script generated some output (i.e. using python), this output is logged in an empty commit. Spatch is run thru a debian-based Docker image. Patch 4 is the travis job: it calls the previous script. To respect travis time limit timeout, each script is limited to <10min. If any commit were generated, they are pushed to my gh-repo: https://github.com/philmd/qemu/compare/travis-cocci_v1...philmd:autogenerated-coccinelle-20170625-126 Build output (Ran for 23 min 7 sec): https://travis-ci.org/philmd/qemu/builds/246848085 Any idea is welcome :) Regards, Phil. Philippe Mathieu-Daudé (4): travis: simplify matrix coccinelle: ignore ASTs pre-parsed cached C files coccinelle: script to run them all travis: add job to run coccinelle scripts .gitignore | 2 + .travis.sshkey | Bin 0 -> 1296 bytes .travis.yml | 145 ++++++----------------------------------- scripts/check-cocci-scripts.sh | 47 +++++++++++++ 4 files changed, 69 insertions(+), 125 deletions(-) create mode 100644 .travis.sshkey create mode 100755 scripts/check-cocci-scripts.sh -- 2.13.1
