<@adamwill:fedora.im>
15:00:49
!startmeeting Quality
<@meetbot:fedora.im>
15:00:51
Meeting started at 2025-04-28 15:00:49 UTC
<@meetbot:fedora.im>
15:00:51
The Meeting name is 'Quality'
<@adamwill:fedora.im>
15:00:55
!topic Roll Call
<@adamwill:fedora.im>
15:01:00
!hi
<@adamwill:fedora.im>
15:01:06
who's around for quality meeting fun?
<@zodbot:fedora.im>
15:01:07
Adam Williamson (adamwill) - he / him / his
<@bittin:matrix.org>
15:02:21
.hi bittin
<@bittin:matrix.org>
15:02:28
!hi bittin
<@zodbot:fedora.im>
15:02:30
Luna Jernberg (bittin) - they / them / theirs
<@nielsenb:fedora.im>
15:02:47
!hi
<@zodbot:fedora.im>
15:02:48
Brandon Nielsen (nielsenb)
<@boniboyblue:fedora.im>
15:03:14
!hi
<@zodbot:fedora.im>
15:03:15
Christopher Boni (boniboyblue)
<@adamwill:fedora.im>
15:04:26
hi hi everyone
<@adamwill:fedora.im>
15:04:29
let's get rolling
<@adamwill:fedora.im>
15:04:33
!topic Previous meeting follow-up
<@lruzicka:matrix.org>
15:04:38
allo
<@lruzicka:matrix.org>
15:05:02
!hi
<@zodbot:fedora.im>
15:05:04
Lukáš Růžička (lruzicka)
<@adamwill:fedora.im>
15:06:21
!info "adamw to check in with anaconda team and co-ordinate plans for webui during f43 cycle" - I have checked in, the current state is that they attempt to run daily and report to the wiki, but it's a bit unsophisticated: they use a cronjob-equivalent, and use a URL template to find the thing to run against; switching between rawhide and branched has to be done manually. like openQA the system does not report failures, so results need to be checked directly in the test system web UI to see and investigate failures. I'll continue working with the anaconda team on ways to improve and organize this
<@adamwill:fedora.im>
15:07:32
anything else on that, or any other followup from last week?
<@nielsenb:fedora.im>
15:08:44
Are these integration style tests, that use a tool to interact with the UI, or more unit style that fake a DOM and mock and backend?
<@nielsenb:fedora.im>
15:09:01
Are these integration style tests, that use a tool to interact with the UI, or more unit style that fake a DOM and mock a backend?
<@nielsenb:fedora.im>
15:09:36
I'm assuming we're interested in the former, like we have for traditional Anaconda
<@m4rtink:fedora.im>
15:09:50
just making sure - if there is just Rawhide, the tests should run jut on Rawhide - if there is both Rawhide and branches, then test should run on both I guess ?
<@kparal:matrix.org>
15:10:41
it would be really nice to make it run anaconda tests together with our own tests, at least for RCs. Otherwise we simply don't know which tests will be covered by automation and spend time to test cases which will get populated some time in the next 24h.
<@adamwill:fedora.im>
15:11:08
Brandon Nielsen they're integration style tests
<@m4rtink:fedora.im>
15:11:16
Brandon Nielsen: its using the Cockpit test tooling, which can do a lot of things - both working with the DOM, clicking on things and even do pixel tests
<@adamwill:fedora.im>
15:11:42
ideally yes
<@m4rtink:fedora.im>
15:11:53
OK
<@adamwill:fedora.im>
15:12:00
but the minimum needed for release validation is to always run on the next release: branched when it exists, rawhide when branched doesn't exist
<@adamwill:fedora.im>
15:12:11
running on rawhide when branched doesn't exist is not *required*
<@m4rtink:fedora.im>
15:12:21
that makes sense
<@adamwill:fedora.im>
15:12:24
running on rawhide when branched exists is not *required*
<@adamwill:fedora.im>
15:13:01
oh, and yes, the current implementation doesn't handle candidates automatically, which is a significant issue
<@adamwill:fedora.im>
15:13:09
thanks for noting that kparal
<@adamwill:fedora.im>
15:14:13
!info kparal notes issues with candidate composes. the current automatic scheduler for the anaconda system does not handle candidate composes at all; even if we fix that, timer-based triggering is a poor fit with candidates where we want the results ASAP
<@adamwill:fedora.im>
15:14:36
mkolman we should probably have tickets to track the main issues here. where should we put those?
<@bittin:matrix.org>
15:16:01
Anaconda Github Issues?
<@adamwill:fedora.im>
15:17:55
the main anaconda repo doesn't have issues enabled, you're meant to file bugzilla bugs
<@adamwill:fedora.im>
15:18:01
bugzilla feels a slightly odd venue for this, but meh
<@adamwill:fedora.im>
15:18:06
i can figure that out with the team async
<@adamwill:fedora.im>
15:18:28
!action adamw to work with anaconda team on tracking the minimum requirements to make this viable for f43 validation
<@bittin:matrix.org>
15:18:48
ah i see i confused with dnf5 sorry
<@bittin:matrix.org>
15:19:33
https://github.com/rhinstaller/anaconda-webui/discussions but yeah maybe there is a better place
<@adamwill:fedora.im>
15:20:04
yeah, the webui repo has tickets enabled. i guess this testing is webui-specific so we *could* do it there.
<@adamwill:fedora.im>
15:20:09
anyhoo!
<@adamwill:fedora.im>
15:20:19
!topic Fedora 43 status
<@adamwill:fedora.im>
15:20:33
i don't really have anything specific, but it's always good to follow tradition
<@adamwill:fedora.im>
15:20:38
anyone got any notes on f43?
<@adamwill:fedora.im>
15:20:53
6.15 kernel series has been a bit rough on my laptop so far...
<@bittin:matrix.org>
15:21:46
tested the 2 latest Workstation candidates and not had any problems so far
<@nielsenb:fedora.im>
15:23:17
The latest nominated compose worked decently on my (ancient) laptop, haven't tried it on anything else yet.
<@nielsenb:fedora.im>
15:23:36
Can't imagine there's much churn in any of the hardware support for something still branded "Compaq".
<@m4rtink:fedora.im>
15:23:59
adamw: yeah, Bugzilla is the best bet :P
<@m4rtink:fedora.im>
15:26:11
https://github.com/rhinstaller/anaconda-webui/issues does seems to be enabled - but there are no issues :)
<@adamwill:fedora.im>
15:27:02
huh, that's weird, i thought we'd used it before.
<@adamwill:fedora.im>
15:28:26
oh, well
<@adamwill:fedora.im>
15:28:39
!topic Test Day / community event status
<@adamwill:fedora.im>
15:29:09
doesn't look like there's anything coming up
<@adamwill:fedora.im>
15:29:24
!info kernel 6.14 test week happened - https://testdays.fedoraproject.org/events/216 . thanks to everyone who tested!
<@adamwill:fedora.im>
15:32:52
that's about all i got
<@adamwill:fedora.im>
15:32:56
!topic Open floor
<@adamwill:fedora.im>
15:32:59
any other business?
<@adamwill:fedora.im>
15:33:26
so I do have one thing for this!
<@adamwill:fedora.im>
15:33:41
we have a new testdays app in testing (exciting, i know): https://testdays.stg.fedoraproject.org/
<@nielsenb:fedora.im>
15:33:54
Oooh!
<@bittin:matrix.org>
15:34:07
its still early in the 43 cycle
<@bittin:matrix.org>
15:34:25
oh
<@kparal:matrix.org>
15:34:44
disclaimer: FAS login is not enabled yet, just Google login
<@adamwill:fedora.im>
15:34:45
please play around with it and see if you find any problems
<@kparal:matrix.org>
15:34:48
but you can play around
<@adamwill:fedora.im>
15:34:53
i just did fas login. it worked
<@adamwill:fedora.im>
15:35:16
it's through staging FAS though, so you might have to do something like use an old password or leave out your OTP
<@kparal:matrix.org>
15:35:23
interesting!
<@kparal:matrix.org>
15:35:36
also, please report all issues here: https://pagure.io/fedora-qa/testdays-web/issues
<@adamwill:fedora.im>
15:35:41
click "Login", then "Login via OIDC"
<@adamwill:fedora.im>
15:36:10
!info new version of the testdays webapp is in testing at https://testdays.stg.fedoraproject.org/ . please try it out and report any problems you find to https://pagure.io/fedora-qa/testdays-web/issues
<@kparal:matrix.org>
15:36:12
you can also submit anonymous results, without login
<@adamwill:fedora.im>
15:38:24
any other business?
<@kparal:matrix.org>
15:38:58
nope
<@nielsenb:fedora.im>
15:39:05
Not from me
<@lruzicka:matrix.org>
15:39:11
not so far
<@adamwill:fedora.im>
15:39:46
allllllrighty. thanks for coming out, folks
<@adamwill:fedora.im>
15:40:14
!endmeeting