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.Dismiss alert
This updates the comment about GitoxideLabs#1622, including by adding links to
Git mailing list posts by Aarni Koskela, who discovered the bug
that turns out to be the cause of this, and Patrick Steinhardt, who
analyzed the bug and wrote a fix (currently in testing), as well as
GitoxideLabs#1622 (comment),
which summarizes that and reports on its connection to GitoxideLabs#1622.
This also narrows partial suppression of the failing test code
(which consists of conditionally using `parse_spec_no_baseline`
instead of `parse_spec` in some assertions) so that it is only done
if Git is at one of the versions that is known to be affected.
If any future Git versions are affected, such as by the currently
cooking patch not being merged as soon as I expect, then this could
potentially fail on CI again. But that is something we would
probably want to find out about.
0 commit comments