| 31 Oct 2025 |
|  connor (he/him) (UTC-5) changed their display name from connor (he/him) (UTC-7) to connor (burnt/out) (UTC-7). | 03:16:46 |
| 2 Nov 2025 |
| connor (he/him) (UTC-5) changed their display name from connor (burnt/out) (UTC-7) to connor (burnt/out) (UTC-8). | 08:12:45 |
|  amadaluzia joined the room. | 22:34:23 |
| 4 Nov 2025 |
|  ivy joined the room. | 02:51:55 |
| ivy | why do check and installCheck phases happen in that order and is there any dependency on the check results for building packages generally? | 02:59:32 |
 Winter | installCheck needs to be done after install because it depends on the ~final version of $out, and no, there’s generally not… checkPhase is like unit tests and the like | 03:01:43 |
| ivy | so there wouldnt be any reason why we couldn't move checks into a sub derivation, that depends on the parent derivations output | 03:07:40 |
| ivy | aka | 03:07:58 |
| ivy | llvm is llvm and llvm.checks,
and all things that depend on llvm have a checks output that depends on llvms checks, so checks can be parrallelised? | 03:08:36 |
| ivy | instead of if a checkPhase fails on hydra it messes up the entire build process and shortcircuits all dependencies on it, | 03:09:35 |
| ivy | and also takes a long time | 03:09:42 |
| ivy | 
Download image.png | 03:15:37 |
| ivy | like this | 03:15:38 |
| Winter | can’t easily go from $out to a test-ready build env though | 03:17:30 |
| Winter | that’s the issue | 03:17:33 |
| Winter | lots of tests depend on the build environment being set up | 03:17:39 |
| Winter | and artifacts being already built etc… | 03:17:49 |
| ivy | can we make that build env passed into that check? | 03:19:23 |
| ivy | like the build env is copied into that new check env | 03:20:05 |
| ivy | 
Download image.png | 03:27:30 |
| ivy | this perhaps then | 03:27:30 |
| ivy | where mid-build-env contains the built artifacts minus the checkPhases | 03:28:12 |
| ivy | so it's more parallelised | 03:29:34 |
| ivy | Winter: thoughts? | 03:30:15 |
 dish [Fox/It/She] | In reply to @ivy:faggot.sh
llvm is llvm and llvm.checks,
and all things that depend on llvm have a checks output that depends on llvms checks, so checks can be parrallelised? i mean if llvm checks are failing i would want stuff to block on that | 03:46:57 |
| dish [Fox/It/She] | since compiler errors are not good | 03:47:06 |
| ivy | it would still block, just not block building them simultaneously | 03:47:49 |
| ivy | like stuff still builds while checks are going on | 03:48:05 |
| ivy | and also would be helpful for compiler understanding of why the test fails when dependencies fail | 03:48:46 |
| dish [Fox/It/She] | yeah what im saying is i'd rather block on checks succeeding for critical deps like compilers | 04:07:16 |
