<div dir="ltr">Hi John,<br><br><div class="gmail_quote"><div class="GmSign">-- <br><br></div><div dir="ltr">On Thu, Jun 16, 2016 at 7:50 PM John McIntosh &lt;<a href="mailto:johnmci@smalltalkconsulting.com">johnmci@smalltalkconsulting.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <div dir="auto"><div><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><font color="#000000"><span style="background-color:rgba(255,255,255,0)"> OS X 64-bit<br></span></font></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><font color="#000000"><span style="background-color:rgba(255,255,255,0)">Sista fails </span></font></blockquote></blockquote></blockquote><div><br></div>Need some pointers so I can debug this <br></div></div></blockquote><div><br></div><div>Here&#39;s the failing build:</div><div><a href="https://travis-ci.org/OpenSmalltalk/vm/jobs/138342179#L73">https://travis-ci.org/OpenSmalltalk/vm/jobs/138342179#L73</a></div><div><br></div><div>According to [1], there is supposed to be a [2]. There isn&#39;t, but there is a [3]. So I&#39;m assuming that 64bit spursista has not been implemented yet (same with Linux 64bit).</div><div>I will disable OS X 64-bit Spur Sista builds for now.</div><div><br></div><div>[1] <a href="https://github.com/OpenSmalltalk/vm/blob/56c4157d4a41fbc6d8f98e241c4eec954d15ebd2/build.macos64x64/squeak.sista.spur/Makefile#L6">https://github.com/OpenSmalltalk/vm/blob/56c4157d4a41fbc6d8f98e241c4eec954d15ebd2/build.macos64x64/squeak.sista.spur/Makefile#L6</a></div><div>[2] <a href="https://github.com/OpenSmalltalk/vm/tree/Cog/spursista64src/vm" style="line-height:1.5;outline:transparent solid 1px">https://github.com/OpenSmalltalk/vm/tree/Cog/spursista64src/vm</a></div><div>[3] <span style="color:rgb(51,103,214);text-decoration:underline;line-height:1.5"><a href="https://github.com/OpenSmalltalk/vm/tree/Cog/spursistasrc/vm">https://github.com/OpenSmalltalk/vm/tree/Cog/spursistasrc/vm</a></span></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div><div><br></div><br><br>Sent from my iPhone</div></div><div dir="auto"><div><br>On Jun 16, 2016, at 9:56 AM, Eliot Miranda &lt;<a href="mailto:eliot.miranda@gmail.com" target="_blank">eliot.miranda@gmail.com</a>&gt; wrote:<br><br></div><blockquote type="cite"><div><span></span><br><span>Hi All,</span><br><span></span><br><blockquote type="cite"><span>On Jun 16, 2016, at 9:38 AM, Ben Coman &lt;<a href="mailto:btc@openinworld.com" target="_blank">btc@openinworld.com</a>&gt; wrote:</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>On Thu, Jun 16, 2016 at 5:10 PM, Serge Stinckwich</span><br></blockquote><blockquote type="cite"><span>&lt;<a href="mailto:serge.stinckwich@gmail.com" target="_blank">serge.stinckwich@gmail.com</a>&gt; wrote:</span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>On Thu, Jun 16, 2016 at 9:24 AM, Tim Felgentreff</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>&lt;<a href="mailto:timfelgentreff@gmail.com" target="_blank">timfelgentreff@gmail.com</a>&gt; wrote:</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Hi all,</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Very impressive work, Tim&amp;Fabio ! The power of full-automation !</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>as of 7:30 UTC the entire history of the SVN up to SVN revision 3745 was</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>migrated to GitHub. Automatic builds are running</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>(<a href="https://ci.appveyor.com/project/timfel/vm/branch/Cog" target="_blank">https://ci.appveyor.com/project/timfel/vm/branch/Cog</a>,</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span><a href="https://travis-ci.org/OpenSmalltalk/vm" target="_blank">https://travis-ci.org/OpenSmalltalk/vm</a>) and binary artifacts are uploaded</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>(<a href="https://bintray.com/opensmalltalk/vm/cog/_latestVersion#files" target="_blank">https://bintray.com/opensmalltalk/vm/cog/_latestVersion#files</a>).</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>About uploading binary artifacts, this is something I asked and this</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>nice that Fabio make it work :-)</span><br></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>What is the advantage of this?   The 44 .image files stored in the</span><br></blockquote><blockquote type="cite"><span>repository take up 196MB, doubling the space.  </span><br></blockquote><span></span><br><span>What are the images?  IIRC there are no images in the svn repo. The only big files are sources files for  various key squeak and Pharo releases.  Did I check in images in the images directory by mistake?  There should be nine there; they&#39;re to be downloaded and built/converted, not checked into the repository.</span><br><span></span><br><span>So please, list these image files here...</span><br><span></span><br><blockquote type="cite"><span> I guess thats not a</span><br></blockquote><blockquote type="cite"><span>big deal for a one time cost to clone the repository - for most of us</span><br></blockquote><blockquote type="cite"><span>with wide bandwidths in the modern world.  But some places still have</span><br></blockquote><blockquote type="cite"><span>limited bandwidth.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Also SSD are sometimes not so big, and maybe someone wants to compile</span><br></blockquote><blockquote type="cite"><span>on a smaller system like as RasPi (although it can handle reasonable</span><br></blockquote><blockquote type="cite"><span>sized storage cards.)</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><span>Apparently there is some problems with some artifacts that have a</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>double .zip extension.</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Right now we have enabled all platform, object memory and bytecode set</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>combinations that I found build scripts for - most work, but OS X 64-bit</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Sista is failing right now (32-bit works). At some point we&#39;ll have to</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>decide which combinations to put into the CI config as &quot;allowed failures&quot; to</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>get a green badge :)</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Another thing for those not familiar with Git: Right now the entire</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>repository is 360MB, including all history. Most of that is old images that</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>were at one point committed to SVN and that have been pulled into the</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>repository. We could clean those out (removing them from the history) to</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>make the repository smaller, but I felt ~400MB is still ok (albeit</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>technically over the Github quota. We&#39;ll see of they complain). I would like</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>to ask everyone to stop committing large binary files into the repository,</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>however. Git is simply not very suited to dealing with binaries.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>If there is a need for that, Github has support for git-lfs, which offers 1GB of free</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>storage with a 1GB bandwith limit per month.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>Initially I said... &quot;Please, can we consider doing that.  1GB/1GB</span><br></blockquote><blockquote type="cite"><span>seems ample, and $5/mth provides 50GB/50GB [1] (and you&#39;d expect those</span><br></blockquote><blockquote type="cite"><span>quotas to expand over time.) And a quick reference to how it works</span><br></blockquote><blockquote type="cite"><span>[2]. However enabling lfs doesn&#39;t automatically convert existing</span><br></blockquote><blockquote type="cite"><span>commits.  The recommend migration tool seems to be git-lfs-migrate</span><br></blockquote><blockquote type="cite"><span>[3].  But history is rewritten, so any clones will need to be rebased</span><br></blockquote><blockquote type="cite"><span>- so now at the start is probably the best time to do it !  &quot;</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>But then I read lfs currently doesn&#39;t work properly with forked repos [4] [5]</span><br></blockquote><blockquote type="cite"><span>Also early lfs versions seem to have had a performance issue [6],</span><br></blockquote><blockquote type="cite"><span>but that may be recently solved [7].</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>btw, is anyone going to be using git-svn, or is everyone making the</span><br></blockquote><blockquote type="cite"><span>big jump pure git?</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>In any case, I&#39;m very glad to see the repo on git.  Thanks all that</span><br></blockquote><blockquote type="cite"><span>helped make it happen, and Tim &amp; Fabio for the work.</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>cheers -ben</span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span>[1] <a href="https://help.github.com/articles/billing-plans-for-git-large-file-storage/" target="_blank">https://help.github.com/articles/billing-plans-for-git-large-file-storage/</a></span><br></blockquote><blockquote type="cite"><span>[2] <a href="https://git-lfs.github.com/" target="_blank">https://git-lfs.github.com/</a></span><br></blockquote><blockquote type="cite"><span>[3] <a href="https://github.com/bozaro/git-lfs-migrate" target="_blank">https://github.com/bozaro/git-lfs-migrate</a></span><br></blockquote><blockquote type="cite"><span>[4] <a href="https://medium.com/@megastep/github-s-large-file-storage-is-no-panacea-for-open-source-quite-the-opposite-12c0e16a9a91#.omrd0qw6n" target="_blank">https://medium.com/@megastep/github-s-large-file-storage-is-no-panacea-for-open-source-quite-the-opposite-12c0e16a9a91#.omrd0qw6n</a></span><br></blockquote><blockquote type="cite"><span>[5] <a href="https://github.com/github/git-lfs/issues/773" target="_blank">https://github.com/github/git-lfs/issues/773</a></span><br></blockquote><blockquote type="cite"><span>[6] <a href="https://www.bountysource.com/issues/21357625-git-lfs-is-unusable-slow-especially-on-windows" target="_blank">https://www.bountysource.com/issues/21357625-git-lfs-is-unusable-slow-especially-on-windows</a></span><br></blockquote><blockquote type="cite"><span>[7] <a href="https://developer.atlassian.com/blog/2016/04/git-lfs-12-clone-faster/" target="_blank">https://developer.atlassian.com/blog/2016/04/git-lfs-12-clone-faster/</a></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><span></span><br></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>If we need more, we can look at</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>the different billing levels.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>If you&#39;re familiar with Git, the only new thing to watch out for is the</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>updateSCSSVersions script as described in the README. It&#39;s not relevant for</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>the CI, but your own binaries will only show correct versions if this script</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>runs at appropriate times.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>If you are not familiar with Git and don&#39;t care, there are scripts for</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>committing that should take care of everything as described in the README.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>Again, let us know if anything doesn&#39;t work. The only difference vs SVN to</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>watch out for for you will be that the old scripts/svnci would commit your</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>changes to the server, whereas the scripts/gitci script only commits them</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>locally. You&#39;ll have to run `git pull` and `git push` to get them up to the</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>server.</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>If you have any questions regarding the repository setup please don&#39;t</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>hesitate to ask. You shouldn&#39;t be able to break anything, since we&#39;ve</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>disabled force pushes to both master and Cog (and thus any chance of</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span>destroying history).</span><br></blockquote></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>What is favorite way of contributing for people outside the vm team ?</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>pull-requests ?</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span></span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Regards,</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>--</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Serge Stinckwich</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>UCBN &amp; UMI UMMISCO 209 (IRD/UPMC)</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span>Every DSL ends up being Smalltalk</span><br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite"><span><a href="http://www.doesnotunderstand.org/" target="_blank">http://www.doesnotunderstand.org/</a></span><br></blockquote></blockquote></div></blockquote></div></blockquote></div></div>