unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Xinglu Chen <public@yoctocell.xyz>
To: 49183@debbugs.gnu.org
Subject: [bug#49183] [PATCH] gnu: ocaml-dose3: Fix tests.
Date: Wed, 23 Jun 2021 10:52:38 +0200	[thread overview]
Message-ID: <4598abb91f7f610e062f34931fe988d04b5d43c1.1624438202.git.public@yoctocell.xyz> (raw)

* gnu/packages/ocaml.scm (ocaml-dose3)[arguments]<#:phases>: Add phase to
patch tests script.
---
The test script was failing to run without this, which also caused
emacs-tuareg to not build.

No idea why one would use Python to test OCaml code...

 gnu/packages/ocaml.scm | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/gnu/packages/ocaml.scm b/gnu/packages/ocaml.scm
index dd30f4cc97..1262c0e303 100644
--- a/gnu/packages/ocaml.scm
+++ b/gnu/packages/ocaml.scm
@@ -647,7 +647,14 @@ underlying solvers like Cplex, Gurobi, Lpsolver, Glpk, CbC, SCIP or WBO.")
        #:make-flags
        (list (string-append "LIBDIR="
                             (assoc-ref %outputs "out")
-                            "/lib/ocaml/site-lib"))))
+                            "/lib/ocaml/site-lib"))
+       #:phases
+       (modify-phases %standard-phases
+         (add-after 'unpack 'fix-test-script
+           (lambda _
+             (substitute* "applications/dose-tests.py"
+               (("warning\\(")
+                "from warnings import warn\nwarn(")))))))
     (propagated-inputs
       `(("ocaml-graph" ,ocaml-graph)
         ("ocaml-cudf" ,ocaml-cudf)

base-commit: 4605ea1a780ff5889b7273d27a255294d7a08327
-- 
2.32.0






             reply	other threads:[~2021-06-23  8:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-23  8:52 Xinglu Chen [this message]
2021-06-23 11:09 ` [bug#49183] [PATCH] gnu: ocaml-dose3: Fix tests pukkamustard
2021-06-23 12:45   ` bug#49183: " Julien Lepiller

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4598abb91f7f610e062f34931fe988d04b5d43c1.1624438202.git.public@yoctocell.xyz \
    --to=public@yoctocell.xyz \
    --cc=49183@debbugs.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: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).