Hide Forgot
Created attachment 835230 [details] build.log Description of problem: Making check in tests make[1]: Entering directory `/builddir/build/BUILD/vagent2-2.1/tests' make check-TESTS make[2]: Entering directory `/builddir/build/BUILD/vagent2-2.1/tests' make[3]: Entering directory `/builddir/build/BUILD/vagent2-2.1/tests' FAIL: badvarnishd.sh FAIL: json.sh FAIL: log.sh FAIL: status.sh FAIL: vcl.sh FAIL: echo.sh make[4]: Entering directory `/builddir/build/BUILD/vagent2-2.1/tests' make[4]: Nothing to be done for `all'. make[4]: Leaving directory `/builddir/build/BUILD/vagent2-2.1/tests' ============================================================================ Testsuite summary for varnish-agent 2.1 ============================================================================ # TOTAL: 6 # PASS: 0 # SKIP: 0 # XFAIL: 0 # FAIL: 6 # XPASS: 0 # ERROR: 0 ============================================================================ See tests/test-suite.log ============================================================================ make[3]: Leaving directory `/builddir/build/BUILD/vagent2-2.1/tests' make[3]: *** [test-suite.log] Error 1 Version-Release number of selected component (if applicable): varnish-agent-2.1-5.fc20 How reproducible: always Steps to Reproduce: 1. ppc-koji build --scratch f20 varnish-agent-2.1-5.fc20.src.rpm 2. 3. Actual results: http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=1567582
Created attachment 835231 [details] root.log
In suspect the stub http server (see empty_response_backend.py) takes more than 10 seconds to start. I'll try some koji builds on PPC with a dump of the test log files in the build's output.
I've started a scratch build on rawhide, it takes *ages* to pass or fail the very first test suite... At least we'll see the test logs in build.log once it's done. http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=1571315 btw, just noticed this bug's id is a palindrome :)
Wrong assumption, it's the client side that fails with "read timeout" messages. http://ppc.koji.fedoraproject.org/kojifiles/work/tasks/1316/1571316/build.log http://ppc.koji.fedoraproject.org/kojifiles/work/tasks/1317/1571317/build.log
*** Bug 1067421 has been marked as a duplicate of this bug. ***
Following bug 1067421, how should I send you my ssh key ?
Hi, Just send me a mail (karsten) with the bugzilla number in the subject and attach the public ssh key to it. I'll set up a user for you on our public accessable PPC machines at the Oregon State University and send you instructions when I'm done.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.