<br><br><div class="gmail_quote">On Wed, Feb 27, 2013 at 7:53 PM, Szilárd Páll <span dir="ltr"><<a href="mailto:szilard.pall@cbr.su.se" target="_blank">szilard.pall@cbr.su.se</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div><br></div><div class="gmail_quote"><div class="im">On Wed, Feb 27, 2013 at 6:51 PM, Mark Abraham <span dir="ltr"><<a href="mailto:mark.j.abraham@gmail.com" target="_blank">mark.j.abraham@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br><br><div class="gmail_quote"><div>On Tue, Feb 26, 2013 at 9:31 PM, Szilárd Páll <span dir="ltr"><<a href="mailto:szilard.pall@cbr.su.se" target="_blank">szilard.pall@cbr.su.se</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div>On Tue, Feb 26, 2013 at 5:50 PM, Roland Schulz <span dir="ltr"><<a href="mailto:roland@utk.edu" target="_blank">roland@utk.edu</a>></span> wrote:<br></div><div class="gmail_extra"><div class="gmail_quote">
<div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div>On Tue, Feb 26, 2013 at 10:25 AM, Szilárd Páll <span dir="ltr"><<a href="mailto:szilard.pall@cbr.su.se" target="_blank">szilard.pall@cbr.su.se</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div>
<div dir="ltr">Bump!
<div><br>
</div>
<div>I have not had time to figure out a solution. Does anybody have suggestions on how to fix this?</div></div></div></blockquote></div><div>you simply upload a fixed version. I think the proper fix is that for the git version, git is used to download. It only makes sense to download a TGZ from http if the source is also a tar ball. But I was waiting for us to decide whether we will change regressiontests to a submodule before I change that.</div>
</div></div></div></blockquote><div><br></div></div><div>I see. I would still like to have it fixed asap and would have done it myself, but Mark suggested that one can not simply replace a file.</div><div><div>
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>
<div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div dir="ltr">
<div>I have a serious concern: as nobody has noticed this except me, I think people are simply running the regressiontests (while I do know that many people are using the source from git). I tend to think this is a problem of communication/documentation
and we should try to improve on this aspect. Not only that if the tests are not used it was a half-futile effort to make them work, but knowing how fragile intrinsic-based kernels are, it is also dangerous.</div></div></div>
</blockquote></div><div>According to <a href="https://code.google.com/p/gromacs/downloads/list" target="_blank">https://code.google.com/p/gromacs/downloads/list</a> the 4.6 was downloaded 328. I think this makes this useful. master was only downloaded 15 so it seems that my assumption that it is mostly useful to people with tar ball not git is mostly true.</div>
</div></div></div></blockquote><div><br></div></div><div><div>In general, I don't think we should jump to conclusions just yet because:</div></div></div></div></div></blockquote><div><br></div></div><div>I'm not sure what the conclusion is to which you might be objecting. Users have downloaded the tests, which is a good thing. We haven't had a forest of complaints about it, but we can't know whether that's a good or bad thing.</div>
</div></blockquote><div><br></div></div>This one: "seems that my assumption that it is mostly useful to people with tar ball not git is mostly true".</div></div></div></blockquote><div><br></div><div>People with the gromacs 4.6 tarball got the correctly-working regressiontests-4.6.tar.gz around 328 times. People with the post-4.6 git branch tried to get the broken regressiontests-master.tar.gz many fewer times. We don't know how many people with either did no testing. Shrug.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
AFAIK most advanced users would expect to get a tarball or git code with self-contained README/INSTALL files that provide brief information on, among other things, compilation. As the INSTALL file in the release was not updated, it doesn't mention "make check" & related things.</div>
</div></div></blockquote><div><br></div><div>Sure. But AFAIK nobody else has complained that such files missing, either.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div class="im"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra">
<div class="gmail_quote">
<div><div>- The feature has just been introduced;<br>
</div><div>- I have the feeling that validating a GROMACS build has not been encouraged enough:</div>
<div> - I just realized hat even the release notes do not mention this new feature (added).<br></div></div><div> - The INSTALL file does not mention it;</div><div> - It might be a good idea to write a separate email about it to the mailing list (will do it, but I'd prefer to have the issue fixed first);</div>
<div><div>- As the auto-download with git source has been buggy some might have simply switched to simply checking out the regressiontests repo exactly because of the bug.</div></div></div></div></div></blockquote><div><br>
</div></div><div>Contributions of time are welcome. I'm paid to manage the development of GROMACS, but if I fixed every little blemish any of us can see, then 5.0 will never happen. :-) If there's a reasonable way for users to find out that we have some tests (e.g. the install guide on the web) and to run them fairly easily (which they can do two different ways) then I think we've done well.</div>
</div></blockquote><div><br></div></div><div>While I've been using *NIX and OSS software not much longer than a decade, AFAIK README, INSTALL, and CHAGELOG files are the standard. Feel free to correct me on this if I'm wrong.</div>
</div></div></div></blockquote><div><br></div><div>That is a standard thing. It's particularly important for code that is often a dependency for other code, because you want to be able to compile and use something correct ASAP. It's less important for code where there are few things that depend on them, and where effective compilation is a non-trivial process. If the user is likely going to have to stop and do some research in order to build GROMACS well, making them go to the webpage to get access to any instructions might even work out better in the long run.</div>
<div><br></div><div>More to the point, I'm not going to spend time duplicating such content, particularly if it has to get bumped for roughly monthly patch releases (or else go out of date), and so go through code review processes that are mostly provided by busy volunteers. That ensures we can't have timely releases. If there's a way to deliver such text files for free such that they're only maintained once, then that's good. But so far there isn't such a way.</div>
<div><br></div><div>Mark</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div class="im">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">
<div>While it is probably true that the tarballs are more useful for users downloading the source, I do think that it there are many advanced users using the git code-base who would benefit from it. I can only guess that these more advanced users are probably less likely to read through the install guide or simply be more confident that they'd notice if something goes wrong because of mis-compilation or other platform-specific bugs. Hence, although the number of users using git code is probably much smaller than source-tarball users, I would guess that these users are more likely to simply not be aware of the integrated regression-tests.</div>
</div></div></div></blockquote><div><br></div></div><div>I don't follow you. If any kind of user won't scan the table of contents of an install guide on the web, and thereby manages to remain ignorant that we have some automated testing, that's a problem to which they've contributed.</div>
</div></blockquote><div><br></div></div><div>I disagree. Se above</div><div class="im"><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="gmail_quote">
<div><br></div><div>If we offer an automated tarball download, then we should make it work correctly. I have replaced the old tarball with one that works. I've also built and uploaded a 4.6.1 test tarball, and updated the machinery by which we do this for future patch releases.</div>
</div></blockquote><div><br></div></div><div>Great. I'll put together an email after 4.6.1 which briefly explains what is regression testing and why should everybody do it.</div><div> </div><div>Cheers,<br></div><div>
Szilard</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class="gmail_quote"><span><font color="#888888">
<div><br></div><div>Mark</div></font></span></div><div class="im">
<br>--<br>
gmx-developers mailing list<br>
<a href="mailto:gmx-developers@gromacs.org" target="_blank">gmx-developers@gromacs.org</a><br>
<a href="http://lists.gromacs.org/mailman/listinfo/gmx-developers" target="_blank">http://lists.gromacs.org/mailman/listinfo/gmx-developers</a><br>
Please don't post (un)subscribe requests to the list. Use the<br>
www interface or send it to <a href="mailto:gmx-developers-request@gromacs.org" target="_blank">gmx-developers-request@gromacs.org</a>.<br></div></blockquote></div><br></div></div>
<br>--<br>
gmx-developers mailing list<br>
<a href="mailto:gmx-developers@gromacs.org">gmx-developers@gromacs.org</a><br>
<a href="http://lists.gromacs.org/mailman/listinfo/gmx-developers" target="_blank">http://lists.gromacs.org/mailman/listinfo/gmx-developers</a><br>
Please don't post (un)subscribe requests to the list. Use the<br>
www interface or send it to <a href="mailto:gmx-developers-request@gromacs.org">gmx-developers-request@gromacs.org</a>.<br></blockquote></div><br>