@jfernandz https://stackoverflow.com/questions/4713088/how-do-i-use-git-bisect
This is just very basic overview and probably unhelpful.
If you’re familiar with git, you can switch to different points in time (via the dev-branch) to figure out when we last knew things were good. So first, I’d suggest trying to find exactly when that would’ve been.
I’d likely start, using dev-branch as the primary “tester case”
git checkout -b dev-branchIf you haven’t already done so of course.
Then I’d put the branch at the same level as when we pushed out 1.5.10:
git checkout 081d1f4Run your install and see if things worked, if they do:
git checkout dev-branch git bisect start git bisect bad git bisect good 081d1f4Of course the 081d1f4 is the hash of the commit where things were good: this might or might not be the 1.5.10 release, so your mileage may very and may need some more adjustment.
You can find these hashes on https://github.com/FOGProject/fogproject/commits/dev-branch/?after=f7fd3a7a3f188b4540f089a7f38c4d368b53376c+174 using the different pages at the bottom to find a point in time, and they show the hashes on the right and side of each commit.
It will iterate through things and you just mark after each install/test what worked (as good or bad) by testing:
If it still fails, you’d run git bisect bad, if it succeeds, you would run git bisect good each iteration.
It’s tedious I know. but it will help us find the exact point things broke and hopefully from what (maybe it’s something we did, maybe something within ipxe, but gives us a starting point to test things out.)
Thanks