Re: [GDB BuildBot] New "Try Server"

[Antoine Tremblay <antoine.tremblay@ericsson.com>]

Sergio Durigan Junior writes:

> Last, but not least, your try build will generate its own testsuite
> logs, which will be recorded in that builder's git repository, available
> at:
>
>   <http://gdb-build.sergiodj.net/cgit>

Humm won't that "pollute" the builder results ?

I mean, if the builder is testing commit 1 2 3 and that those are
commits that were done on master but there's a try patch coming in
between named say 7 and it has higher priority.

You will then have 1 2 7 3 being tested.

Then when we want to check the results of 1 2 3 won't it be confusing to
see 7 there ? Will there be an indication that it's a try patch ?

Also since the regressions are calculated from one build to the next
won't that possibly be a problem if let's say build 7 introduces a FAIL,
then build 3 has the same FAIL, but build 2 had a PASS ? We would then
miss a regression on a master commit.

Should we have separate try builders to avoid that?

I'm also curious about what happens if you send it a series of patches,
will it squash them ?

In any case thanks for working on this :) I'm sure it will be quite
useful.