CI-users

ci-users@lists.centos.org

1 participants
418 discussions

'No space left on device' on systemd-ci-slave01
by František Šumšal 19 Mar '19

19 Mar '19

Hello, I noticed that systemd CI jobs started failing with "No space left on device" error: https://ci.centos.org/job/systemd-ci-build/264/console Can't update build descriptionjava.io.IOException: com.thoughtworks.xstream.io.StreamException: : No space left on device ERROR: Step ‘Archive the artifacts’ aborted due to exception: java.io.IOException: No space left on device https://ci.centos.org/job/systemd-pr-build-vagrant/775/console I wanted to tweak the artifact rotation settings a little (as right now it's 180 days for regular builds and 90 days for debug builds, but it was already too late. Thank you, Frantisek -- GPG key ID: 0xFB738CE27B634E4B

1 0

irregular execution
by Vladimir Benes 20 Feb '19

20 Feb '19

Hi all, is there a reason why we have irregular execution? https://ci.centos.org/view/NetworkManager/job/NetworkManager-nm-1-14/ or https://ci.centos.org/view/NetworkManager/job/NetworkManager-master/ Does anyone see it too? All my NM jobs are affected. Thanks, Vladimir

2 3

Service Degradation: Github triggered Jobs | 14-Feb-2019/Ongoing
by Brian Stinson 19 Feb '19

19 Feb '19

Date: 14-Feb-2019 - Ongoing Description: We are noticing that we are burning through our entire hourly Github API quota, sometimes quite rapidly. This affects jobs that trigger from Github, and jobs that report back using the githubNotify pipeline step. Symptoms: - Jobs that trigger using the GHPRB or Github-branch-source plugins (even with webhooks properly configured) may be delayed in triggering - Jobs that report back to Github PRs may hang until it can grab the appropriate quota Next steps: - Clean up old repos [we've already done as many as we can, if you have dead jobs please contact us] - Split up "heavy" Github API users to new Github tokens, with their own quotas Timeline for resolution: Ongoing, we'll post here as we have more details.

1 0

Request for more executor VMs for the Gluster project
by Kaushal M 09 Jan '19

09 Jan '19

Hi, Just a little while back, the gluster-ci-slave01 VM assigned to the Gluster project went offline. Fabian diagnosed this to have been caused by the VM being overloaded with too many jobs. Can an additional VM be setup for the gluster project to handle the increased load? Thanks.

2 2

gluster-ci-slave01 is offline
by Kaushal M 08 Jan '19

08 Jan '19

Hi, gluster-ci-slave01 has gone offline sometime in the last 3-4 hours. This is blocking CI tests for a few gluster projects. Can this be looked at? Thanks. ~kaushal

1 1

Http address for Minishift master branch builds not available
by Lalatendu Mohanty 03 Jan '19

03 Jan '19

Hi, We observed that [2] i.e. artifacts.ci.centos.org/minishift/minishift/master is returning 404 error. Hence our CI jobs are failing [1] . Any idea why this happened? [1] https://github.com/minishift/minishift/issues/3102 [2] http://artifacts.ci.centos.org/minishift/minishift/master Thanks, Lala

1 0

Environment variables in jenkins
by Anjan Nath 17 Dec '18

17 Dec '18

Hi, We need to add couple of environment variables to the minishift-slave02 these are some credentials for our integration tests. Is it possible to add this from the web console, or one of the maintainers need to do it? If so who is the contact person for this? Thanks, Anjan

3 3

Minishift ci slave is offline
by Lalatendu Mohanty 04 Dec '18

04 Dec '18

Hi, It seems that minishift-ci-slave02 is offline [1], so we can not run CI jobs. Can someone look into this? [1] https://ci.centos.org/computer/minishift-ci-slave02/ Thanks, Lala

2 1

duffy fails to give nodes on devtools slave04
by Roman Iuvshyn 29 Nov '18

29 Nov '18

This has been an issue since ~11 AM UTC. -- ROMAN IUVSHYN Red Hat <https://www.redhat.com/> riuvshyn(a)redhat.com <https://red.ht/sig>

2 3

Some propsed changes in bugs.centos.org (permissions updates, and reorganization)
by Brian Stinson 27 Nov '18

27 Nov '18

Hi Folks, I have a couple of problems and proposals that I'd like to discuss for bugs.centos.org: PROBLEM 1: Currently when a user reports an issue it's very difficult for them to know where to route things properly. The confusion seems to be between projects and categories. For example, Ci.centos.org Ecosystem Testing is the category under the Buildsys project that's supposed to be used for both infrastructure issues and new account requests. It's not immediately obvious that the user needs to select the Buildsys project to get there though. If they do make it that far, but forget to choose the Ci.centos.org ecosystem testing category , it may get assigned by default to someone who are active in CentOS but outside of maintaining the CICO infra (sorry alphacc and range!). PROPOSAL: Move CentOS CI to it's own "Project" so that it shows up in the dropdown list, and allow us to segment CI requests from SIG requests. PROBLEM 2: In the Buildsys project, once someone reports and issue, they can no longer update it (ex: if they chose the wrong category, or no longer have the issue and would like to close it). In a few projects like Buildsys (and CICO) it makes sense to allow these folks a little freedom in modifying some of the bug fields. PROPOSAL: For the Buildsys and CICO projects -only- allow Reporters to Close, Reopen, and Update their own issues. This would leave the Distro and SIG projects unaffected. I can make these changes if we're all happy. Are there any objections? -- Brian Stinson CentOS Infrastructure Team

1 0

← Newer
1
...
11
12
13
14
15
16
17
...
42
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

CI-users