<omegatron>
ah yes, I know rrdtool - i'm in the middle of building and installing packages myself on my machine and rrdtool is on my list ..
<omegatron>
right now i'm stuck at upgrading x265 for ffmpeg
ximion has quit []
<bipul>
omegatron, Can you please help me in compiling rrdtool from source? on Linux as well as on freebsd?
<bipul>
I have downloaded the source code using apt-get download source rrdtool and received rrdtool_1.7.1-2.debian.tar.xzrrdtool_1.7.1-2.dsc rrdtool_1.7.1.orig.tar.gz files.
<omegatron>
I could try, as soon as I got x265 built and installed ..
<omegatron>
though, I have no freebsd machine here .. (but I guess instructions will be most likely the same)
hir0pro has quit [Ping timeout: 480 seconds]
<daniels>
bipul: you can probably get more help from #linux and #freebsd as it's becoming rather off-topic here, but in general when your build fails because it tells you a dependency is missing (or command/header/library not found), you need to find that dependency and build and instal it
<daniels>
this will likely take you ... quite some time
<shadeslayer>
hi! I was wondering if one of the sysadmins could help me and enable the `:junit_pipeline_screenshots_view` flag on gitlab? :D
<bipul>
ok
<daniels>
shadeslayer: 'The feature flag was removed and was made generally available in GitLab 13.12.'
<daniels>
we just need to upgrade really, which makes sense now that .1 is out
<shadeslayer>
daniels: fdo has 13.11
<daniels>
yeah, 13.12.1 is now released
<daniels>
I'm not going to drive production in my current state tbh, but hopefully everything's passed by the weekend and I can do it then
<omegatron>
bipul: but you can join me in #lfs if you still need help ..
<shadeslayer>
daniels: ack, I have no idea of the work involved for either upgrading or enabling a feature flag, so I guess I'm gonna have to wait :)
<daniels>
shadeslayer: heh, the upgrade is pretty mechanical and should be done anyway :)
<daniels>
but best to do it on a weekend regardless in case anything gets more on fire
aaronp has joined #freedesktop
<bipul>
OKay time to compilenow
<bipul>
I will update you soon
<kusma>
daniels: I've been told deploying on fridays is widely considered a good idea ;)
scorpion2185[m] has joined #freedesktop
<shadeslayer>
can confirm, have had multiple successful deployments at 5 PM on a Friday
_whitelogger has joined #freedesktop
MrCooper has quit [Remote host closed the connection]
MrCooper has joined #freedesktop
hir0pro has joined #freedesktop
hir0pro has quit []
ds- is now known as ds`
node1 has joined #freedesktop
bipul has quit [Read error: No route to host]
ds` has quit [Quit: ...]
ds` has joined #freedesktop
arekm has joined #freedesktop
arekm has quit []
arekm has joined #freedesktop
alanc has quit [Remote host closed the connection]
arekm has quit []
alanc has joined #freedesktop
arekm has joined #freedesktop
arekm has quit []
arekm has joined #freedesktop
arekm has quit []
arekm has joined #freedesktop
ngcortes has joined #freedesktop
<ndufresne>
bentiss: struggling with yet more failing job, without any obvious reason, ERROR: Job failed (system failure): wait: remote command exited without exit status or exit signal
<ndufresne>
ERROR: Job failed (system failure): wait: remote command exited without exit status or exit signal
node1 has quit [Remote host closed the connection]
hir0pro has joined #freedesktop
hir0pro has quit [Quit: Konversation terminated!]
hir0pro has joined #freedesktop
hir0pro has quit []
<daniels>
ndufresne: I'm afraid we have no idea at all about how macOS works
<daniels>
and no access to that machine either
<ndufresne>
I don't think it failed on that machine, I think it failed in some gitlab internals there
<daniels>
no, that's on the machine
<ndufresne>
the process we run is very verbose when it fails
<ndufresne>
well, it's gitlab runner code that failed then ?
<daniels>
well yeah, something went wrong in gitlab-runner, presumably in its process monitoring
<ndufresne>
note, I have just no clue, if there is nothing on the server, then indeed, someone need to access that machine
<ndufresne>
if I have access, I forgot how to do so, but I don't think I have access
<daniels>
that message comes directly from the macOS gitlab-runner
<daniels>
the GitLab service doesn't execute and monitor remote commands, that's the runner
<ndufresne>
but it could be a side effect of some server error .. I have no idea
<daniels>
it's not
<daniels>
could be something like Parallels crashing
<ndufresne>
thing is that except for the sever, I doubt anything have change on these runners
<ndufresne>
unless they are running out of disk space or something
hir0pro has joined #freedesktop
<daniels>
I don't know, all I can tell you is that 'remote command exited without status or exit signal' isn't anything to do with the service, because neither gitlab.fd.o nor gitlab-runner executes commands remotely and doesn't get an exit status
<daniels>
that happens when the gitlab-runner process on the macOS machine is executing commands through Parallels
<daniels>
the only interaction is that gitlab-runner receives a job ID and job definition, pulls artifacts + git repo from the remote server - then executes every command locally without checking back at every stage (since that would be mad inefficient) - it streams logs back through HTTP as it goes, then when it's done it uploads artifacts and sends back a job status
hir0pro has quit [Ping timeout: 480 seconds]
<Lyude>
is something up with cgit?
<Lyude>
I can't seem to pull from any of the drm branches
<imirkin>
feels pretty slow to respond.
<emersion>
daniels, can we mention "freedesktop infra" in the topic? just to make it clearer it's about the infra, not specs
<imirkin>
(as in, hasn't responded since i just tried it)
<Lyude>
daniels: btw ^
<Lyude>
must have just happened because I pushed something to drm-misc-next like 10 minutes ago
<imirkin>
you killed it!
<Lyude>
I have no regrets!
<imirkin>
;(
<Lyude>
bentiss: also btw ^
* daniels
looks
<daniels>
machine kicked
<imirkin>
it's baaack! thanks
<daniels>
np
danvet has quit [Ping timeout: 480 seconds]
ngcortes has quit [Remote host closed the connection]
<robclark>
btw, what is the recommended way to shutdown irc channel on freenode and point folks at OFTC (other than the obvious step of setting /topic)?
<imirkin>
daniels: cgit super slow again =/
thelounge26 has joined #freedesktop
Guest102 has quit [Ping timeout: 480 seconds]
<FLHerne>
You could add an entry message to ChanServ, but obviously that's vulnerable to any future round of hijacking