Windows users... recent issues?

Software darktable
4

I’ve answered a bit on github, but I can give more hints here too.

3.1.0+769~g1ef4476cf - this is the current master, known by you to be bad.
v708 is known to not be affected but you don’t know the hash, so let’s do it by math 769-708=61 (so 61 commits ago). since my git revisions-fu is weak i’ll use bruteforce and see the last line in git log:
git log --oneline -61
this gives me:90611440b (might be different for you)

So now you start bisecting!

do it like this:

  1. make sure you are on latest master
  2. enter folowing commands:
  git bisect start
  git bisect bad
  git bisect good 90611440b
  1. now rebuild darktable (with clean install dir etc) and test if you can replicate the problem. if you can, issue command git bisect bad (without any commit hash) and if you can’t (so the version is good) - issue git bisect good
  2. repeat step 3 until git tells you exactly which commit caused problem.

whit that knowledge go to github issue and describe process you’ve taken + results of your bisect hunt

now it’s time to reset your git repo with: git bisect reset

And you’re done! this will be significantly faster than trying each commit by hand as it will perform binary search on troubling commits.

4 Likes