From: "Matt Jolly" <kangie@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/chromium-tools:master commit in: /
Date: Mon, 10 Mar 2025 13:43:17 +0000 (UTC) [thread overview]
Message-ID: <1741614133.4aedd6f8789600d542d7498a7ebbff49353b3de4.kangie@gentoo> (raw)
commit: 4aedd6f8789600d542d7498a7ebbff49353b3de4
Author: Matt Jolly <kangie <AT> gentoo <DOT> org>
AuthorDate: Mon Mar 10 13:42:13 2025 +0000
Commit: Matt Jolly <kangie <AT> gentoo <DOT> org>
CommitDate: Mon Mar 10 13:42:13 2025 +0000
URL: https://gitweb.gentoo.org/proj/chromium-tools.git/commit/?id=4aedd6f8
Be more specific about where a fetch failed
We really shouldn't see one fail and the other succeed, but if it does
happen it's really nice to know where to start looking.
Signed-off-by: Matt Jolly <kangie <AT> gentoo.org>
get-chromium-toolchain-strings.py | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/get-chromium-toolchain-strings.py b/get-chromium-toolchain-strings.py
index d7c124d..ee8ca21 100755
--- a/get-chromium-toolchain-strings.py
+++ b/get-chromium-toolchain-strings.py
@@ -20,8 +20,8 @@ def get_testfonts(url) -> str:
str: The SHA256 of the testfonts, or None if not found.
"""
- # We're not properly parsing the DEPS file, but it's 'close enough' to JSON that
- # we can throw away the preamble and do some remediation to read the values in.
+ # We're not properly parsing the DEPS file (it's basically python), but it's 'close enough'
+ # to JSON that we can throw away the preamble and do some remediation to read the values in.
testfonts = None
response = requests.get(url)
@@ -145,7 +145,7 @@ def get_testfonts(url) -> str:
# Now we can get the testfonts SHA
return deps['src/third_party/test_fonts/test_fonts']['objects'][0]['object_name']
else:
- raise ValueError(f"Failed to get revision info. Status code: {response.status_code}")
+ raise ValueError(f"Failed to get testfont revision info. Status code: {response.status_code}")
return testfonts
@@ -181,7 +181,7 @@ def get_revision_info(url) -> str:
raise ValueError("Failed to extract revision and sub-revision")
return revision, sub_revision
else:
- raise ValueError(f"Failed to get revision info. Status code: {response.status_code}")
+ raise ValueError(f"Failed to get Clang and Rust revision info. Status code: {response.status_code}")
def main():
@@ -194,6 +194,7 @@ def main():
clang_revision, clang_sub_revision = get_revision_info(clang_url)
rust_revision, rust_sub_revision = get_revision_info(rust_url)
testfonts = get_testfonts(deps_url)
+ print(f"Chromium toolchain strings for: {version}")
if clang_revision and clang_sub_revision:
print(f"clang revision: {clang_revision}-{clang_sub_revision}")
else:
next reply other threads:[~2025-03-10 13:43 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 13:43 Matt Jolly [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-10 13:43 [gentoo-commits] proj/chromium-tools:master commit in: / Matt Jolly
2024-10-23 3:50 Matt Jolly
2024-10-23 3:50 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=1741614133.4aedd6f8789600d542d7498a7ebbff49353b3de4.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