You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.
Is this still relevant? I saw my name at the top of https://dev.golang.org/reviews with it attached to this, so I wanted to see if it still needs attention from me. The last comments on the review were mine.
Gotcha. How many commits do you want to go back? Also, I know there was previously a discussion about the maintner package, is the current CL still the proper way to implement this change or does it now need to be made somewhere else?
From: Brad Fitzpatrick [mailto:firstname.lastname@example.org]
Sent: Thursday, December 7, 2017 12:56 PM
To: golang/go <email@example.com>
Cc: Mike Lloyd <firstname.lastname@example.org>; Comment <email@example.com>
Subject: Re: [golang/go] x/build: make trybots refuse to test a commit that's too old (#19664)
This would still be nice to have done, but it should be based on number of git commits back rather than time.
Also, the CL above has merge conflicts and needs to be rebased.
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#19664 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AHMEsUyR7O5ERi7myqIR9GzzQlCRY1cYks5s-EK8gaJpZM4Ml8j_>.
It might need to be some combination of N commits back and time back, and maybe whether the build was broken & fixed in the meantime, but that's kinda tricky.
We could start with just something like it's okay to run trybots it's fewer than 10 commits old OR less than 5 days. But once it's older than 10 commits AND older than 5 days, then we make them rebase? We can adjust the thresholds later.