copr-devel November 2016

copr-devel@lists.stg.fedorahosted.org

10 participants
10 discussions

| tail the logs
by Ryan H. Lewis 29 Nov '16

29 Nov '16

Koji allows us to the the logs more or less as they are generated. Is it possible to do the same with koji? I have long builds ~30 minutes -- 1 hour. It is nice to see where things are while the logs get generated..

2 1

| erase old builds
by Ryan H. Lewis 28 Nov '16

28 Nov '16

I've got about ~40 builds that are over a day old and dont seem to want to complete. I really would like to be able to cancel jobs that have already started, or enforce a timeout on the build jobs that fails them if they take longer than X time. Here is a list of some of the stale jobs: 479039 elemental 0.87-2.el7.centos 2 hours ago 102 minutes running 478917 elemental 0.87-2.el7.centos 24 hours ago 105 minutes running 478902 elemental 0.87-2.el7.centos 25 hours ago 2 hours failed 478900 elemental 0.87-2.el7.centos 25 hours ago 42 minutes failed 478894 elemental 0.87-2.el7.centos 25 hours ago 2 hours failed 478890 elemental 0.87-2.el7.centos 26 hours ago 2 hours running 478889 elemental 0.87-2.el7.centos 26 hours ago 113 minutes running 478870 elemental 0.87-2.el7.centos 27 hours ago 105 minutes succeeded 478866 elemental 0.87-2.el7.centos 28 hours ago 105 minutes succeeded 478848 elemental 0.87-2.el7.centos 30 hours ago 27 hours running 478669 elemental 0.87-2.el7.centos 2 days ago 28 hours succeeded 478629 elemental 0.87-2.el7.centos 2 days ago 29 hours failed 478627 elemental 0.87-2.el7.centos 2 days ago 31 hours failed 478625 elemental 0.87-2.el7.centos 2 days ago 28 hours failed 478622 elemental 0.87-2.el7.centos 2 days ago 30 hours failed I've tried asking a few times in #fedora-buildsys, but, I have not been able to see any responses there. I've been having trouble with IRC.

2 4

| missing status_to_order function
by Martin Juhl 23 Nov '16

23 Nov '16

Hi When trying to access the build and package pages I get: ProgrammingError: (psycopg2.ProgrammingError) function status_to_order(integer) does not exist LINE 8: ...LECT build_chroot.build_id, started_on, ended_on, status_to_... ^ HINT: No function matches the given name and argument types. You might need to add explicit type casts. [SQL: '\nSELECT build.id, MAX(package.name) AS pkg_name, build.pkg_version, build.submitted_on,\n MIN(statuses.started_on) AS started_on, MAX(statuses.ended_on) AS ended_on, order_to_status(MIN(statuses.st)) AS status,\n build.canceled, MIN("group".name) AS group_name, MIN(copr.name) as copr_name, MIN("user".username) as user_name\nFROM build\nLEFT OUTER JOIN package\n ON build.package_id = package.id\nLEFT OUTER JOIN (SELECT build_chroot.build_id, started_on, ended_on, status_to_order(status) AS st FROM build_chroot) AS statuses\n ON statuses.build_id=build.id\nLEFT OUTER JOIN copr\n ON copr.id = build.copr_id\nLEFT OUTER JOIN "user"\n ON copr.user_id = "user".id\nLEFT OUTER JOIN "group"\n ON copr.group_id = "group".id\nWHERE build.copr_id = %(copr_id)s\nGROUP BY\n build.id;\n'] [parameters: {'copr_id': 1}] Seems like the function "status_to_order" is missing.. I have tried upgrading to python-psycopg2-2.6.1-1.. no change... Any suggestions??? /Martin

3 8

| Kerberos authentication example
by Martin Juhl 22 Nov '16

22 Nov '16

Hi guys Miroslav has told me that Pavel Raiskup is using Kerberos authentication on his Copr installation.. Is it possible to see the configuration for the kerberos authentication.. both in copr.conf and for apache?? Thanks Martin Juhl IT-Consultant@Casalogic A/S, RHCA

3 6

| planned hotfix deployment for build restarting
by Michal Novotny 22 Nov '16

22 Nov '16

Today (11/22) at 4pm UTC, I will apply a hotfix for build restarting. Also, I will attempt to address https://bugzilla.redhat.com/ show_bug.cgi?id=1395582 for ppc64le builders. clime

1 0

| Erase build (stuck as pending)
by Yves Dionne 19 Nov '16

19 Nov '16

I have a build that is stuck in limbo. https://copr.fedorainfracloud.org/coprs/dionney/kernel/build/432228/ I've cancelled it a while ago, and the status is cancelled in the 'General Information' section, but it also shows as pending in the 'Results' section. I can't do anything about, can you help me?

1 0

| Erase build
by Antonio Trande 18 Nov '16

18 Nov '16

Hi all. Please, erase the build https://copr.fedorainfracloud.org/coprs/sagitter/trilinos/build/477291/ that looks endless (it's running since over 26 hours). -- --- Antonio Trande mailto: sagitter 'at' fedoraproject 'dot' org https://fedoraproject.org/wiki/User:Sagitter GPG Key: 0x6CE6D08A Check on https://keys.fedoraproject.org/

2 1

| Loading changes to an own Copr project
by Antonio Trande 17 Nov '16

17 Nov '16

Hi all. How can i commit changes to my Copr project without uploading source code archive every time? -- --- Antonio Trande mailto: sagitter 'at' fedoraproject 'dot' org https://fedoraproject.org/wiki/User:Sagitter GPG Key: 0x6CE6D08A Check on https://keys.fedoraproject.org/

3 3

| move to pagure
by Michal Novotny 15 Nov '16

15 Nov '16

Hey, I'd like to ask the community if it's alright to officially move to pagure. I should have probably asked earlier but I haven't thought about it, I must admit. Pagure is an open-source project tight to Fedora Infrastructure, which COPR can use to its advantage. Auto-rebuilds launched on new commits are already working by employing great fedmsg infrastructure bus. I think there might be more possibilities there that I cannot see at the moment. Another advantage is that we can move our COPR wiki to Pagure from fedorahosted.org (going to be sunset) and have both code base and wiki on pagure.io and therefore use only one platform for these two. I probably won't be able to move closed pull requests from Github, which I wanted to do, but I have already started (really just started) working on that feature into pagure-importer so that other projects can have this. If you have any objections against moving to Pagure, please, tell. Thanks clime

5 19

| codebase moved to pagure.io
by Michal Novotny 03 Nov '16

03 Nov '16

Hello folks, codebase will be now hosted on pagure.io (https://pagure.io/copr/copr) We would like to start working on this platform. Not that Github is bad but I think that pagure.io will be good place as well. COPR team

5 15

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

copr-devel November 2016