ravanelli has quit [Remote host closed the connection]
ksinny_ has joined #fedora-coreos
ksinny has quit [Ping timeout: 276 seconds]
paragan has joined #fedora-coreos
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 258 seconds]
Betal has quit [Quit: WeeChat 3.5]
jpn has joined #fedora-coreos
jpn has quit [Ping timeout: 246 seconds]
jpn has joined #fedora-coreos
ksinny_ has quit [Remote host closed the connection]
crobinso has joined #fedora-coreos
miabbott[m] has quit [Quit: You have been kicked for being idle]
jcajka has joined #fedora-coreos
jpn has quit [Ping timeout: 246 seconds]
jpn has joined #fedora-coreos
KrisK1980 has joined #fedora-coreos
ravanelli has joined #fedora-coreos
<KrisK1980>
Hi, is there any option to autologin to FedoraCoreos (I'm using IronicPythonAgent), this lines stopped to work for me: - coreos.autologin=tty1 coreos.autologin=ttyS0
vladan5 is now known as vladan
nalind has joined #fedora-coreos
miabbott[m] has joined #fedora-coreos
plarsen has joined #fedora-coreos
ikonia_ has joined #fedora-coreos
ikonia_ has quit [Client Quit]
jlebon has joined #fedora-coreos
mheon has joined #fedora-coreos
plarsen has quit [Ping timeout: 255 seconds]
plarsen has joined #fedora-coreos
plarsen has quit [Remote host closed the connection]
<travier[m]>
<dustymabe> "hey travier - should we revisit..." <- Indeed, I should put that on my to-do for this week
<dustymabe>
travier[m]: +1
<dustymabe>
we should probably also take some time to get together and hash out the remaining details for release notes mechanics
<travier[m]>
Yep. Can you put something in my calendar?
<dustymabe>
i can try :)
bgilbert has joined #fedora-coreos
gursewak has joined #fedora-coreos
<dustymabe>
jlebon: ravanelli: can we get together today to discuss some strategy for the cosa multi-arch pieces ?
<dustymabe>
and how it overlaps with the investigation of using `podman --remote` instead of gangplank
<dustymabe>
gursewak: FYI I added the `ok-to-promote` labels to the FCOS streams tickets for the releases earlier today (to get a head start on CI)
<ravanelli>
dustymabe: Sure, Do you guys have time now? If not, let me know when
<dustymabe>
i can do now - will wait on jlebon to respond
<gursewak>
👍
* dustymabe
be back in 5
jcajka has quit [Quit: Leaving]
<jlebon>
dustymabe, ravanelli: i can do now assuming it's not too long
<dustymabe>
it shouldn't be
mnguyen_ has joined #fedora-coreos
mnguyen has quit [Ping timeout: 244 seconds]
paragan has quit [Remote host closed the connection]
mnguyen has joined #fedora-coreos
mnguyen_ has quit [Ping timeout: 246 seconds]
jpn has quit [Ping timeout: 246 seconds]
jcajka has joined #fedora-coreos
<dustymabe>
saqali: bgilbert: a lot of our test pipeline flakes are now related to network access to remote resources (i.e. yum mirror fails intermittently for package layering test) - I wonder if we could/should enhance our logic to allow reruns to succeed the run for tests that "needs-internet".
<saqali>
I think thats definitely doable
<saqali>
However, I would prefer if we could first explore a way to allow passes only on network issues rather than allowing for any test that "needs-internet".
Betal has joined #fedora-coreos
<saqali>
Since we can still see race conditions depending on the test.
<dustymabe>
saqali: i.e. inspect each test to see if we could make it more resilient?
<saqali>
more along the lines of enabling a flag that will allow rerun to pass for that test only if it failed on a network issue
PhrozenByte has left #fedora-coreos [#fedora-coreos]
<dustymabe>
right, but how do you know without inspecting the test?
<dustymabe>
i.e. modifying each test
<saqali>
I think it would be worthwhile to modify a test to introduce "error types", it would only be adding a couple lines to each test
<dustymabe>
I think part of the problem there is for exttests - not sure how we'd be able to pass that information back to kola
<saqali>
Hmm maybe certain exit codes?
<saqali>
not sure exactly
<dustymabe>
yeah that's true. could use specific exit codes to pass that info
<saqali>
we wouldnt need to modify all tests at once, we could do it on a as-needed basis
<dustymabe>
maybe let's see what bgilbert thinks
<saqali>
👍
<bgilbert>
I suppose we don't have any way to improve network reliability on the runners
<bgilbert>
failing that... yeah, I like saqali's idea
<bgilbert>
and exit codes for ext tests sgtm
<dustymabe>
bgilbert: +1
<dustymabe>
saqali: so in that case what we could do is add the scaffolding for supporting this (i.e. test is able to indicate it failed due to network issue and the rerun logic) - and then when we have issues with tests we'll just add the support to them one by one to hook into this functionality
<saqali>
dustymabe: sounds good!
rsaini has joined #fedora-coreos
gursewak_ has joined #fedora-coreos
gursewak has quit [Ping timeout: 240 seconds]
arnulfo_7 has joined #fedora-coreos
arnulfo_7 has quit [Changing host]
arnulfo_7 has joined #fedora-coreos
skunkerk__ is now known as skunkerk
<skunkerk>
dustymabe: our devconf.us talk on the FCOS lab session got accepted
<dustymabe>
skunkerk: yep. I saw!
<dustymabe>
have you talked to your manager yet about travel?
gursewak_ has quit [Ping timeout: 272 seconds]
gursewak has joined #fedora-coreos
jcajka has quit [Quit: Leaving]
jpn has joined #fedora-coreos
mnguyen_ has joined #fedora-coreos
mnguyen has quit [Ping timeout: 255 seconds]
rsaini has quit [Quit: Leaving]
rsaini has joined #fedora-coreos
rsaini has quit [Client Quit]
Guest19 has joined #fedora-coreos
Guest19 has quit [Client Quit]
crobinso has quit [Remote host closed the connection]