<div dir="ltr">Odd. With the latest cog/spur/win64x64<div><br></div><div>Test: 21:06.89</div><div>Slowest:</div><div><div> 05:24.970 PureBehaviorTest</div><div> 03:17.736 TraitTest</div><div> 03:02.790 TraitMethodDescriptionTest</div><div> 02:05.559 TraitCompositionTest</div><div> 01:07.887 TraitFileOutTest</div></div><div><br></div><div>So 3 minutes slower, although decompiler test are still significantly faster.</div><div><br></div><div>On the good side, the errors went away:</div><div>4494 run, 4442 passes, 29 expected failures, 22 failures, 0 errors, 1 unexpected passes<br></div><div>(probably because there were 134 less tests ran?)</div><div><br></div><div>Thanks,</div><div>cbc</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jul 14, 2018 at 9:40 AM, Chris Cunningham <span dir="ltr"><<a href="mailto:cunningham.cb@gmail.com" target="_blank">cunningham.cb@gmail.com</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">Yes, stack. It was the VM that came with the image I downloaded (months ago) for dev.<div><br></div><div>Using a more recent VM (cog/spur):</div><div><div> Croquet Closure Cog[Spur] VM [CoInterpreterPrimitives VMMaker.oscog-eem.2361]</div><div> Win32 built on Apr 3 2018 17:24:23 GMT Compiler: 4.2.1 Compatible Clang 5.0.1 (tags/RELEASE_501/final)</div></div><div>(this is the 'stable' VM from <a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/latest" target="_blank">https://github.com/<wbr>OpenSmalltalk/opensmalltalk-<wbr>vm/releases/latest</a>):</div><div><br></div><div>Tests: 18:35.123</div><div>Slowest:</div><div><div> 05:24.681 PureBehaviorTest</div><div> 03:10.968 TraitTest</div><div> 02:32.973 TraitMethodDescriptionTest</div><div> 01:50.439 TraitCompositionTest</div></div><div>I find it interesting that these tests didn't really improve at all. On the other hand, Decompiler test went from 3 minutes to under a minute - it is sensitive to the VM, apparently (i.e., faster with newer VM's).</div><div class="gmail_extra"><br></div><div class="gmail_extra">Oh, and the number of failures increased DRAMATICALLY:</div><div class="gmail_extra">4528 run, 4311 passes, 32 expected failures, 30 failures, <b>154 errors</b>, 1 unexpected passes</div><div class="gmail_extra">(the stack VM had
<span style="font-size:small;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline"><span> "</span>4479 run, 4426 passes, 29 expected failures, 23 failures, <b>0 errors</b>, 1 unexpected passes". It seems to have run 150+ new tests over the last run, and while I added the HelpSystem tests back in, those were only 13 total and all passed. I would guess that the extra tests were previous filtered out for Windows, but that stable VM let them run, maybe).</span></div><div class="gmail_extra"><br></div><div class="gmail_extra">Will run with latest VM in a bit, and see if I can find out more about the additional errors. That worries me.</div><div class="gmail_extra"><br></div><div class="gmail_extra">-cbc</div><div><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jul 14, 2018 at 2:58 AM, Levente Uzonyi <span dir="ltr"><<a href="mailto:leves@caesar.elte.hu" target="_blank">leves@caesar.elte.hu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Is that a Stack VM? That could explain why it takes more than just a few minutes to run the full test suite.<br>
<br>
Levente<div><div class="m_-1794462816194567029gmail-m_-3574440787350517584gmail-h5"><br>
<br>
On Fri, 13 Jul 2018, Chris Cunningham wrote:<br>
<br>
</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div class="m_-1794462816194567029gmail-m_-3574440787350517584gmail-h5">
Hi.<br>
I'm trying to run the full test suite in Squeak, and it takes a while. So, I've timed it and noted which parts are slow.<br>
<br>
Full test suite in Test Runner (except the "Help System-*" tests - more on that later) took 26:21.798 - just under a 1/2 hour.<br>
<br>
The top 6 test classes (those taking over a minute each):<br>
05:11.612 PureBehaviorTest<br>
03:15.047 DecompilerTests<br>
03:09.779 TraitTest<br>
03:01.287 TraitMethodDescriptionTest<br>
02:19.789 TraitCompositionTest<br>
01:12.013 TraitFileOutTest<br>
So, about 2/3rds of the time on those tests.<br>
<br>
Testing environment:<br>
Squeak5.2alpha<br>
latest update: #18145<br>
Image format 68021 (64 bit)<br>
Croquet Closure Stack VM [StackInterpreterPrimitives VMMaker.oscog-eem.2203]<br>
Win32 built on Apr 27 2017 03:08:19 GMT Compiler: 4.2.1 Compatible Clang 3.9.1 (tags/RELEASE_391/final)<br>
platform sources revision VM: 201704270225 <br>
hardware:<br>
Processors: AMD FX(tm)-6300 Six-Core Processor <br>
Identifier: AMD64 Family 21 Model 2 Stepping 0<br>
~MHZ: 3516<br>
Operating System: Windows 10 Home (Build 9200 )<br>
<br>
Results:<br>
4479 run, 4426 passes, 29 expected failures, 23 failures, 0 errors, 1 unexpected passes<br>
Issues:<br></div></div>
[IMAGE]<span class="m_-1794462816194567029gmail-m_-3574440787350517584gmail-"><br>
<br>
So, what are the 'normal' failing tests that I should ignore, if any?<br>
<br>
If you are interested in how the timing was done, I loaded this package (recently created for another purpose):<br>
MCHttpRepository<br>
location: '<a href="http://www.squeaksource.com/CBCTimeLogging" rel="noreferrer" target="_blank">http://www.squeaksource.com/C<wbr>BCTimeLogging</a>'<br>
user: ''<br>
password: ''<br>
Load "Time Logging" (at least version cbc.2)<br>
Load "Test logging sunit integration" (at least version cbc.1)<br>
<br>
Then, any runs of tests in TestRunner should log the it takes. The following commands show the results as noted above:<br>
(TimeLogging globalTimingLogs category: #testRunner) categoryTime. <br>
(((TimeLogging globalTimingLogs category: #testRunner) slowestGroupTimes select: [:sgt| sgt second >= 1 minute]) collect: #printString) joinSeparatedBy: String cr.<br>
<br>
* About the "Help-System-*" tests, they manage to block the TestRunner with a failure in showing one of the UI's, which after moving a window or two locked up the image. Not nice. Will follow up in another<br>
message.<br>
<br>
Also, why does Test Runner not keep a progress bar showing all of the time? It is unnerving now knowing if it is running or not - several times it just seems locked while it is doing things in the<br>
background.<br>
<br>
Thanks,<br>
cbc<br>
<br>
</span></blockquote>
<br><br>
<br></blockquote></div><br></div></div></div></div>
</blockquote></div><br></div>