The savegame breakage bisection thread

[cybersphinx]

Take a risk and pick the most suspicious of the remaining commits: d818ff5a195d9e010edf9dd060c9553a07dfec5c
If this is it, we're finished, if not, we've added an extra step.
http://wz2100.net/~cybersphinx/3200/war ... dfec5c.exe
http://wz2100.net/~cybersphinx/3200/war ... dfec5c.zip

The boring alternative: 7649bfe27680cfd649fcb863f38e6745382d773c
http://wz2100.net/~cybersphinx/3200/war ... 2d773c.exe
http://wz2100.net/~cybersphinx/3200/war ... 2d773c.zip

[zany]

Take a risk and pick the most suspicious of the remaining commits: d818ff5a195d9e010edf9dd060c9553a07dfec5c
If this is it, we're finished, if not, we've added an extra step.
http://wz2100.net/~cybersphinx/3200/war ... dfec5c.exe
http://wz2100.net/~cybersphinx/3200/war ... dfec5c.zip

The boring alternative: 7649bfe27680cfd649fcb863f38e6745382d773c
http://wz2100.net/~cybersphinx/3200/war ... 2d773c.exe
http://wz2100.net/~cybersphinx/3200/war ... 2d773c.zip

BROKEN & BROKEN
you mean that either https://github.com/Warzone2100/warzone2 ... 3a07dfec5c
perim authored December 02, 2011
or
https://github.com/Warzone2100/warzone2 ... 45382d773c
cybersphinx authored December 02, 2011

broke it? I only see that change log stuff and Txt doc/Makefile.am whatever that is in yours so the fault is with perim?

[zany]

so it is over now? will beta 5 be out today with fixed savegames?

[cybersphinx]

Right, the first one broke it. The second was autopicked by git for being in the middle between the last working and first broken commit (of those previously tested).

Too late today to even start thinking about beta5, especially with just the offending commit and no fix yet. But soon, hopefully.

[zany]

oh I thought you can just roll back that change and it would be fixed

[cybersphinx]

Possibly. But (excepting the things it breaks) that change improves the code, so we'd need a fix for master anyway, and I don't know if anything else now depends on it already. Needs more investigation (and some sleep before that).