| 19 Jan 2025 |
 Tristan Ross | You can use the --keep-failed flag and then try debugging it through the tmp directory it put the build in. | 15:06:32 |
 WeetHet | The environment isn't preserved though | 15:07:41 |
| Tristan Ross | In reply to @weethet:catgirl.cloud
The environment isn't preserved though It saves the environmental variables | 15:08:20 |
| Tristan Ross | You can source those | 15:08:28 |
| WeetHet | Wait it does? | 15:08:44 |
| Tristan Ross | Yes | 15:08:51 |
 emily | what would you do to debug/fix it that wouldn't change the original derivation anyway? | 15:08:57 |
| Tristan Ross | env-vars is the file | 15:09:10 |
| WeetHet | Skipping tests that require network/flaky tests | 15:09:33 |
| WeetHet | To be fair, it's probably a non-issue when you have something like crate2nix | 15:10:33 |
| WeetHet | * To be fair, it's probably a non-issue when you have something like crate2nix, since rebuilds don't take that much | 15:10:44 |
| emily | fair enough | 15:11:04 |
| WeetHet | I still wish there was a way to make each phase it's own derivation without needing to copy the build folder ten times | 15:11:47 |
