From: "Diego Elio Pettenò" <flameeyes@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/flameeyes-tinderbox:master commit in: /
Date: Sat, 16 Jun 2012 14:39:04 +0000 (UTC) [thread overview]
Message-ID: <1339857537.c1bcfdbf405f07d53e23e81875bfdc804d93337d.flameeyes@gentoo> (raw)
commit: c1bcfdbf405f07d53e23e81875bfdc804d93337d
Author: Diego Elio Pettenò <flameeyes <AT> flameeyes <DOT> eu>
AuthorDate: Sat Jun 16 14:38:57 2012 +0000
Commit: Diego Elio Pettenò <flameeyes <AT> gentoo <DOT> org>
CommitDate: Sat Jun 16 14:38:57 2012 +0000
URL: http://git.overlays.gentoo.org/gitweb/?p=proj/flameeyes-tinderbox.git;a=commit;h=c1bcfdbf
If we have an automake failure, inline the log file, this way we don't have to hunt for it.
---
bashrc | 5 +++++
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/bashrc b/bashrc
index f84bb64..6f1ed40 100755
--- a/bashrc
+++ b/bashrc
@@ -62,6 +62,11 @@ tinderbox_failed() {
dent_me "${CATEGORY}/${PF} merge #failed$(tinderbox_stats)"
SANDBOX_ON=0 sed -i -e "\$a =${CATEGORY}/${PF}" /etc/portage/package.mask/currentrun
+ # check if this is an automake failure and if so, get the whole log inlined
+ if grep -f -q "/temp/automake.out" "${PORTAGE_LOG_FILE}"; then
+ cat "${T}"/automake.log
+ fi
+
tinderbox_send_log
}
next reply other threads:[~2012-06-16 14:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-16 14:39 Diego Elio Pettenò [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-05 13:42 [gentoo-commits] proj/flameeyes-tinderbox:master commit in: / Diego Elio Pettenò
2013-02-19 20:39 Diego Elio Pettenò
2013-01-26 14:49 Diego Elio Pettenò
2013-01-26 1:15 Diego Elio Pettenò
2013-01-26 0:23 Diego Elio Pettenò
2013-01-26 0:23 Diego Elio Pettenò
2013-01-26 0:23 Diego Elio Pettenò
2012-11-01 18:51 Diego Elio Pettenò
2012-11-01 16:54 Diego Elio Pettenò
2012-07-15 10:31 Diego Elio Pettenò
2012-07-15 10:28 Diego Elio Pettenò
2012-06-22 19:49 Diego Elio Pettenò
2012-06-22 19:49 Diego Elio Pettenò
2012-06-22 19:46 Diego Elio Pettenò
2012-06-21 10:48 Diego Elio Pettenò
2012-06-19 18:59 Diego Elio Pettenò
2012-06-16 14:57 Diego Elio Pettenò
2012-06-16 14:51 Diego Elio Pettenò
2012-06-16 14:48 Diego Elio Pettenò
2012-06-16 14:45 Diego Elio Pettenò
2012-06-16 14:39 Diego Elio Pettenò
2012-06-15 15:09 Diego Elio Pettenò
2012-06-15 15:09 Diego Elio Pettenò
2012-06-15 15:09 Diego Elio Pettenò
2012-05-18 16:03 Diego Elio Pettenò
2012-05-18 15:56 Diego Elio Pettenò
2012-05-18 15:56 Diego Elio Pettenò
2012-05-18 15:56 Diego Elio Pettenò
2012-05-18 4:32 Diego Elio Pettenò
2012-05-18 4:07 Diego Elio Pettenò
2012-05-18 4:07 Diego Elio Pettenò
2011-08-07 12:23 Diego Elio Pettenò
2011-05-28 9:09 Diego Elio Pettenò
2011-05-03 14:54 Diego Elio Pettenò
2011-05-03 14:54 Diego Elio Pettenò
2011-04-13 12:50 Diego Elio Pettenò
2011-03-22 17:09 Jeremy Olexa
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=1339857537.c1bcfdbf405f07d53e23e81875bfdc804d93337d.flameeyes@gentoo \
--to=flameeyes@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