From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/portage-utils:master commit in: travis/
Date: Fri, 3 Jan 2020 15:00:49 +0000 (UTC) [thread overview]
Message-ID: <1578063623.5743951c803b852e3ff48535b1ba5cfe89a2dd8a.grobian@gentoo> (raw)
commit: 5743951c803b852e3ff48535b1ba5cfe89a2dd8a
Author: Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Fri Jan 3 15:00:23 2020 +0000
Commit: Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Fri Jan 3 15:00:23 2020 +0000
URL: https://gitweb.gentoo.org/proj/portage-utils.git/commit/?id=5743951c
travis: drop old coverity call
Signed-off-by: Fabian Groffen <grobian <AT> gentoo.org>
travis/main.sh | 3 ---
1 file changed, 3 deletions(-)
diff --git a/travis/main.sh b/travis/main.sh
index 52a3c90..5cbd480 100755
--- a/travis/main.sh
+++ b/travis/main.sh
@@ -21,9 +21,6 @@ do_run() {
if [[ ${CC} == coverity ]] ; then
[[ -n ${COVERITY_SCAN_TOKEN} ]] || exit 0; # don't fail on this for PRs
- # Do scans last as they like to dirty the tree and some tests
- # expect a clean tree (like code style checks).
- v --fold="coverity_scan" coverity_scan
# ensure we end up with an existing compiler
export CC=gcc
v ./configure ${DEFARGS} --enable-qmanifest --enable-qtegrity
next reply other threads:[~2020-01-03 15:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 15:00 Fabian Groffen [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-04 10:47 [gentoo-commits] proj/portage-utils:master commit in: travis/ Fabian Groffen
2020-01-03 15:07 Fabian Groffen
2020-01-03 14:55 Fabian Groffen
2020-01-02 15:24 Fabian Groffen
2019-07-18 17:51 Fabian Groffen
2019-07-18 17:47 Fabian Groffen
2019-05-21 14:55 Fabian Groffen
2019-05-21 14:52 Fabian Groffen
2019-05-21 14:32 Fabian Groffen
2019-03-19 20:32 Fabian Groffen
2018-03-30 7:50 Fabian Groffen
2018-03-30 7:50 Fabian Groffen
2018-03-30 7:50 Fabian Groffen
2016-06-24 9:09 Mike Frysinger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1578063623.5743951c803b852e3ff48535b1ba5cfe89a2dd8a.grobian@gentoo \
--to=grobian@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox