| 11 Dec 2021 |
andi- | How do I tell hydra to run for each branch of a git repo without declaring those manually? | 21:01:08 |
| 13 Dec 2021 |
| ldesgoui joined the room. | 00:20:39 |
| 14 Dec 2021 |
@grahamc:nixos.org | my PR moving from perlcritic level 3 to level 2 is ready: https://github.com/NixOS/hydra/pull/1045 | 15:19:12 |
@grahamc:nixos.org | perlcritic level 1: https://github.com/NixOS/hydra/pull/1075 | 16:46:55 |
| 20 Dec 2021 |
@grahamc:nixos.org | I have a PR here about hydra-notify and the defunct buildQueued event, with a WIP patch to re-enable that event: https://github.com/NixOS/hydra/pull/1083 it involves a discussion about pushing 100k+ NOTIFY events through postgres | 18:49:06 |
| 21 Dec 2021 |
toonn | Should I still refrain from putting load on the Linux Hydra or have all the important release-related cycles finished? | 19:07:41 |
@grahamc:nixos.org | go for it | 20:35:29 |
@grahamc:nixos.org | (but, see #infra:nixos.org for the nixos.org hydra :)) | 20:35:53 |
toonn | Oh, I keep confusing these channels >.< (Thought pattern's something like this, "Where should I go, Infra or Hydra, I think Infra but I always go to the wrong channel so, Hydra of course \o/") | 20:39:26 |
@grahamc:nixos.org | no worries :) | 20:40:11 |
Rick (Mindavi) | grahamc (he/him): any opinions on the ca-derivations PR? Or waiting for the RFC, or something else? | 20:44:06 |
| 22 Dec 2021 |
| tpw_rules joined the room. | 21:56:49 |
tpw_rules | hi. it seems like there's something wrong with the build dependencies tab. e.g. here https://hydra.nixos.org/build/161612951#tabs-build-deps any job i click on goes to an arbitrary other job, not the one the link says it is for. the log links work, but they have the wrong job name | 21:58:47 |
tpw_rules | okay i take it back it's not all of them. but e.g. on that page gnugrep goes to git, bootstrap-tools goes to gdk-pixbuf, | 22:03:26 |
| 23 Dec 2021 |
@grahamc:nixos.org | that is ineresting | 00:43:43 |
@grahamc:nixos.org | I wonder if it is picking the build for which that step was built for | 00:43:55 |
@grahamc:nixos.org | ie: gnugrep was forced to be built as a result of the queue runner trying to build git | 00:44:19 |
@grahamc:nixos.org | if you click the log link it takes you to the correct log | 00:46:25 |
tpw_rules | just wanted to be sure it's not like, database corruption | 02:20:27 |
tpw_rules | (and want to know how long it takes hydra to build chromium) | 02:20:41 |
@grahamc:nixos.org | I briefly tried to make that page render with D3 but I'm don't know how to make it be a reasonably useful thing | 02:42:06 |
@grahamc:nixos.org | here is the dataset: https://gist.githubusercontent.com/grahamc/78f231db3de572a2462d5b6df4362952/raw/3bd28308b6572676122974b572204d91a540d548/t.json | 02:42:10 |
@grahamc:nixos.org | using https://www.d3-graph-gallery.com/graph/network_basic.html | 02:42:20 |
tpw_rules | the problem is the chromium job there is just a wrapper that writes a couple scripts. i need to know the build time of chromium-unwrapped but clicking on it just goes to "puppeteer" | 02:46:06 |
@grahamc:nixos.org | hydra=> select * from buildsteps where build = 161613001 and stepnr = 1;
-[ RECORD 1 ]------+---------------------------------------------------------------------------------
build | 161613001
stepnr | 1
type | 0
drvpath | /nix/store/jkg3bff4hscmzvcz8y4pwx6nvlhxyp7q-chromium-unwrapped-96.0.4664.110.drv
busy | 0
status | 0
errormsg |
starttime | 1639840844
stoptime | 1639848563
machine | root@74cdda1e.packethost.net
system | x86_64-linux
propagatedfrom |
overhead | 194474
timesbuilt | 1
isnondeterministic |
| 02:47:46 |
tpw_rules | so 7719 seconds? | 02:48:47 |
@grahamc:nixos.org | yeah | 02:48:58 |
tpw_rules | not bad | 02:49:17 |
tpw_rules | i assume there is not a public access sql terminal :) thank you | 02:49:30 |
@grahamc:nixos.org | from the puppeteer page you can click Build Steps and it'll show you the duration there too apparently https://hydra.nixos.org/build/161613001#tabs-buildsteps | 02:49:46 |