Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#55327 - [you-get] build fails during check()

Attached to Project: Community Packages
Opened by Erich Eckner (deepthought) - Tuesday, 29 August 2017, 07:06 GMT
Last edited by Doug Newgard (Scimmia) - Thursday, 31 August 2017, 13:13 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

The package build fails during check() with:

error: Test failed: <unittest.runner.TextTestResult run=6 errors=1 failures=0>
==> ERROR: A failure occurred in check().
Aborting...

Additional info:
* package version(s)
you-get-0.4.803-1 (git revision f4752bb376aa85e2518cc2db771d2afa3664155d)
* config and/or log files etc.
full log is attached

Steps to reproduce:
Try to build it in a clean chroot via staging-x86_64-build.
   log (12.5 KiB)
This task depends upon

Closed by  Doug Newgard (Scimmia)
Thursday, 31 August 2017, 13:13 GMT
Reason for closing:  Not a bug
Comment by Doug Newgard (Scimmia) - Tuesday, 29 August 2017, 15:01 GMT
Builds fine for me, against both extra and staging
Comment by Erich Eckner (deepthought) - Tuesday, 29 August 2017, 17:14 GMT
I just tried to build on a different box, and there's the same error. Let me double check that it's not due to an unnoticed difference in devtools vs. devtools32 (the x86_64 version should be identical, though)
   log (15.1 KiB)
Comment by Erich Eckner (deepthought) - Tuesday, 29 August 2017, 17:19 GMT
ok, it fails with the official devtools in the same way. Let me know if I can provide any other hints - the only thing I can think of currently is, that the machine has no ipv6.
Comment by Doug Newgard (Scimmia) - Wednesday, 30 August 2017, 04:45 GMT
I don't have ipv6 on the machine I tested with, either. Since the issue is a connection timeout and it works for me, it would seem to be a problem with your connection.

I think the site in question is http://m.miaopai.com/show/channel/vlvreCo4OZiNdk5Jn1WvdopmAvdIJwi8 , which opens just fine for me.
Comment by Erich Eckner (deepthought) - Wednesday, 30 August 2017, 05:00 GMT
I just tried on a different machine in a different network in a different country, but it still fails.
Could this be something country-specific? (all machines so far reside in europe: germany and france)
   log (9.7 KiB)
Comment by Doug Newgard (Scimmia) - Wednesday, 30 August 2017, 05:11 GMT
Can you connect to http://www.miaopai.com/ at all?
Comment by Erich Eckner (deepthought) - Wednesday, 30 August 2017, 06:53 GMT
yes, from all three boxes
Comment by Doug Newgard (Scimmia) - Wednesday, 30 August 2017, 14:53 GMT
So why can't the tests? The remote box gives a 404, and the original times out, you'll need to figure out why.
Comment by Erich Eckner (deepthought) - Thursday, 31 August 2017, 07:17 GMT
Seem to have been a temporary problem. Sry for the noise. This issue can be closed.

Loading...