public inbox for buildbot@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: buildbot@sourceware.org
Cc: Mark Wielaard <mark@klomp.org>
Subject: [PATCH] Add make_dist_step to valgrind_snapshots_trunk_factory
Date: Mon, 10 Apr 2023 01:51:24 +0200	[thread overview]
Message-ID: <20230409235124.3009537-1-mark@klomp.org> (raw)

Otherwise we cannot put the tar.bz2 under the output.
---
 builder/master.cfg | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/builder/master.cfg b/builder/master.cfg
index 061451d..d78e4a4 100644
--- a/builder/master.cfg
+++ b/builder/master.cfg
@@ -1083,6 +1083,9 @@ make_check_testsuite_step = steps.Test(
             util.Interpolate('-j%(prop:ncpus)s')]),
         name="make check", haltOnFailure=False, flunkOnFailure=True,
         logfiles={"testsuite.log": "tests/testsuite.log"})
+make_dist_step = steps.Test(
+        command=["make", "dist"],
+        name="make dist")
 make_distcheck_step = steps.Test(
         command=addOutputSync.withArgs(["make", "distcheck",
             util.Interpolate('-j%(prop:ncpus)s')]),
@@ -3998,6 +4001,7 @@ valgrind_snapshots_trunk_factory = util.BuildFactory()
 valgrind_snapshots_trunk_factory.addStep(valgrind_git_step)
 valgrind_snapshots_trunk_factory.addStep(valgrind_autogen_step)
 valgrind_snapshots_trunk_factory.addStep(configure_step)
+valgrind_snapshots_trunk_factory.addStep(make_dist_step)
 valgrind_snapshots_trunk_factory.addStep(valgrind_make_all_docs_step)
 valgrind_snapshots_trunk_factory.addStep(valgrind_make_download_docs_step)
 valgrind_snapshots_trunk_factory.addStep(wait_snapshots_output_ready_step)
-- 
2.31.1


                 reply	other threads:[~2023-04-09 23:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230409235124.3009537-1-mark@klomp.org \
    --to=mark@klomp.org \
    --cc=buildbot@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).