public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alfredo Tupone <tupone@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] dune.eclass changes for test not raising warn to error
Date: Mon, 10 Jan 2022 15:52:37 +0100	[thread overview]
Message-ID: <20220110155237.4e2cb7ed@alfredo-i5> (raw)

I'm changing dune eclass src_test so that the profile is release
Previously only src_compile used that profile
profile release does not promote warning to error.

Tupone

From 4d3ed43d94a8d6ba4fb6faa0423b090fadc129c0 Mon Sep 17 00:00:00 2001
From: Alfredo Tupone <tupone@gentoo.org>
Date: Mon, 10 Jan 2022 14:38:01 +0100
Subject: [PATCH] eclass/dune.eclass: src_test do not change warn to err

Closes: https://bugs.gentoo.org/822876

Signed-off-by: Alfredo Tupone <tupone@gentoo.org>
---
 eclass/dune.eclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/eclass/dune.eclass b/eclass/dune.eclass
index 4653db3ae79..5b0418152da 100644
--- a/eclass/dune.eclass
+++ b/eclass/dune.eclass
--- a/eclass/dune.eclass
+++ b/eclass/dune.eclass
@@ -38,31 +38,31 @@ case ${EAPI:-0} in
                ;;
        *)
                BDEPEND="dev-ml/dune dev-lang/ocaml"
                DEPEND="${RDEPEND}"
                ;;
 esac

 dune_src_compile() {
        ebegin "Building"
        dune build @install --profile release
        eend $? || die
 }

 dune_src_test() {
        ebegin "Testing"
-       dune runtest
+       dune runtest --profile release
        eend $? || die
 }

 # @FUNCTION: dune-install
 # @USAGE: <list of packages>
 # @DESCRIPTION:
 # Installs the dune packages given as arguments. For each "${pkg}"
 element in # that list, "${pkg}.install" must be readable from
 "${PWD}/_build/default" #
 # Example use:
 # @CODE
 # dune-install menhir menhirLib menhirSdk
 # @CODE
 dune-install() {
        local -a pkgs=( "${@}" )


                 reply	other threads:[~2022-01-10 14:52 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=20220110155237.4e2cb7ed@alfredo-i5 \
    --to=tupone@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