Proposal: Allowing selective pushes to hotspot without jprt

[David Holmes]

On 22/11/2014 1:35 AM, Magnus Ihse Bursie wrote:
>
> On 2014-11-19 09:23, Volker Simonis wrote:
>> On Wed, Nov 19, 2014 at 2:53 AM, David Holmes
>> <david.holmes at oracle.com> wrote:
>>> On 18/11/2014 8:03 PM, Volker Simonis wrote:
>>>> You're right - it works!
>>>> I've just pushed my first AIX-only change to hotspot-rt!
>>>
>>> Congratulations!
>>>
>>> Unfortunately it caused us a problem as now the repos can change
>>> whilst a
>>> job is going through JPRT - this requires a new merge due to multiple
>>> heads
>>> and so triggered a failure. But Mikael is working on it :)
>> It's astonishing how even the smallest changes can introduce
>> non-foreseeable problems.
>>
>> Hopefully Mikael will be able to fix the problem somehow (if he didn't
>> had too much of the champagne already :)
>
> Actually, having non-atomic commits *is* a foreseeable problem. ;-)
> Which is what you get when you just throw a bunch of unrelated
> mercurials together without any synchronization in-between them. In
> fact, I'm surprised this kind of thing does not happen any more often,
> but then again, a lot of our procedures have probably evolved partially
> as a response to this constraint.

This wasn't the non-atomic commit problem, but rather a concurrent 
commit to the same repo while a JPRT job was running. At push time it 
surprised JPRT to find a new head in the target repo - something it 
considered to be an error.

David
-----

> I'd like to see us moving to using atomic commits for the whole project.
> Unfortunately, there is no simple solution to this even for the open
> source code only, and it gets worse when adding the closed components.
>
> /Magnus