hmpffff_ has joined #nixos-borg
hmpffff has quit [Ping timeout: 260 seconds]
cole-h has quit [Quit: Goodbye]
orivej has quit [Ping timeout: 272 seconds]
hmpffff has joined #nixos-borg
hmpffff_ has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-borg
orivej has quit [Ping timeout: 240 seconds]
orivej has joined #nixos-borg
orivej has quit [Ping timeout: 256 seconds]
<
MichaelRaskin>
Hm, it is still possible for evaluations to create no build jobs?
<
LnL>
what do you mean exactly
<
MichaelRaskin>
Looking at ofborg grafana
<
MichaelRaskin>
Apparently the last evaluation to finish has not created any build jobs.
<
LnL>
checks complete and builds received looks pretty 1 to 1 to me
<
MichaelRaskin>
Oh, evaluations in the evaluation count graph are single steps of eval checks?
<
LnL>
you mean in progress evals?
<
MichaelRaskin>
Yes
<
LnL>
no I think that's one step per eval
<
LnL>
but if the corresponding build job takes 0.1s to figure out it can't build anything nothing in progress might show up on that graph
<
MichaelRaskin>
That's true.
<
MichaelRaskin>
But the eval finishing around 10:55 also did not lead to a Check Complete (if I read the graph correctly)
<
MichaelRaskin>
(10:55 UTC)
<
LnL>
I think that's the same data
<
LnL>
just represented differently, with the in progress graph you can't really see when something new started unless the queue was empty
<
LnL>
pending went down by one and there's a tick for both checks and builds
<
LnL>
this the time range you're talking about?
<
MichaelRaskin>
Hmmm
<
MichaelRaskin>
If I zoom in, more «Check Complete» dots appear
<
LnL>
also I think a mismatch is possible, pretty sure builds are not started if evaluation fails
<
LnL>
I'd love to also get some data from the queue itself tho, this currently only includes the ofborg instances
cole-h has joined #nixos-borg
<
cole-h>
OK, I think I'm satisfied with #482 now. If anybody wants to take another quick look, that would be swell.
<
LnL>
hmm, why doesn't @ofborg autocomplete?
<
cole-h>
Because it's an org, IIRC
<
cole-h>
Try to just `@NixOS`, won't work either
<
cole-h>
But it will still linkify in the preview and comment
<
cole-h>
A better example might be your test org: `@eb6cb83a-cf75-4e88-a11a-ce117467d8ae`
<
cole-h>
Which is why it was suggested ~yesterday to see if we can switch ofborg to a regular user (which GH's docs say is possible)
<
cole-h>
(Maybe 2 days ago -- sense of time is slipping, and I never really had one anyways...)
<
cole-h>
(Only slightly related, but how were those uuid-looking things generated?)
<
LnL>
oh heh, I think that was for testing the maintainer stuff :)
<
cole-h>
Yep, it was :P
* LnL
wonders how you know that
<
LnL>
I barely remember that
<
{^_^}>
eb6cb83a-cf75-4e88-a11a-ce117467d8ae/4ec54bd9-c707-4238-bc46-48596d6d7659#4 (by grahamc, 1 year ago, open): 21ac12f7-d8d0-4058-a9d8-ff1fc1eb09ad
<
LnL>
I wonder how confused somebody would get if you just send them that pr
<
LnL>
uuids everywhere :p
<
cole-h>
I was certainly confused the first time I looked at your profile
* cole-h
sees uuid-looking org
* cole-h
goes to uuid-named org
* cole-h
goes to uuid-named repo and click on uuid-named PR with uuid-body, uuid-contents, and uuid-comments
<
cole-h>
>> ??????????????
<
MichaelRaskin>
Number stations!
<
cole-h>
Basically how it went, until I saw the reference to the RFC
prusnak has left #nixos-borg [#nixos-borg]