public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: mengqinggang <mengqinggang@loongson.cn>
To: builder@sourceware.org
Cc: binutils@sourceware.org
Subject: Re: ☠ Buildbot (Sourceware): binutils-gdb - failed test (failure) (master)
Date: Tue, 6 Jun 2023 15:02:16 +0800	[thread overview]
Message-ID: <26eed2de-adda-a2e6-6960-6c1172ab84e2@loongson.cn> (raw)
In-Reply-To: <20230530134911.4B9523858D28@sourceware.org>

This is the 5/6 commit of the LoongArch linker relaxation patch, the test of
last commit is OK.


在 2023/5/30 下午9:49, builder@sourceware.org 写道:
> A new failure has been detected on builder binutils-gentoo-sparc while building binutils-gdb.
>
> Full details are available at:
>      https://builder.sourceware.org/buildbot/#builders/228/builds/778
>
> Build state: failed test (failure)
> Revision: 56576f4a722b7398d35802ecf7d4185c27d6d69b
> Worker: gentoo-sparc
> Build Reason: (unknown)
> Blamelist: mengqinggang <mengqinggang@loongson.cn>
>
> Steps:
>
> - 0: worker_preparation ( success )
>
> - 1: git checkout ( success )
>      Logs:
>          - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/1/logs/stdio
>
> - 2: rm -rf binutils-build ( success )
>      Logs:
>          - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/2/logs/stdio
>
> - 3: configure ( success )
>      Logs:
>          - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/3/logs/stdio
>          - config.log: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/3/logs/config_log
>
> - 4: make ( warnings )
>      Logs:
>          - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/4/logs/stdio
>          - warnings (21): https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/4/logs/warnings__21_
>
> - 5: make check ( failure )
>      Logs:
>          - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/5/logs/stdio
>          - ld.sum: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/5/logs/ld_sum
>          - ld.log: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/5/logs/ld_log
>          - gas.sum: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/5/logs/gas_sum
>          - gas.log: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/5/logs/gas_log
>          - binutils.sum: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/5/logs/binutils_sum
>          - binutils.log: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/5/logs/binutils_log
>          - libsframe.sum: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/5/logs/libsframe_sum
>          - libsframe.log: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/5/logs/libsframe_log
>          - libctf.sum: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/5/logs/libctf_sum
>          - libctf.log: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/5/logs/libctf_log
>          - warnings (12): https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/5/logs/warnings__12_
>
> - 6: prep ( success )
>      Logs:
>          - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/6/logs/stdio
>
> - 7: build bunsen.cpio.gz ( success )
>      Logs:
>          - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/7/logs/stdio
>
> - 8: fetch bunsen.cpio.gz ( success )
>      Logs:
>          - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/8/logs/stdio
>
> - 9: unpack bunsen.cpio.gz ( success )
>      Logs:
>          - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/9/logs/stdio
>
> - 10: pass .bunsen.source.gitname ( success )
>      Logs:
>          - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/10/logs/stdio
>
> - 11: pass .bunsen.source.gitdescribe ( success )
>      Logs:
>          - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/11/logs/stdio
>
> - 12: pass .bunsen.source.gitbranch ( success )
>      Logs:
>          - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/12/logs/stdio
>
> - 13: pass .bunsen.source.gitrepo ( success )
>      Logs:
>          - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/13/logs/stdio
>
> - 14: upload to bunsen ( success )
>      Logs:
>          - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/14/logs/stdio
>
> - 15: clean up ( success )
>      Logs:
>          - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/15/logs/stdio
>
> - 16: rm -rf binutils-build_1 ( success )
>      Logs:
>          - stdio: https://builder.sourceware.org/buildbot/#builders/228/builds/778/steps/16/logs/stdio


       reply	other threads:[~2023-06-06  7:02 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230530134911.4B9523858D28@sourceware.org>
2023-06-06  7:02 ` mengqinggang [this message]
2024-04-27  1:03 builder
  -- strict thread matches above, loose matches on Subject: below --
2024-04-20  1:18 builder
2024-04-19 22:16 builder
2024-04-19  3:32 builder
2024-04-12  6:06 builder
2024-04-03 20:45 builder
2024-02-27  5:20 builder
2024-02-27  5:03 builder
2024-01-26 12:15 builder
2024-01-10 12:28 builder
2023-12-29 12:19 builder
2023-12-29  4:32 builder
2023-12-29  3:57 builder
2023-12-29  3:47 builder
2023-12-13  6:51 builder
2023-10-13  0:42 builder
2023-10-16  6:48 ` Jan Beulich
2023-10-19 11:23   ` Mark Wielaard
2023-10-19 11:48     ` Jan Beulich
2023-10-10 12:24 builder
2023-10-09 17:33 builder
2023-10-08  3:07 builder
2023-10-06  0:36 builder
2023-10-05 14:02 builder
2023-10-03  0:40 builder
2023-09-29 15:32 builder
2023-09-29  0:36 builder
2023-09-27 17:01 builder
2023-09-27  9:53 builder
2023-09-26 14:41 builder
2023-09-18  8:14 builder
2023-09-18  9:04 ` Sam James
     [not found] <20230914084342.10CE138555A9@sourceware.org>
2023-09-14  8:58 ` Jan Beulich
2023-09-14 18:33   ` Mark Wielaard
2023-09-14  8:43 builder
     [not found] <20230818215458.6F9403858D32@sourceware.org>
2023-08-21  6:25 ` Jan Beulich
2023-08-21  8:57   ` Mark Wielaard
2023-08-18 21:54 builder
2023-08-01 14:33 builder
2023-07-17 20:31 builder
2023-07-17 16:50 builder
2023-07-17  8:19 builder
2023-07-07 10:47 builder
     [not found] <20230704171241.36F7E3858C31@sourceware.org>
2023-07-05  7:19 ` Jan Beulich
2023-07-05  9:39   ` Mark Wielaard
2023-07-04 17:12 builder
2023-06-30  5:04 builder
2023-06-29 20:25 builder
2023-06-27 23:59 builder
2023-06-14  5:36 builder
2023-06-11  0:39 builder
2023-06-07 22:58 builder
2023-06-08  0:08 ` Indu Bhagat
2023-06-08  0:25   ` Mark Wielaard
2023-06-05 16:17 builder
2023-06-05  4:39 builder
2023-05-30 13:49 builder
2023-05-30  5:12 builder
2023-05-19  7:36 builder
2023-05-07  0:40 builder
2023-05-03 15:12 builder
2023-05-03  6:48 builder
2023-03-07 15:07 builder
2023-03-05  0:19 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=26eed2de-adda-a2e6-6960-6c1172ab84e2@loongson.cn \
    --to=mengqinggang@loongson.cn \
    --cc=binutils@sourceware.org \
    --cc=builder@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).