| 26 Apr 2025 |
 raitobezarius | But then you are not testing the releng but something else | 21:56:18 |
 jade_ | um. that's just an aarch64 mac and an x86 linux box | 21:56:19 |
| jade_ | but also | 21:56:25 |
| jade_ | the main type of not working that releng might do is in fact in the vein of the manual upload not working | 21:56:48 |
 KFears (burning out) | It's also an x86 mac and aarch 64 linux box | 21:56:52 |
| jade_ | and git push bits not working | 21:56:54 |
| KFears (burning out) | * It's also an x86 mac and aarch64 linux box | 21:56:59 |
| jade_ | x86 mac is rosetta | 21:57:00 |
| jade_ | aarch64 linux is a vm | 21:57:05 |
| KFears (burning out) | Well, I don't have a Mac at all, and I'm not amazed at the prospect of having to own one to be able to run a local environment | 21:57:47 |
| jade_ | i have these four systems on my desk at work in the form of a mini pc and a macbook. but regardless. that is besides the point. without building everything you can still test something meaningful! | 21:57:57 |
| KFears (burning out) | The whole point of local environment is to be local | 21:58:02 |
| raitobezarius | I don't think any other arc than the one available truly matters in releng, perfect is the enemy of good, etc. | 21:58:05 |
| KFears (burning out) | Yes, so I'm not "not testing the releng but something else" | 21:58:39 |
| raitobezarius | The four systems are only required for staging and production release process | 21:58:58 |
| jade_ | testing the building of the manual is a reasonable thing to do. testing exclusively the git bits is also a reasonable thing to do. you could also add a smaller release target. idk | 21:59:14 |
| jade_ | there's many things that can be done here which do not require the entire setup. yes they are not 100% coverage but they are much better than 0% coverage | 21:59:41 |
| raitobezarius | In reply to @kfears:matrix.org
Yes, so I'm not "not testing the releng but something else" I am still not sure I understand what you mean by sidestepping n-e-j but it is an integral part of the process, it doesn't require the four systems | 21:59:59 |
| raitobezarius | Cutting the process somewhere is fine but ideally it should not be altering the process somewhere | 22:00:27 |
| KFears (burning out) | Yes it does, the build+upload uploads all 4 permutations | 22:01:04 |
| jade_ | depends on the target! | 22:01:13 |
| jade_ | the manual target does not | 22:01:19 |
| jade_ | target x86_64-linux_only manual somethign something | 22:01:36 |
| KFears (burning out) | I mean, I might be able to just push the manual target tomorrow if that's any useful | 22:01:37 |
| KFears (burning out) | But like | 22:01:39 |
| KFears (burning out) | That's like 10% of what is needed to test | 22:01:59 |
| jade_ | python -m releng build --profile x86_64-linux-only --target manual | 22:02:15 |
| jade_ | well yes, but testing the entire thing is unrealistic to start off with as a goal! | 22:02:26 |
| KFears (burning out) | And it also tests the happy path | 22:02:34 |
| KFears (burning out) | If I have a week of actively working on it, I'll do it | 22:02:57 |
