all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: 44745@debbugs.gnu.org
Subject: bug#44745: tests/lint.scm fails building guix with guile-2.2
Date: Thu, 19 Nov 2020 16:35:42 -0800	[thread overview]
Message-ID: <87y2iwvp9d.fsf@yucca> (raw)

[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]

I'm exploring building with guile 2.2 because guile-gnutls built with
guile 3.0 is only available in experimental, and even there, missing for
arm64.

From tests/lint.log:

test-name: archival: missing content
location: /build/guix-EdK9LP/guix-1.2.0~rc2/tests/lint.scm:921
source:
+ (test-assert
+   "archival: missing content"
+   (let* ((origin
+            (origin
+              (method url-fetch)
+              (uri "http://example.org/foo.tgz")
+              (sha256 (make-bytevector 32))))
+          (warnings
+            (with-http-server
+              '((404 "Not archived."))
+              (parameterize
+                ((%swh-base-url (%local-url)))
+                (check-archival
+                  (dummy-package "x" (source origin)))))))
+     (warning-contains? "not archived" warnings)))
actual-value: #f
actual-error:
+ (keyword-argument-error
+   #<procedure http-request (uri #:key body port method version keep-alive? headers decode-body? streaming? request)>
+   "Unrecognized keyword"
+   ()
+   (#:verify-certificate?))
result: FAIL


I haven't tried reproducing this without the Debian patches applied
which liberally sprinkle the test suites with:

  (unless (network-reachable?  (test-skip 1))

... but if you can spot a likely issue, I'd be happy to test it. :)


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

             reply	other threads:[~2020-11-20  0:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20  0:35 Vagrant Cascadian [this message]
2020-11-20  9:32 ` bug#44745: tests/lint.scm fails building guix with guile-2.2 zimoun
2020-11-20 11:47   ` Ludovic Courtès

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=87y2iwvp9d.fsf@yucca \
    --to=vagrant@debian.org \
    --cc=44745@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.