From: Adam Maleszka via Bug reports for GNU Guix <bug-guix@gnu.org>
To: 53823@debbugs.gnu.org
Subject: bug#53823: Build fails for cpplint@1.4.5
Date: Sun, 06 Feb 2022 14:47:38 +0100 [thread overview]
Message-ID: <87h79c6md6.fsf@aol.com> (raw)
In-Reply-To: 87h79c6md6.fsf.ref@aol.com
[-- Attachment #1.1: Type: text/plain, Size: 3249 bytes --]
Since I moved to Guix distribution on the 1st of January (btw, good
move), compiling cpplint@1.4.5 has always failed. More specifically,
errors are triggered by pytest during the check phase.
Some of relevant lines extracted from the log:
E AssertionError: ('Lists differ: [\'src/chrome_content_renderer_client.cc:113[1733 chars], \'\'] != [\'pytest-cov: Failed to setup subprocess co[2001 chars], \'\']\n\nFirst differing element 0:\n\'src/chrome_content_renderer_client.cc:113[69 chars] [4]\'\n\'pytest-cov: Failed to setup subprocess co[219 chars]\\\'")\'\n\nSecond list contains 1 additional elements.\nFirst extra element 14:\n\'\'\n\nDiff is 2313 characters long. Set self.maxDiff to None to see it.', 'Failed check in /tmp/guix-build-cpplint-1.4.5.drv-0/tmpj8jqkp85/./samples/chromium-sample for command: /gnu/store/j3cx0yaqdpw0mxizp5bayx93pya44dhn-python-wrapper-3.9.9/bin/python /tmp/guix-build-cpplint-1.4.5.drv-0/source/cpplint.py --repository /tmp/guix-build-cpplint-1.4.5.drv-0/tmpj8jqkp85 src/*')
E AssertionError: ('Lists differ: [\'src/libvlc.c:41: Found C system header a[51270 chars], \'\'] != [\'pytest-cov: Failed to setup subprocess co[51538 chars], \'\']\n\nFirst differing element 0:\n\'src/libvlc.c:41: Found C system header a[91 chars] [4]\'\n\'pytest-cov: Failed to setup subprocess co[219 chars]\\\'")\'\n\nSecond list contains 1 additional elements.\nFirst extra element 602:\n\'\'\n\nDiff is 56098 characters long. Set self.maxDiff to None to see it.', 'Failed check in /tmp/guix-build-cpplint-1.4.5.drv-0/tmpj8jqkp85/./samples/vlc-sample for command: /gnu/store/j3cx0yaqdpw0mxizp5bayx93pya44dhn-python-wrapper-3.9.9/bin/python /tmp/guix-build-cpplint-1.4.5.drv-0/source/cpplint.py --repository /tmp/guix-build-cpplint-1.4.5.drv-0/tmpj8jqkp85 src/*')
E AssertionError: ('Lists differ: [\'src/pptable.cpp:0: No copyright message [56843 chars], \'\'] != [\'pytest-cov: Failed to setup subprocess co[57111 chars], \'\']\n\nFirst differing element 0:\n\'src/pptable.cpp:0: No copyright message [87 chars] [5]\'\n\'pytest-cov: Failed to setup subprocess co[219 chars]\\\'")\'\n\nSecond list contains 1 additional elements.\nFirst extra element 681:\n\'\'\n\nDiff is 60050 characters long. Set self.maxDiff to None to see it.', 'Failed check in /tmp/guix-build-cpplint-1.4.5.drv-0/tmpzqrghr8e/./samples/codelite-sample for command: /gnu/store/j3cx0yaqdpw0mxizp5bayx93pya44dhn-python-wrapper-3.9.9/bin/python /tmp/guix-build-cpplint-1.4.5.drv-0/source/cpplint.py src/*')
-
E AssertionError: '' != 'pytest-cov: Failed to setup subprocess co[221 chars]")\n'
E + pytest-cov: Failed to setup subprocess coverage. Environ: {'COV_CORE_SOURCE': 'cpplint', 'COV_CORE_CONFIG': ':', 'COV_CORE_DATAFILE': '/tmp/guix-build-cpplint-1.4.5.drv-0/source/.coverage'} Exception: ModuleNotFoundError("No module named 'coverage'")
A common message for all of these errors is that pytest-cov failed to
setup sub-process, probably, due to the lack of the 'coverate' module
(even though the python-pytest-cov package is listed in native-inputs).
I have tested this on several machines (all of them x86_64-linux) and on
a fresh system and the errors appear the same everywhere. I've attached
the complete log to this post.
[-- Attachment #1.2: complete build log --]
[-- Type: application/octet-stream, Size: 5808 bytes --]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next parent reply other threads:[~2022-02-06 15:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87h79c6md6.fsf.ref@aol.com>
2022-02-06 13:47 ` Adam Maleszka via Bug reports for GNU Guix [this message]
2022-02-06 17:41 ` bug#53823: Build fails for cpplint@1.4.5 Adam Maleszka via Bug reports for GNU Guix
2022-02-09 23:28 ` Marius Bakke
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=87h79c6md6.fsf@aol.com \
--to=bug-guix@gnu.org \
--cc=53823@debbugs.gnu.org \
--cc=adam_maleszka@aol.com \
/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).