public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Matt Jolly" <kangie@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/chromium-tools:master commit in: /
Date: Wed, 23 Oct 2024 03:50:08 +0000 (UTC)	[thread overview]
Message-ID: <1729655284.8325458dc3fc907432f50d0710909cba9144834e.kangie@gentoo> (raw)

commit:     8325458dc3fc907432f50d0710909cba9144834e
Author:     Matt Jolly <kangie <AT> gentoo <DOT> org>
AuthorDate: Wed Oct 23 03:47:39 2024 +0000
Commit:     Matt Jolly <kangie <AT> gentoo <DOT> org>
CommitDate: Wed Oct 23 03:48:04 2024 +0000
URL:        https://gitweb.gentoo.org/proj/chromium-tools.git/commit/?id=8325458d

Fail after a (configurable) timeout

If we make it more than say 5 minutes we've probably gotten past
the point where GN would complain and any failures are likely to
require actual dev effort.

Just die with an error at that point to save on electricity.

Signed-off-by: Matt Jolly <kangie <AT> gentoo.org>

 iterate-over-ebuild.sh | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/iterate-over-ebuild.sh b/iterate-over-ebuild.sh
index 9d0d479..7cd0f64 100755
--- a/iterate-over-ebuild.sh
+++ b/iterate-over-ebuild.sh
@@ -9,6 +9,7 @@ package="${1%.ebuild}"
 tmpfile=$(mktemp)
 iter=0
 added=()
+timeout_secs=300
 
 # Trap for Ctrl+C
 trap 'cleanup' INT
@@ -20,6 +21,7 @@ cleanup() {
 }
 
 while true; do
+  start_time=$(date +%s)
   libs=()
   echo "[$(date)]: Processing $package; iteration $((++iter))"
   echo "So far, we've added:"
@@ -54,6 +56,15 @@ while true; do
     rm "$tmpfile"
     break
   fi
+
+  end_time=$(date +%s)
+  elapsed_time=$((end_time - start_time))
+  if [ $elapsed_time -gt $timeout_secs ]; then
+    echo "[$(date)]: Ebuild execution took longer than the timeout. This is likely a build failure that requires patching. Exiting."
+    echo "$tmpfile" for this iteration\'s logs.
+    exit 1
+  fi
+
   # Start with a clean slate for the next iteration
   rm "$tmpfile"
 done


             reply	other threads:[~2024-10-23  3:50 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-23  3:50 Matt Jolly [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-23  3:50 [gentoo-commits] proj/chromium-tools:master commit in: / Matt Jolly
2024-10-10 21:52 Matt Jolly
2024-10-10 10:03 Matt Jolly
2024-09-27  0:52 Matt Jolly
2024-09-27  0:52 Matt Jolly
2024-09-27  0:52 Matt Jolly
2024-09-26  7:25 Matt Jolly
2024-09-26  5:29 Matt Jolly
2024-09-26  5:21 Matt Jolly
2024-09-26  3:03 Matt Jolly
2024-09-26  2:39 Matt Jolly
2024-09-26  2:36 Matt Jolly
2024-08-30  3:39 Matt Jolly
2024-06-01  7:22 Matt Jolly
2024-05-31 23:02 Matt Jolly
2024-03-28  2:39 Matt Jolly
2024-03-20 21:45 Matt Jolly
2024-03-20 21:45 Matt Jolly
2024-03-20 21:45 Matt Jolly
2024-03-20 21:45 Matt Jolly
2023-02-05 15:09 Stephan Hartmann
2022-09-01 19:33 Mike Gilbert
2022-09-01 19:24 Mike Gilbert
2022-05-06  9:55 Stephan Hartmann
2022-05-03 16:54 Mike Gilbert
2022-05-03 16:54 Mike Gilbert
2022-02-11 17:16 Stephan Hartmann
2022-02-05 16:29 Stephan Hartmann
2022-01-31 20:20 Stephan Hartmann
2020-11-21 19:34 Stephan Hartmann
2020-10-26 17:48 Mike Gilbert
2016-09-15 16:15 Mike Gilbert
2016-09-15 16:11 Mike Gilbert
2015-08-13 20:53 Mike Gilbert
2012-07-31 23:27 Mike Gilbert
2012-07-31 20:39 Mike Gilbert
2012-06-18  7:38 Paweł Hajdan
2011-10-25 16:36 Paweł Hajdan

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=1729655284.8325458dc3fc907432f50d0710909cba9144834e.kangie@gentoo \
    --to=kangie@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