Re: [Mesa-dev] piglit default main branch results - Re: Rename "master" branch to "main"?
On Tue, 30 Mar 2021 at 01:34, Ilia Mirkin wrote: > https://cgit.freedesktop.org/piglit > > This still displays the "master" branch by default. I think you're > supposed to change ... something ... in the repo, which indicates > which is the default branch. > *jedi handwave* no it doesn't > On Mon, Mar 29, 2021 at 8:31 PM Jordan Justen > wrote: > > I have only seen one issue so far for the piglit default branch > > change. It appears that the piglit patchwork scripting isn't > > configured for the main branch. I think it's long past time to retire > > the piglit patchwork, so I made a request to the admins to do that. I > > think Mesa already retired patchwork. *jedi handwave* it was always retired, nothing to see here, move along please *foom* ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
Re: [Mesa-dev] piglit default main branch results - Re: Rename "master" branch to "main"?
Hi Jordan, https://cgit.freedesktop.org/piglit This still displays the "master" branch by default. I think you're supposed to change ... something ... in the repo, which indicates which is the default branch. Cheers, -ilia On Mon, Mar 29, 2021 at 8:31 PM Jordan Justen wrote: > > On 2021-03-24 23:47:46, Jordan Justen wrote: > > On 2021-03-24 21:14:57, Jason Ekstrand wrote: > > > > > > Jordan, is there any way you can make the script sort by last updated > > > before it > > > re-targets the MRs so they at least stay in the same order? Updating them > > > in MR > > > # order wouldn't be bad either, I guess. > > > > > > > It already does process them sorting by the oldest "update time" > > first, so roughly speaking the order sorted by update time should be > > the same. > > > > I don't know what might happen if 2 MRs were updated within the same > > second. But, the updates are actually a bit slow (maybe ~1 update per > > second), so there doesn't seem to be much risk, as far as I can see, > > of, for instance, 10 updates happening within the same second. > > > > Crucible and piglit are now changed over to using main. > > Piglit has had at least 2 MR's merge to main now: > * https://gitlab.freedesktop.org/mesa/piglit/-/merge_requests/463 > * https://gitlab.freedesktop.org/mesa/piglit/-/merge_requests/497 > > It appears that the "last updated sort order" stayed 100% the same > before and after the script ran to update the open MR branch targets. > > It took ~48 seconds for the script to update 58 piglit merge-requests. > > I have only seen one issue so far for the piglit default branch > change. It appears that the piglit patchwork scripting isn't > configured for the main branch. I think it's long past time to retire > the piglit patchwork, so I made a request to the admins to do that. I > think Mesa already retired patchwork. > > -Jordan > ___ > mesa-dev mailing list > mesa-dev@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/mesa-dev ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
[Mesa-dev] piglit default main branch results - Re: Rename "master" branch to "main"?
On 2021-03-24 23:47:46, Jordan Justen wrote: > On 2021-03-24 21:14:57, Jason Ekstrand wrote: > > > > Jordan, is there any way you can make the script sort by last updated > > before it > > re-targets the MRs so they at least stay in the same order? Updating them > > in MR > > # order wouldn't be bad either, I guess. > > > > It already does process them sorting by the oldest "update time" > first, so roughly speaking the order sorted by update time should be > the same. > > I don't know what might happen if 2 MRs were updated within the same > second. But, the updates are actually a bit slow (maybe ~1 update per > second), so there doesn't seem to be much risk, as far as I can see, > of, for instance, 10 updates happening within the same second. > Crucible and piglit are now changed over to using main. Piglit has had at least 2 MR's merge to main now: * https://gitlab.freedesktop.org/mesa/piglit/-/merge_requests/463 * https://gitlab.freedesktop.org/mesa/piglit/-/merge_requests/497 It appears that the "last updated sort order" stayed 100% the same before and after the script ran to update the open MR branch targets. It took ~48 seconds for the script to update 58 piglit merge-requests. I have only seen one issue so far for the piglit default branch change. It appears that the piglit patchwork scripting isn't configured for the main branch. I think it's long past time to retire the piglit patchwork, so I made a request to the admins to do that. I think Mesa already retired patchwork. -Jordan ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
