| 28 May 2021 |
 cdepillabout | That's a good point. I assumed we did, but I dunno. I don't personally care about them. | 09:03:08 |
| cdepillabout | Although mergeable and maintained are both failing now. | 09:03:31 |
| cdepillabout | Err, maybe it is just maintained that is failing? | 09:05:09 |
| cdepillabout | Sometimes I have a hard time figuring out exactly what is failing on Hydra, especially when build statuses get cached. | 09:06:04 |
|  aria joined the room. | 09:08:34 |
| cdepillabout | * Sometimes I have a hard time figuring out exactly what is failing on Hydra, especially when builds incorrectly fail, and then build statuses get cached. | 09:10:07 |
 maralorn | Well, if there are problems you can obviously pass on the torch. | 09:10:48 |
 sterni (he/him) | cdepillabout: sometimes the status of the aggregate jobs is stale and you need to restart (just) the aggregate job | 09:39:25 |
| sterni (he/him) | but nevertheless I can look into it :) | 09:39:35 |
| sterni (he/him) | and do the merge of course | 09:39:55 |
| sterni (he/him) | I would like to take some time the next two weeks going over the list of jobs in mergeable if you guys have any ideas on how to expand / change the list I'd be interestetd to hear it | 09:41:34 |
|  zwro changed their display name from zzz to zwro. | 11:42:19 |
| cdepillabout | In reply to @sternenseemann:systemli.org
cdepillabout: sometimes the status of the aggregate jobs is stale and you need to restart (just) the aggregate job Ah, I was actually wondering about that. Restarting the mergeable or maintained job should also restart all of its failed child jobs? | 12:09:48 |
| cdepillabout | I had thought that I had tried that once and it didn't work, but maybe I was just mistaken. | 12:10:05 |
| sterni (he/him) | In reply to @cdepillabout:matrix.org
Ah, I was actually wondering about that. Restarting the mergeable or maintained job should also restart all of its failed child jobs? no, that's the point it doesn't restart any of the aggregated jobs | 12:10:32 |
| sterni (he/him) | but if something was fixed by restarting for example the aggregate job doesn't get updated so you'd need to restart it | 12:10:52 |
| sterni (he/him) | so restarting it only helps with stale failures | 12:11:13 |
| maralorn | I mean that’s not even special for aggregate jobs. All jobs don‘t update automatically if they failed because of a broken dependency and then that dependency got fixed. | 12:12:00 |
| cdepillabout | Ah, I see what you're saying. So if the aggregate job has a child job that has failed, you need to restart both the failed child job and the aggregate jobset? | 12:12:19 |
| sterni (he/him) | yep | 12:12:28 |
| cdepillabout | Man, that's somewhat annoying | 12:12:50 |
| maralorn | In reply to @cdepillabout:matrix.org
Man, that's somewhat annoying Yeah, the most annoying part is, that you can‘t selectively bulk restart jobs. | 12:16:24 |
| cdepillabout | Ah, yeah, so you have to go to each failed job and manually restart it. | 12:17:03 |
| maralorn | Or you restart all failed jobs, but that will produce a lot of unnecessary work. | 12:17:51 |
| cdepillabout | 
Download image.png | 12:20:01 |
| cdepillabout | Oh, good point. I see that there is the Restart all failed builds option. Although you're completely right, that would create a lot of unnecessary work. | 12:20:46 |
| sterni (he/him) | may be a good shout though when we have a lot of dubious build failures again | 12:21:40 |
| cdepillabout | At some point in the not-too-far future, maybe we can correctly mark all darwin/aarch64 builds that don't work broken, so our "failing jobs" will really be unexpected failures. In that case, I imagine there will be a lot less failed builds, so restarting all failed builds should cause much less work. | 12:22:31 |
| sterni (he/him) | seems like we are getting almost none of the queue because three jobsets have much more queued builds than us :'( | 12:22:47 |
| sterni (he/him) | cdepillabout: yeah I'm planning-ish to work on that | 12:23:17 |
