[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [cdt-dev] bisecting regression ranges
|
Hi Nathan,
One way I've done before is to copy/paste the target file (you have to rename it also inside the file), fix the dependencies and keep that file untracked. You can set this as your target platform probably for a lot of commits you are bisecting.
The only archives of builds are the few last builds on Hudson and the milestones.
Hope this helps,
Marc-Andre
________________________________________
From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] on behalf of Nathan Ridge [zeratul976@xxxxxxxxxxx]
Sent: Thursday, 07 July 2016 2:26 AM
To: CDT Mailing List
Subject: [cdt-dev] bisecting regression ranges
Hi,
Sometimes, when investigating a regression, debugging the problem directly (without knowing where to look for it) can be quite difficult. In these cases, it really helps to identify which commit caused the regression.
Given a "known good" revision (a previous release which does not suffer from the regression) and a "known bad" revision (e.g. head of master branch which suffers from the regression), the commit that caused the regression can be identified by testing O(log N) revisions (where N is the number of commits between "known good" and "known bad"), using binary search.
For another project that I work on, there is an archive of builds for every revision, and a tool that guides you in performing this process by downloading relevant revisions in turn and running them, and asking you if the current one exhibits the problem.
Is there some similar way to bisect a regression range for CDT? I tried using "git bisect", but I had trouble building older revisions, due to mismatches between CDT and Platform code. For example, for the revision from which 8.8 was branched (which is the "known good" revision for a particular regression I'm investigating), I was unable to build that using any of the available target platforms.
It would be particularly hepful if there were an archive of builds - if not for every revision, then at least for every nightly build. Is there such an archive somewhere?
Thanks,
Nate
_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev
