Re: [PATCH v4 5/8] status: print per-file porcelain v2 status data
- From
Stefan Beller <sbeller@google.com>
- Date
- Aug 5, 2016, 21:43 UTC
- Message-ID
- <CAGZ79kb2aO80csCfV=QbH8D1spdNLdkTCSPriZ8W9nSy6T5QAg@mail.gmail.com>
- In-Reply-To
- <20160805211434.54mtaw2cty4gaxsr@sigill.intra.peff.net>
On Fri, Aug 5, 2016 at 2:14 PM, Jeff King <peff@peff.net> wrote:
Show 6 quoted lines
> > Unfortunately it is hard for me to test a one-off, as running it locally > is a complete pain. Stefan set it up long ago to pull "pu" and email out > the results from their central servers, so I just scan those emails for > things that look like real issues. >
I am glad this provides actual value. :) (I tend to ignore the emails nowadays as I am focusing on other stuff. I'll get back to down the number issues eventually, I promise ;)
Running one offs is "relatively" easy. I did that for other projects once upon a time. Here is my script to run the build:
#!/bin/bash
. .profile cd coverity/git
git clean -dfx
git fetch --all
git checkout origin/pu
git am ../git_strbuf_stop_out_of_bounds_coverity.patch descrip="scripted upload scanning github.com/gitster/git pu"
name=$(git describe) cov-build --dir cov-int make
tar czvf git-${name}.tgz cov-int curl --form project=git \
--form token=<sekret> \
--form email=<my mail address> \
--form file=@git-${name}.tgz \
--form version="${name}" \
--form description="${descrip}" \
https://scan.coverity.com/builds?project=gitgit clean -dfx
You can get a token if you look around, e.g. at https://scan.coverity.com/projects/git/builds/new and the email address is the one you signed up with coverity (or the one from Github, if signed up via Github)
I am currently applying one patch on top of pu, (id: 1434536209-31350-1-git-send-email-pclouds@gmail.com I can resend if you don't have that.)
I am running this script as a cron job, but it can be run "as is" as well, you'd just need to toss in the one-off test patch.
Thanks, Stefan