You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
this requires knowing which csources hash was used to build a particular commit
future csources2 should have a commit hash version controlled in nim repo so we can programmatically access it (EDIT: indeed, see nimBuildCsourcesIfNeeded in 1.5.1)
EDIT
for new nim versions, use . ci/funs.sh && nimBuildCsourcesIfNeeded (which also already handles caching)
Digger can:
build and test D from git
build older versions of D
build D plus forks and pending pull requests
bisect D's history to find where regressions are introduced (or bugs fixed)
timotheecour
changed the title
program to build nim at any revision (cf D's digger); useful for git bisect
nim-digger: program to build nim at any revision (cf D's digger); useful for git bisect
Dec 6, 2020
timotheecour
changed the title
nim-digger: program to build nim at any revision (cf D's digger); useful for git bisect
nim-digger: program to build nim at any revision (including forks/PRs) (cf D's digger); useful for git bisect
Dec 6, 2020
note
EDIT
. ci/funs.sh && nimBuildCsourcesIfNeeded
(which also already handles caching)git fetch --tags
andgit tag
and finding the latest tag, the using a table lookup to identify the appropriate csources hash. Sadly necessary because of lack of prior design but not very complicated (followup here for this: nim-digger: program to build nim at any revision (including forks/PRs) (cf D's digger); useful for git bisect #332)links
in D: https://github.com/CyberShadow/Digger
links
choosenim devel --latest
fails build dom96/choosenim#256 (comment)The text was updated successfully, but these errors were encountered: