Message6864
Hello John,
Yes issue2550964 sounds suspiciously like the same problem that that was
causing the incorrect history to be shown, which was in turn causing the
traceback to be shown.
Doing yet more investigation seems to reveal that the problem resulting
in the traceback was indeed fixed by commit:
hg:1e4c45a4254b7e3c0cba50c86e24f995e63d3509
git:936c7ad852555644370dcb5d2abc520b10eb7e24
So I think this issue can be closed again in favour of issue2550964
Apologies for the noise in reopening this issue.
SeeYa,
John.
On 19/1/20 1:36 pm, John Rouillard wrote:
>
> John Rouillard added the comment:
>
> Jerrykan/John:
>
> In reading your description, it looks like the problem is that the
> history is being updated when it shouldn't. The rollback from the
> failure should result in no change to history. But from your
> description it looks like the history is updated. Is this correct?
>
> issue2550964 describes something similar, but it's a temporary/cosmetic issue.
>
> -- rouilj
>
> (sending via email because tracker is throwing an error at the moment). |
|
Date |
User |
Action |
Args |
2020-01-20 02:18:25 | jerrykan | set | recipients:
+ jerrykan, ber, rouilj, antmail |
2020-01-20 02:18:25 | jerrykan | link | issue2550612 messages |
2020-01-20 02:18:24 | jerrykan | create | |
|