15:32:38 #startmeeting Fedora CI SIG 15:32:38 Meeting started Wed Dec 2 15:32:38 2020 UTC. 15:32:38 This meeting is logged and archived in a public location. 15:32:38 The chair is jbair. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:32:38 Useful Commands: #action #agreed #halp #info #idea #link #topic. 15:32:38 The meeting name has been set to 'fedora_ci_sig' 15:32:38 .hello jimbair 15:32:39 jbair: jimbair 'Jim Bair' 15:40:57 quiet day today :) 15:42:57 What are the current CPU/Memory specs for the test runners and would it be possible to allocate test runners with more resources for select packages? 15:42:59 msrb: anything noteworthy on the jobs in our new jenkins instances? 15:45:00 jbair, can't think of anything right now 15:45:32 tstellar, mvadkert should be able to answer your question about the current resources 15:45:44 msrb: thanks. to tstellar's questions, are test runners tied to standard-test-roles? I know you can set more RAM in provision.fmf 15:46:10 jbair, provision.fmf is ignored by testing farm 15:46:18 AFAIK 15:46:29 ah - how do we change runner resources in testing farm? 15:47:12 I don't think it is possible right now. The machines there should be beefy enough for most use cases, but mvadkert knows the details 15:49:02 Our use case is for the toolchain packages: Rebuilding X number of important packages for a gcc or clang update. 15:49:26 I've experimented with this in the past, but ran into timeouts for some of the bigger packages. 15:50:07 But this was also with old Jenkins system, so part of what I wanted to know is if the test runners on the new system had more resources allocated. 15:51:01 tstellar: it sounds like it - msrb do you know what the new runners are configured with? 15:52:16 jbair, I am pretty sure mvadkert told me in the past, but I don't remember... sorry 15:52:21 is there a git repo I can dig into? 15:52:48 testing farm deployment? 15:53:00 no idea :) 15:56:01 I assume miro is tied up or he would reply :) but tstellar I would try it out (if you can) and if it fails let us know 15:56:12 but the new workers have more resources, but how many I don't know - we can find out once Miro is available 15:56:21 yep 15:56:37 jbair: OK, that's good to know. I will do some experimenting. 15:57:06 great :) alright, closing out our weekly meeting as things are a bit slow coming into the shutdown :) 15:57:07 #endmeeting