understanding Auto-Test

[Seb]

On Thursday, 22 March 2018 at 04:17:52 UTC, Mike Franklin wrote:
> On Thursday, 22 March 2018 at 04:12:00 UTC, John Belmonte wrote:
>
>> I'm still rather puzzled.  My pull request remains with 8 
>> tests pending after several hours.  I can't find any 
>> confirmation on the pulls display 
>> https://auto-tester.puremagic.com/pulls.ghtml?projectid=1 that 
>> it intends to run the tests.   Surely being listed in the "Old 
>> results" table doesn't imply pending runs against a new SHA, 
>> otherwise why would there be entries there dated 2017?
>
> I see.  It appears GitHub didn't pick of the latest status (or 
> the auto-tester didn't notify GitHub;

Everything is working as expected. Every time a PR gets merged, 
ALL pull requests get invalidated and are moved to "Old results" 
as their results have been calculated against an old head.
Then auto-tester starts to reduce the "Old results" list by 
building them again.
It's a constant fight.

> I'm not which way the  data flows).

GitHub -> CIs (via hooks)

(though especially auto-tester queries back a lot)

> Let's see what happens after the auto-tester starts testing it 
> again.  I'll keep an eye on it.

No need to keep an eye on this. auto-tester will constantly 
rebuild the PR and invalidate it.
The only way interaction is possible is via:

- manually invalidating builds (called "delete" at the 
auto-tester) - not really useful as builds are automatically 
invalidated
- "auto-merge" priority builds. The PR has super-priority in the 
build queue.

That's happening currently with the four builds at the top:

https://imgur.com/a/29Ohn