Closed nalimilan closed 3 years ago
I manually disabled checking the return value of that particular step, since it almost always fails for me. (It would time out, or one of the copr builds would fail, while many others would succeed, etc....) I'll try to figure out what's going on.
I was able to manually start a new build through the copr
web interface, so it's not a permissions error with my account. Running it on the commandline with --debug
gives:
$ copr-cli --debug build nalimilan/julia-nightlies https://s3.amazonaws.com/julianightlies/bin/srpm/julia-0.4.0-0.20150313.el7.centos.src.rpm
[16:25:52] {/usr/lib/python2.7/site-packages/copr_cli/main.py:402} DEBUG - # Debug log enabled #
[16:25:52] {/usr/lib/python2.7/site-packages/copr/client/client.py:154} DEBUG - Fetching url: https://copr.fedoraproject.org/api/coprs/nalimilan/julia/new_build/, for login: ********************
[16:25:52] {/usr/lib/python2.7/site-packages/urllib3/connectionpool.py:535} INFO - Starting new HTTPS connection (1): copr.fedoraproject.org
[16:25:53] {/usr/lib/python2.7/site-packages/urllib3/connectionpool.py:295} DEBUG - "POST /api/coprs/nalimilan/julia/new_build/ HTTP/1.1" 500 54
[16:25:53] {/usr/lib/python2.7/site-packages/copr/client/client.py:169} DEBUG - raw response: {
"error": "Invalid request",
"output": "notok"
}
[16:25:53] {/usr/lib/python2.7/site-packages/copr/client/client.py:192} ERROR - Server error, raw response body: {
"error": "Invalid request",
"output": "notok"
}
Something went wrong:
Error: Invalid request
I've blanked out my login
above, just 'cause I'm paranoid. I remade my authentication token as I noticed it would expire in a week or so, but that doesn't seem to have fixed anything. What is the output you get from pasting the above line?
@nalimilan has this been causing problems? Do we need to change anything? My guess is that the copr-cli
command is failing just because it's timing out since the Julia build takes a long time to run. I don't want to increase the timeout since I want the machine to be able to go on building other things, so I don't think there's anything to fix here. Do you agree?
I don't understand why copr-cli fails when trying to build RPM nightlies. The command works fine locally. Could you try to run it manually on the buildbot?
http://buildbot.e.ip.saba.us:8010/builders/package_srpm/builds/385/steps/Bully%20Copr%20into%20building%20for%20us/logs/stdio
Also, any idea why the build is considered as successful even if one of the steps failed? We should be able to check the return value of
copr-cli
(0 for success, as usual).