> However: > 'make check2' fails for dmtcp also without --with-record-replay.
Yep. It's still internally inconsistent, while we do some final development. We'll have all of that working painlessly at the release (and if there are bug reports, we'll be quick to fix them). Thanks for the feedback, - Gene On Fri, Apr 13, 2012 at 09:41:09PM +0200, Matzi Kratzi wrote: > Do not worry. I have been waiting for something like this for years - > I can wait a few more. > > However: > 'make check2' fails for dmtcp also without --with-record-replay. > > Best regards > Mats > > On Fri, Apr 13, 2012 at 9:01 PM, Gene Cooperman <[email protected]> wrote: > > I'm afraid that FReD is not really at the formal release stage, yet. > > We had expected to release an early version in the last month or two -- > > but then decided to wait until some additional things were fixed. > > So, FReD is currently in an internally inconsistent state. > > When it is ready, we'll also put up an announcement on the DMTCP > > web page about FReD. > > > > (For others who may read this, FReD stands for "Fast Reversible > > Debugger". It is based on the ability of DMTCP to checkpoint and > > restart an entire gdb session. We are hoping for a formal release > > in the next month or so.) > > > > Thanks very much for your interest. Sorry that the FReD project > > hadn't made clear its status. > > > > Best wishes, > > - Gene, and the DMTCP team > > > > > > On Fri, Apr 13, 2012 at 08:51:44PM +0200, Matzi Kratzi wrote: > >> Hi, > >> dmtcp and FReD are interesting projects. > >> > >> I fetched the code from svn a few hours ago and try to run make check > >> and make check2 and always some of the tests fail. > >> > >> check2 always fails. > >> > >> Are these tests expected to work? > >> > >> Thank you for very interesting projects. I look forward to using them. > >> > >> /Mats > >> > >> $ uname -a > >> Linux planet 3.0.0-17-generic-pae #30-Ubuntu SMP Thu Mar 8 17:53:35 > >> UTC 2012 i686 athlon i386 GNU/Linux > >> $ > >> > >> ./configure |tee conf-no-parameters.log > >> make |tee make-no-parameters.log > >> make check|tee make-check-no-parameters.log > >> make check2|tee make-check2-no-parameters.log > >> > >> > >> After configuring --with-record-replay, make check always fails, but > >> not always the same way. > >> dmtcp5 always fails. > >> > >> I collected some logs. > >> > >> make clean > >> ./configure --with-record-replay|tee conf-record-replay.log > >> make -j3|tee make-record-replay.log > >> make check|tee make-check-record-replay.log > >> make check|tee make-check-record-replay.log > >> make check|tee make-check-record-replay_secondRun.log > >> make check|tee make-check-record-replay_thirdRun.log > >> make check|tee make-check-record-replay_forthRun.log > > > > > > > >> ------------------------------------------------------------------------------ > >> For Developers, A Lot Can Happen In A Second. > >> Boundary is the first to Know...and Tell You. > >> Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! > >> http://p.sf.net/sfu/Boundary-d2dvs2 > > > >> _______________________________________________ > >> Dmtcp-forum mailing list > >> [email protected] > >> https://lists.sourceforge.net/lists/listinfo/dmtcp-forum > > ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Dmtcp-forum mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dmtcp-forum
