8am or 9am is often a good time to check out IMP as it is the last night tests plus fixes for anything that was discovered to be broken :-)
Would providing a tag/branch in git that is a more formal representation of that be useful to people? Specifically, have a "nightly" branch which is the version used in the last nightly test + any fixes for specific problems discovered.
On Wed, Jun 26, 2013 at 9:53 AM, Jan Kosinski kosinski@embl.de wrote:
> OK, updated to 2.0.0-588-g04dc1f9 and I can enjoy functional IMP again > :-) > > I think the todays commits from drussel and maxbonomi made a difference, > thanks a lot! > > Jan > > > n 06/26/2013 05:14 PM, Ben Webb wrote: > > On 6/26/13 7:45 AM, Jan Kosinski wrote: > > I have problems with compiling recent dev versions of IMP. The last > version I can build successfully is 2.0.0-544-gb4dfefb. > > The version 2.0.0-545-ga3aaf4a is the first that crashes > > ... > > Is it a bug? The dev logs from > http://salilab.org/imp/nightly/logs/develop/20130625/x86_64-intel8/ seem > ok. So maybe I build IMP wrong way? > > > If you build from develop, you're going to hit compile problems from time > to time, particularly when lots of things are going on, like right now. I'd > suggest you check http://salilab.org/imp/nightly/results/ (as you seem to > be doing already) and updating only when things look good there. The logs > you point to are for 954614a11a, which is a few commits after yours, so > most likely the decorator problems you ran into were fixed by that point. > > Ben > > > > -- > Jan Kosinski, PhD > Structural and Computational Biology Unit > European Molecular Biology Laboratory (EMBL) > Meyerhofstrasse 1 > 69117 Heidelberg > Germany > > > _______________________________________________ > IMP-users mailing list > IMP-users@salilab.org > https://salilab.org/mailman/listinfo/imp-users > >