public inbox for debugedit@sourceware.org
 help / color / mirror / Atom feed
From: builder@sourceware.org
To: debugedit@sourceware.org
Subject: ☺ Buildbot (Sourceware): debugedit - build successful (main)
Date: Wed, 22 May 2024 14:19:54 +0000	[thread overview]
Message-ID: <20240522141954.1C59F3858CD1@sourceware.org> (raw)

A restored build has been detected on builder debugedit-fedora-clang-x86_64 while building debugedit.

Full details are available at:
    https://builder.sourceware.org/buildbot/#/builders/304/builds/7

Build state: build successful
Revision: 630644cd7ce3ee068f5c105ad42adaa5a6f21287
Worker: bb1-1
Build Reason: (unknown)
Blamelist: Denys Vlasenko <dvlasenk@redhat.com>, Kalev Lember <klember@redhat.com>, Mark Wielaard <mark@klomp.org>, Nikita Popov <npopov@redhat.com>, Prarit Bhargava <prarit@redhat.com>, Violet Purcell <vimproved@inventati.org>, daifan <daifan@uniontech.com>

Steps:

- 0: worker_preparation ( success )

- 1: set package name ( success )

- 2: git checkout ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/2/logs/stdio

- 3: autoreconf ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/3/logs/stdio

- 4: configure ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/4/logs/stdio
        - config.log: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/4/logs/config_log

- 5: get version ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/5/logs/stdio
        - property changes: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/5/logs/property_changes

- 6: make ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/6/logs/stdio

- 7: make check ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/7/logs/stdio
        - testsuite.log: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/7/logs/testsuite_log

- 8: make distcheck ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/8/logs/stdio
        - testsuite.log: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/8/logs/testsuite_log

- 9: prep ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/9/logs/stdio

- 10: build bunsen.cpio.gz ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/10/logs/stdio

- 11: fetch bunsen.cpio.gz ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/11/logs/stdio

- 12: unpack bunsen.cpio.gz ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/12/logs/stdio

- 13: pass .bunsen.source.* ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/13/logs/stdio

- 14: upload to bunsen ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/14/logs/stdio

- 15: clean up ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/15/logs/stdio

- 16: make clean ( success )
    Logs:
        - stdio: https://builder.sourceware.org/buildbot/#/builders/304/builds/7/steps/16/logs/stdio


             reply	other threads:[~2024-05-22 14:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-22 14:19 builder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-27 16:10 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=20240522141954.1C59F3858CD1@sourceware.org \
    --to=builder@sourceware.org \
    --cc=debugedit@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).