ChanServ changed the topic of #freedesktop to: https://www.freedesktop.org infrastructure and online services || for questions about freedesktop.org projects, please see each project's contact || for discussions about specifications, please use https://gitlab.freedesktop.org/xdg or xdg@lists.freedesktop.org
Ultrasauce has quit [Remote host closed the connection]
sauce has joined #freedesktop
Haaninjo has quit [Quit: Ex-Chat]
___nick___ has quit []
___nick___ has joined #freedesktop
___nick___ has quit []
___nick___ has joined #freedesktop
alpernebbi has quit [Ping timeout: 480 seconds]
alpernebbi has joined #freedesktop
alanc has quit [Remote host closed the connection]
alanc has joined #freedesktop
m5zs7k has quit [Ping timeout: 480 seconds]
m5zs7k has joined #freedesktop
danvet has joined #freedesktop
itoral has joined #freedesktop
pzanoni has quit [Ping timeout: 480 seconds]
pzanoni has joined #freedesktop
agd5f_ has joined #freedesktop
agd5f has quit [Ping timeout: 480 seconds]
mvlad has joined #freedesktop
scrumplex has quit [Quit: Quassel - Signing Off]
scrumplex has joined #freedesktop
<bentiss>
daniels: do you plan on doing the 15.8.1 upgrade this morning or should I?
phasta has joined #freedesktop
<daniels>
bentiss: I was going to do it just now but you’re also welcome to if you prefer?
<bentiss>
daniels: not specially, feel free to do it
<bentiss>
the new "feature" that consists in harrassing admins when there is a security update is really efficient I must confess :)
we11en has joined #freedesktop
agd5f has joined #freedesktop
<mupuf>
bentiss: hehe
* mupuf
wonders if this will also fix the slowness for pipelines to appear
<mupuf>
it can take over a minute after a push for a pipeline to appear
agd5f_ has quit [Ping timeout: 480 seconds]
we11en has quit []
<daniels>
bentiss: have you ever seen anything where the migrations job succeeds, but the webservice won't start because the db/schema versions are out of sync?
<bentiss>
daniels: I had a migration failing once, it was painful to sort it out :/
<daniels>
I was looking at the registry migrations having finished yet; the main schema is still working away
<bentiss>
oh, yes
<bentiss>
still the last log event was registered at 2023-02-01 09:57:42, so it's taking a little bit of time
<bentiss>
do we have enough space on the postgres disk?
<bentiss>
(I checked before the migration and it was OK)
<bentiss>
94%...
AbleBacon has quit [Read error: Connection reset by peer]
<daniels>
oh ...
<bentiss>
the postgresql pod is using some CPU since that time so I guess it must be working
<bentiss>
it advanced
<bentiss>
and done
<daniels>
\o/
<bentiss>
yep :)
<bentiss>
I manually kicked the ones that were failing to speed up things a bit
<daniels>
heh, thanks :)
<bentiss>
daniels: BTW, looking at the CPU usages per pods that you mentioned yesterday. The OSD and the rgw pods have a limit of 3, but they never reach that value (from the influx logs)
<bentiss>
maybe we can increase them, but I am not sure it'll change a lot
<daniels>
hrm, I wonder where the 50x is coming from then :\
<bentiss>
have you explored the logs through grafana/loki?
<eric_engestrom>
within a few minutes, cloning random repos on the instance and sending a nonsense MR to one of them, and apparently requesting access to another...
<eric_engestrom>
looks way too much like a spam bot trying to hit all the checkboxes to not get marked as inactive
<eric_engestrom>
oh, and that account is also "following" another account (whatever that means on gitlab?)
<daniels>
shrug, there are a lot of legitimate people who do that, because they just want to register on a gitlab instance and see what the buttons do
<daniels>
but yeah, blocked now
MajorBiscuit has joined #freedesktop
vkareh has joined #freedesktop
phasta_ has joined #freedesktop
itoral has quit [Remote host closed the connection]
phasta has quit [Ping timeout: 480 seconds]
phasta__ has joined #freedesktop
ximion has quit []
ximion has joined #freedesktop
phasta_ has quit [Ping timeout: 480 seconds]
agd5f_ has joined #freedesktop
agd5f has quit [Ping timeout: 480 seconds]
phasta has joined #freedesktop
<Venemo>
hi guya
<Venemo>
hi guys
<Venemo>
when can I expect to see the new VK CTS in the Mesa CI?
<Venemo>
I have been waiting for that since september, and this is now blocking some progress in RADV development
<daniels>
Venemo: that'd be #dri-devel, but I don't know of anyone who has specific plans to bump the dep - you could just file an MR if it's blocking you - and make sure to stress-test the resulting tree to find out what exciting new problems it brings with it
<Venemo>
I don't see why that is up to me, to be honest
<Venemo>
but ok I'll take this to dri-devel
<daniels>
Venemo: shrug, it's something for Mesa as a whole to do
<daniels>
who were you expecting to do it?
<Venemo>
I don't know, whoever is responsible for that part
<daniels>
no-one's specifically responsible for the CTS - when it's been updated, it's been updated by whichever driver team needed the new version at that point
phasta__ has quit [Ping timeout: 480 seconds]
<Venemo>
oh my god
<Venemo>
I guess I'll just accept that this EXT will have no test coverage for the foreseeable future
<daniels>
that's a shame
Leopold_ has quit [Ping timeout: 480 seconds]
<jenatali>
There was a discussion about upreving the CTS a few minutes ago in dri-devel
<daniels>
jenatali: uh ... if there was, it never made it across the Matrix barrier
<jenatali>
Oh
<daniels>
Venemo: put it this way, updating the CTS is the same as getting core support for the extension as a whole - it's not something that someone else will magically do, but someone who wants/needs it has to sit down and make it happen
<Venemo>
I'm sorry but that's too much for me, I have zero clue how the CI system works
<daniels>
it's definitely less difficult than implementing task shaders :P
<jenatali>
At least I assume that's what was meant by vckts
<daniels>
jenatali: oh huh
phasta has quit [Ping timeout: 480 seconds]
<Venemo>
I'd be fine with dealing with that for the radv ci, but I don't have the energy to deal with this for every driver. Is there a way to just use the new version for radv and let everyone else upgrade to it on their own time?
<daniels>
no
<Venemo>
ok
<Venemo>
fortunately the NV mesh shader tests cover much of the same code paths, so I guess I'll just keep relying on those tests then
<daniels>
sure, if that works for you
ManMower has joined #freedesktop
<Venemo>
it's disappointing, but I don't think I have a choice
Leopold_ has joined #freedesktop
phasta has joined #freedesktop
Leopold__ has joined #freedesktop
Leopold_ has quit [Ping timeout: 480 seconds]
Leopold__ has quit [Ping timeout: 480 seconds]
Leopold_ has joined #freedesktop
AbleBacon has joined #freedesktop
<alanc>
did gitlab change fonts? It looks... different
<zmike>
oh I thought it was just me
<bentiss>
we updated this morning to 15.8.1, so... maybe?
<daniels>
airlied: ohhh, it's on GitHub, because it's forked from the Khronos repo. ugh. I think just move it to your own for now and let's figure it out
Leopold_ has quit [Remote host closed the connection]
Leopold_ has joined #freedesktop
<daniels>
bwidawsk: you're not declaring $FDO_DISTRIBUTION_TAG (this needs to be a value you bump every time you want the container to be rebuilt, i.e. you've changed deps or just want new versions or whatever) which is the error - but you're also setting $FDO_DISTRIBUTION_EXEC twice
<bwidawsk>
daniels: the second was alast minute fix attempt... thanks