www.digitalmars.com         C & C++   DMDScript  

digitalmars.D - Why are tests restarting in Github?

reply tcak <1ltkrs+3wyh1ow7kzn1k sharklasers.com> writes:
There are 10 test. Some of them gets completed. And then, I look 
at it again, tests have restarted, and less number of tests are 
passed at that point.

1. What is the reason of restarts?

2. What is reason of long waiting time? Sometimes number of 
passed tests stay there 2-3 days.
Apr 24 2016
next sibling parent reply ag0aep6g <anonymous example.com> writes:
On 24.04.2016 21:26, tcak wrote:
 There are 10 test. Some of them gets completed. And then, I look at it
 again, tests have restarted, and less number of tests are passed at that
 point.

 1. What is the reason of restarts?
Something else has been pulled. That changes the code that's being tested, so all tests need to restarted.
 2. What is reason of long waiting time? Sometimes number of passed tests
 stay there 2-3 days.
The pull request is probably not a priority for the auto-tester. Pull requests that have been marked for auto-merging have priority over others. I'm not sure, but the auto-tester may also prioritize requests with recent activity over older ones.
Apr 24 2016
parent Daniel Murphy <yebbliesnospam gmail.com> writes:
On 25/04/2016 5:44 AM, ag0aep6g wrote:
 On 24.04.2016 21:26, tcak wrote:
 There are 10 test. Some of them gets completed. And then, I look at it
 again, tests have restarted, and less number of tests are passed at that
 point.

 1. What is the reason of restarts?
Something else has been pulled. That changes the code that's being tested, so all tests need to restarted.
 2. What is reason of long waiting time? Sometimes number of passed tests
 stay there 2-3 days.
The pull request is probably not a priority for the auto-tester. Pull requests that have been marked for auto-merging have priority over others. I'm not sure, but the auto-tester may also prioritize requests with recent activity over older ones.
Yes, if you rebase and force-push your pull will be put at the top of the list.
Apr 24 2016
prev sibling parent Basile B. <b2.temp gmx.com> writes:
On Sunday, 24 April 2016 at 19:26:43 UTC, tcak wrote:
 2. What is reason of long waiting time? Sometimes number of 
 passed tests stay there 2-3 days.
There's a windows tester (win-farm-1) that takes 1 hour to complete each single test while most of the other testers usually take 10 to 20 minutes. On high activity period it's almost impossible to get an old PR fully tested. Each time someone amends or fixes-up something the slow machines take the new stuffs before. For example look at this one: https://auto-tester.puremagic.com/pull-history.ghtml?projectid=1&repoid=3&pullid=4204 win_32_64 (win-farm-1) has only run **once** while FreeBSD_32 has run **21 times** !!
Apr 24 2016