> If you want it fixed, you need to find out 1) was it actually fixed in 0.174
No, it was actually fixed in 0.173, and is ridiculously easy to reproduce in 0.172.
> and 2)
> if it was, what version broke it again.
Working on that now.
Edit 1: The issue was still fixed as of 0.187.
Edit 2: 0.194 exhibits the issue once more.
Edit 3: 0.190 exhibits the issue once more.
Edit 4: 0.189 exhibits the issue once more.
Edit 5: 0.188 exhibits the issue once more. Re-testing with 0.187 again verifies that the issue was still fixed as of 0.187, so the behavior regressed between 0.187 and 0.188.
Edit 6: An archived daily build from 14 July 2017, roughly halfway between 0.187 and 0.188, built off of changeset 45fdeec9(...), exhibits the issue once more.
Edit 7: An archived daily build from 7 July 2017, built off of changeset c338b974(...), exhibits the issue once more.
Edit 8: An archived daily build from 3 July 2017, built off of changeset 4ea3dde4(...), exhibits the issue once more.
Edit 9: An archived daily build from 22 June 2017, built off of changeset a202e211(...), does not exhibit the issue.
Edit 10: An archived daily build from 24 June 2017, built off of changeset 4a4883dd(...), does not exhibit the issue.
Edit 11: An archived daily build from 26 June 2017, built off of changeset 54567f76(...), exhibits the issue once more.
Edit 12: An archived daily build from 25 June 2017, built off of changeset fb61e98c(...), exhibits the issue once more.
We can therefore infer from this that the issue was re-introduced in one of the commits made between 24 June 2017 and 25 June 2017.
Edit 13: Changeset d09534c3(...) from 24 June 2017 does not exhibit the issue.
Edited by MooglyGuy (10/04/18 11:18 PM)
|
Index 
Flat 
Re: Why does MAMEUI need to continue to exist? (nt)
Reply
