public inbox for gcc-testresults@sourceware.org help / color / mirror / Atom feed
From: builder@sourceware.org To: gcc-testresults@gcc.gnu.org Subject: ☠ Buildbot (Sourceware): gcc - failed compile (failure) (master) Date: Wed, 12 Jul 2023 13:38:46 +0000 [thread overview] Message-ID: <20230712133846.0C0693857717@sourceware.org> (raw) A new failure has been detected on builder gcc-debian-amd64 while building gcc. Full details are available at: https://builder.sourceware.org/buildbot/#builders/154/builds/5720 Build state: failed compile (failure) Revision: 275a2124e4928c88bd5469096356ba393b6aadfb Worker: bb1-1 Build Reason: (unknown) Blamelist: Roger Sayle <roger@nextmovesoftware.com> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/154/builds/5720/steps/1/logs/stdio - 2: rm -rf gcc-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/154/builds/5720/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/154/builds/5720/steps/3/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#builders/154/builds/5720/steps/3/logs/config_log - 4: make ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/154/builds/5720/steps/4/logs/stdio - warnings (4): https://builder.sourceware.org/buildbot/#builders/154/builds/5720/steps/4/logs/warnings__4_ A new failure has been detected on builder gcc-opensusetw-x86_64 while building gcc. Full details are available at: https://builder.sourceware.org/buildbot/#builders/155/builds/4804 Build state: failed compile (failure) Revision: 275a2124e4928c88bd5469096356ba393b6aadfb Worker: bb1-1 Build Reason: (unknown) Blamelist: Roger Sayle <roger@nextmovesoftware.com> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/155/builds/4804/steps/1/logs/stdio - 2: rm -rf gcc-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/155/builds/4804/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/155/builds/4804/steps/3/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#builders/155/builds/4804/steps/3/logs/config_log - 4: make ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/155/builds/4804/steps/4/logs/stdio - warnings (4): https://builder.sourceware.org/buildbot/#builders/155/builds/4804/steps/4/logs/warnings__4_ A new failure has been detected on builder gcc-fedora-x86_64 while building gcc. Full details are available at: https://builder.sourceware.org/buildbot/#builders/159/builds/5343 Build state: failed compile (failure) Revision: 275a2124e4928c88bd5469096356ba393b6aadfb Worker: bb1-1 Build Reason: (unknown) Blamelist: Roger Sayle <roger@nextmovesoftware.com> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/159/builds/5343/steps/1/logs/stdio - 2: rm -rf gcc-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/159/builds/5343/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/159/builds/5343/steps/3/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#builders/159/builds/5343/steps/3/logs/config_log - 4: make ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/159/builds/5343/steps/4/logs/stdio - warnings (13): https://builder.sourceware.org/buildbot/#builders/159/builds/5343/steps/4/logs/warnings__13_ A new failure has been detected on builder gcc-debian-i386 while building gcc. Full details are available at: https://builder.sourceware.org/buildbot/#builders/160/builds/5743 Build state: failed compile (failure) Revision: 275a2124e4928c88bd5469096356ba393b6aadfb Worker: debian-i386 Build Reason: (unknown) Blamelist: Roger Sayle <roger@nextmovesoftware.com> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/160/builds/5743/steps/1/logs/stdio - 2: rm -rf gcc-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/160/builds/5743/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/160/builds/5743/steps/3/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#builders/160/builds/5743/steps/3/logs/config_log - 4: make ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/160/builds/5743/steps/4/logs/stdio - warnings (4): https://builder.sourceware.org/buildbot/#builders/160/builds/5743/steps/4/logs/warnings__4_ A new failure has been detected on builder gcc-debian-testing-x86_64 while building gcc. Full details are available at: https://builder.sourceware.org/buildbot/#builders/161/builds/5696 Build state: failed compile (failure) Revision: 275a2124e4928c88bd5469096356ba393b6aadfb Worker: bb1-1 Build Reason: (unknown) Blamelist: Roger Sayle <roger@nextmovesoftware.com> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/161/builds/5696/steps/1/logs/stdio - 2: rm -rf gcc-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/161/builds/5696/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/161/builds/5696/steps/3/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#builders/161/builds/5696/steps/3/logs/config_log - 4: make ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/161/builds/5696/steps/4/logs/stdio - warnings (4): https://builder.sourceware.org/buildbot/#builders/161/builds/5696/steps/4/logs/warnings__4_ A new failure has been detected on builder gcc-opensuseleap-x86_64 while building gcc. Full details are available at: https://builder.sourceware.org/buildbot/#builders/162/builds/4845 Build state: failed compile (failure) Revision: 275a2124e4928c88bd5469096356ba393b6aadfb Worker: bb1-2 Build Reason: (unknown) Blamelist: Roger Sayle <roger@nextmovesoftware.com> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/162/builds/4845/steps/1/logs/stdio - 2: rm -rf gcc-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/162/builds/4845/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/162/builds/4845/steps/3/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#builders/162/builds/4845/steps/3/logs/config_log - 4: make ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/162/builds/4845/steps/4/logs/stdio - warnings (4): https://builder.sourceware.org/buildbot/#builders/162/builds/4845/steps/4/logs/warnings__4_ A new failure has been detected on builder gcc-fedora-mingw while building gcc. Full details are available at: https://builder.sourceware.org/buildbot/#builders/262/builds/1234 Build state: failed compile (failure) Revision: 275a2124e4928c88bd5469096356ba393b6aadfb Worker: bb1-2 Build Reason: (unknown) Blamelist: Roger Sayle <roger@nextmovesoftware.com> Steps: - 0: worker_preparation ( success ) - 1: git checkout ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/262/builds/1234/steps/1/logs/stdio - 2: rm -rf gcc-build ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/262/builds/1234/steps/2/logs/stdio - 3: configure ( success ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/262/builds/1234/steps/3/logs/stdio - config.log: https://builder.sourceware.org/buildbot/#builders/262/builds/1234/steps/3/logs/config_log - 4: make ( failure ) Logs: - stdio: https://builder.sourceware.org/buildbot/#builders/262/builds/1234/steps/4/logs/stdio - warnings (16): https://builder.sourceware.org/buildbot/#builders/262/builds/1234/steps/4/logs/warnings__16_
next reply other threads:[~2023-07-12 13:38 UTC|newest] Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-12 13:38 builder [this message] -- strict thread matches above, loose matches on Subject: below -- 2024-05-07 19:30 builder 2024-05-07 18:26 builder 2024-04-09 6:48 builder 2024-04-03 9:24 builder 2024-03-18 10:13 builder 2024-03-05 15:44 builder 2024-03-05 10:19 builder 2024-03-05 3:12 builder 2024-01-17 15:26 builder 2024-01-17 15:22 builder 2024-01-17 15:20 builder 2024-01-17 14:56 builder 2023-12-13 14:53 builder 2023-12-01 7:42 builder 2023-11-27 12:11 builder 2023-10-22 13:28 builder 2023-10-20 19:40 builder 2023-10-20 15:47 builder 2023-10-12 15:16 builder 2023-10-12 14:42 builder 2023-10-03 14:53 builder 2023-10-02 11:11 builder 2023-10-02 10:58 builder 2023-10-02 10:56 builder 2023-09-07 7:59 builder 2023-08-29 9:12 builder 2023-08-17 20:37 builder 2023-07-26 16:35 builder 2023-07-20 9:53 builder 2023-07-20 8:51 builder 2023-06-30 12:35 builder 2023-06-25 14:32 builder 2023-06-19 7:55 builder 2023-05-16 6:51 builder 2023-05-02 17:41 builder 2023-05-02 15:56 builder 2023-04-21 14:17 builder 2023-04-18 20:23 builder 2023-04-18 20:13 builder 2023-04-14 9:54 builder 2023-04-13 20:28 builder 2023-03-12 18:47 builder 2023-03-12 18:46 builder 2023-03-03 20:12 builder 2023-02-01 12:14 builder 2023-02-01 10:04 builder 2023-01-28 18:28 builder
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=20230712133846.0C0693857717@sourceware.org \ --to=builder@sourceware.org \ --cc=gcc-testresults@gcc.gnu.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).