You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Karl Heinz Marbaise <kh...@gmx.de> on 2014/01/16 19:23:11 UTC

Bug ? With SVN 1.8.4 on Mac

Hi,

i observed a strange thing during a checkin process running where i got 
the following messages:

Karl-Heinzs-MacBook-Pro:exec-maven-plugin kama$ svn ci -F x.diff
Sending        src/it/mexec-100/pom.xml
Sending        src/it/mexec-105/pom.xml
Transmitting file data ..
Committed revision 19310.
svn: E120108: Commit failed (details follow):
svn: E120108: Error running context: The server unexpectedly closed the 
connection.
svn: E120108: Additional errors:
svn: E120108: Error running context: The server unexpectedly closed the 
connection.

BUT:

On my build server this version is already being used:

19:17:54 Updating 
https://svn.codehaus.org/mojo/trunk/mojo/exec-maven-plugin at revision 
'2014-01-16T19:17:39.738 +0100'
19:17:57 U         src/it/mexec-100/pom.xml
19:17:57 U         src/it/mexec-105/pom.xml
19:17:57 At revision 19310

This means for me the above error message is simply wrong, cause the 
revision has already been committed into the repository...and could be 
used and has been use for an update...

Anything known about this ?


Kind regards
Karl-Heinz Marbaise
-- 
SoftwareEntwicklung Beratung Schulung    Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz Marbaise        ICQ#: 135949029
Hauptstrasse 177                         USt.IdNr: DE191347579
52146 Würselen                           http://www.soebes.de

Re: Bug ? With SVN 1.8.4 on Mac

Posted by Ben Reser <be...@reser.org>.
On 1/16/14, 12:34 PM, Bert Huijben wrote:
> That script is only going to help you for the platform invariant error codes
> in Subversion itself + the codes on the platform you are checking on.

It knows about APR's errors as well (not that this is important in this case),
see the aprerr.txt file in tools/dev

RE: Bug ? With SVN 1.8.4 on Mac

Posted by Bert Huijben <be...@qqmail.nl>.

> -----Original Message-----
> From: Philip Martin [mailto:philip.martin@wandisco.com]
> Sent: donderdag 16 januari 2014 20:59
> To: info@soebes.de
> Cc: users@subversion.apache.org
> Subject: Re: Bug ? With SVN 1.8.4 on Mac
> 
> Karl Heinz Marbaise <kh...@gmx.de> writes:
> 
> > Hi,
> >
> > so after i did an svn up i got this:
> >
> > Karl-Heinzs-MacBook-Pro:exec-maven-plugin kama$ svn up
> > Updating '.':
> > G    src/it/mexec-100/pom.xml
> > G    src/it/mexec-105/pom.xml
> >
> > more or less expected....
> >
> >> furthermore i have recodnized that the local files are currently in the
> >> state of modified:
> >>
> >> Karl-Heinzs-MacBook-Pro:exec-maven-plugin kama$ svn st
> >> M       src/it/mexec-100/pom.xml
> >> M       src/it/mexec-105/pom.xml
> >>
> >>> i observed a strange thing during a checkin process running where i
got
> >>> the following messages:
> >>>
> >>> Karl-Heinzs-MacBook-Pro:exec-maven-plugin kama$ svn ci -F x.diff
> >>> Sending        src/it/mexec-100/pom.xml
> >>> Sending        src/it/mexec-105/pom.xml
> >>> Transmitting file data ..
> >>> Committed revision 19310.
> >>> svn: E120108: Commit failed (details follow):
> >>> svn: E120108: Error running context: The server unexpectedly closed
the
> >>> connection.
> >>> svn: E120108: Additional errors:
> >>> svn: E120108: Error running context: The server unexpectedly closed
the
> >>> connection.
> 
> E120108 is unknown on my Linux box:
> 
> $ ../src/tools/dev/which-error.py E120108
> 00120108  *** UNKNOWN ERROR CODE ***
> 
> The client recognises SVN_ERR_REPOS_POST_COMMIT_HOOK_FAILED
> (165007) as
> a failed post-commit so the unknown E120108 meant the client didn't do
> post-commit processing so the committed files showed up as uncommitted.

That error code looks like the platform specific error code for "The server
unexpectedly closed the connection.".

That script is only going to help you for the platform invariant error codes
in Subversion itself + the codes on the platform you are checking on.

	Bert


Re: Bug ? With SVN 1.8.4 on Mac

Posted by Philip Martin <ph...@codematters.co.uk>.
Philip Martin <ph...@wandisco.com> writes:

>>>> Karl-Heinzs-MacBook-Pro:exec-maven-plugin kama$ svn ci -F x.diff
>>>> Sending        src/it/mexec-100/pom.xml
>>>> Sending        src/it/mexec-105/pom.xml
>>>> Transmitting file data ..
>>>> Committed revision 19310.
>>>> svn: E120108: Commit failed (details follow):
>>>> svn: E120108: Error running context: The server unexpectedly closed the
>>>> connection.
>>>> svn: E120108: Additional errors:
>>>> svn: E120108: Error running context: The server unexpectedly closed the
>>>> connection.
>
> E120108 is unknown on my Linux box:
>
> $ ../src/tools/dev/which-error.py E120108
> 00120108  *** UNKNOWN ERROR CODE ***

I think that might be SERF_ERROR_ABORTED_CONNECTION.

Is that an error the commiting client generated while reading the
response from the server or a server error returned to the committing
client?  The committing client seems to have received enough of the
response to get the new revision number.

-- 
Philip

Re: Bug ? With SVN 1.8.4 on Mac

Posted by Philip Martin <ph...@wandisco.com>.
Karl Heinz Marbaise <kh...@gmx.de> writes:

> Hi,
>
> so after i did an svn up i got this:
>
> Karl-Heinzs-MacBook-Pro:exec-maven-plugin kama$ svn up
> Updating '.':
> G    src/it/mexec-100/pom.xml
> G    src/it/mexec-105/pom.xml
>
> more or less expected....
>
>> furthermore i have recodnized that the local files are currently in the
>> state of modified:
>>
>> Karl-Heinzs-MacBook-Pro:exec-maven-plugin kama$ svn st
>> M       src/it/mexec-100/pom.xml
>> M       src/it/mexec-105/pom.xml
>>
>>> i observed a strange thing during a checkin process running where i got
>>> the following messages:
>>>
>>> Karl-Heinzs-MacBook-Pro:exec-maven-plugin kama$ svn ci -F x.diff
>>> Sending        src/it/mexec-100/pom.xml
>>> Sending        src/it/mexec-105/pom.xml
>>> Transmitting file data ..
>>> Committed revision 19310.
>>> svn: E120108: Commit failed (details follow):
>>> svn: E120108: Error running context: The server unexpectedly closed the
>>> connection.
>>> svn: E120108: Additional errors:
>>> svn: E120108: Error running context: The server unexpectedly closed the
>>> connection.

E120108 is unknown on my Linux box:

$ ../src/tools/dev/which-error.py E120108
00120108  *** UNKNOWN ERROR CODE ***

The client recognises SVN_ERR_REPOS_POST_COMMIT_HOOK_FAILED (165007) as
a failed post-commit so the unknown E120108 meant the client didn't do
post-commit processing so the committed files showed up as uncommitted.

-- 
Philip Martin | Subversion Committer
WANdisco // *Non-Stop Data*

Re: Bug ? With SVN 1.8.4 on Mac

Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi,

so after i did an svn up i got this:

Karl-Heinzs-MacBook-Pro:exec-maven-plugin kama$ svn up
Updating '.':
G    src/it/mexec-100/pom.xml
G    src/it/mexec-105/pom.xml

more or less expected....

 > Hi,
>
> furthermore i have recodnized that the local files are currently in the
> state of modified:
>
> Karl-Heinzs-MacBook-Pro:exec-maven-plugin kama$ svn st
> M       src/it/mexec-100/pom.xml
> M       src/it/mexec-105/pom.xml
>
> which is really strange, cause the files i have changed the above two
> pom files have already been used on my build server.
>
> BTW: My SVN Environment:
>
> svn, version 1.8.4 (r1534716)
>     compiled Oct 25 2013, 11:02:47 on x86_64-apple-darwin12.4.0
>
> Copyright (C) 2013 The Apache Software Foundation.
> This software consists of contributions made by many people;
> see the NOTICE file for more information.
> Subversion is open source software, see http://subversion.apache.org/
>
> The following repository access (RA) modules are available:
>
> * ra_svn : Module for accessing a repository using the svn network
> protocol.
>    - with Cyrus SASL authentication
>    - handles 'svn' scheme
> * ra_local : Module for accessing a repository on local disk.
>    - handles 'file' scheme
> * ra_serf : Module for accessing a repository via WebDAV protocol using
> serf.
>    - using serf 1.2.1
>    - handles 'http' scheme
>    - handles 'https' scheme
>
> On 1/16/14 7:23 PM, Karl Heinz Marbaise wrote:
>> Hi,
>>
>> i observed a strange thing during a checkin process running where i got
>> the following messages:
>>
>> Karl-Heinzs-MacBook-Pro:exec-maven-plugin kama$ svn ci -F x.diff
>> Sending        src/it/mexec-100/pom.xml
>> Sending        src/it/mexec-105/pom.xml
>> Transmitting file data ..
>> Committed revision 19310.
>> svn: E120108: Commit failed (details follow):
>> svn: E120108: Error running context: The server unexpectedly closed the
>> connection.
>> svn: E120108: Additional errors:
>> svn: E120108: Error running context: The server unexpectedly closed the
>> connection.
>>
>> BUT:
>>
>> On my build server this version is already being used:
>>
>> 19:17:54 Updating
>> https://svn.codehaus.org/mojo/trunk/mojo/exec-maven-plugin at revision
>> '2014-01-16T19:17:39.738 +0100'
>> 19:17:57 U         src/it/mexec-100/pom.xml
>> 19:17:57 U         src/it/mexec-105/pom.xml
>> 19:17:57 At revision 19310
>>
>> This means for me the above error message is simply wrong, cause the
>> revision has already been committed into the repository...and could be
>> used and has been use for an update...
>>
>> Anything known about this ?
>>
>>
>> Kind regards
>> Karl-Heinz Marbaise
>
>
> Kind regards
> Karl-Heinz Marbaise


Mit freundlichem Gruß
Karl-Heinz Marbaise
-- 
SoftwareEntwicklung Beratung Schulung    Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz Marbaise        ICQ#: 135949029
Hauptstrasse 177                         USt.IdNr: DE191347579
52146 Würselen                           http://www.soebes.de

Re: Bug ? With SVN 1.8.4 on Mac

Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi,

furthermore i have recodnized that the local files are currently in the 
state of modified:

Karl-Heinzs-MacBook-Pro:exec-maven-plugin kama$ svn st
M       src/it/mexec-100/pom.xml
M       src/it/mexec-105/pom.xml

which is really strange, cause the files i have changed the above two 
pom files have already been used on my build server.

BTW: My SVN Environment:

svn, version 1.8.4 (r1534716)
    compiled Oct 25 2013, 11:02:47 on x86_64-apple-darwin12.4.0

Copyright (C) 2013 The Apache Software Foundation.
This software consists of contributions made by many people;
see the NOTICE file for more information.
Subversion is open source software, see http://subversion.apache.org/

The following repository access (RA) modules are available:

* ra_svn : Module for accessing a repository using the svn network protocol.
   - with Cyrus SASL authentication
   - handles 'svn' scheme
* ra_local : Module for accessing a repository on local disk.
   - handles 'file' scheme
* ra_serf : Module for accessing a repository via WebDAV protocol using 
serf.
   - using serf 1.2.1
   - handles 'http' scheme
   - handles 'https' scheme

On 1/16/14 7:23 PM, Karl Heinz Marbaise wrote:
> Hi,
>
> i observed a strange thing during a checkin process running where i got
> the following messages:
>
> Karl-Heinzs-MacBook-Pro:exec-maven-plugin kama$ svn ci -F x.diff
> Sending        src/it/mexec-100/pom.xml
> Sending        src/it/mexec-105/pom.xml
> Transmitting file data ..
> Committed revision 19310.
> svn: E120108: Commit failed (details follow):
> svn: E120108: Error running context: The server unexpectedly closed the
> connection.
> svn: E120108: Additional errors:
> svn: E120108: Error running context: The server unexpectedly closed the
> connection.
>
> BUT:
>
> On my build server this version is already being used:
>
> 19:17:54 Updating
> https://svn.codehaus.org/mojo/trunk/mojo/exec-maven-plugin at revision
> '2014-01-16T19:17:39.738 +0100'
> 19:17:57 U         src/it/mexec-100/pom.xml
> 19:17:57 U         src/it/mexec-105/pom.xml
> 19:17:57 At revision 19310
>
> This means for me the above error message is simply wrong, cause the
> revision has already been committed into the repository...and could be
> used and has been use for an update...
>
> Anything known about this ?
>
>
> Kind regards
> Karl-Heinz Marbaise


Kind regards
Karl-Heinz Marbaise
-- 
SoftwareEntwicklung Beratung Schulung    Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz Marbaise        ICQ#: 135949029
Hauptstrasse 177                         USt.IdNr: DE191347579
52146 Würselen                           http://www.soebes.de

Re: Bug ? With SVN 1.8.4 on Mac

Posted by Karl Heinz Marbaise <kh...@gmx.de>.
Hi Mark,

 >     Transmitting file data ..
>     Committed revision 19310.
>
>
> It looks like the commit worked.

So this mean in other words the whole transaction on the server side
is done....


>
>     svn: E120108: Commit failed (details follow):
>     svn: E120108: Error running context: The server unexpectedly closed
>     the connection.
>     svn: E120108: Additional errors:
>     svn: E120108: Error running context: The server unexpectedly closed
>     the connection.
>
>
> And the failure came in the post-commit updating of your working copy to
> reflect this.

But this is only on the client side which failed...(for whatever reason)...

Apart from the wrong message saying: "Commit failed..." ....from my 
point of view ..

Thanks for helping.

Kind regards
Karl-Heinz Marbaise
-- 
SoftwareEntwicklung Beratung Schulung    Tel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz Marbaise        ICQ#: 135949029
Hauptstrasse 177                         USt.IdNr: DE191347579
52146 Würselen                           http://www.soebes.de

Re: Bug ? With SVN 1.8.4 on Mac

Posted by Mark Phippard <ma...@gmail.com>.
On Thu, Jan 16, 2014 at 1:23 PM, Karl Heinz Marbaise <kh...@gmx.de>wrote:


> i observed a strange thing during a checkin process running where i got
> the following messages:
>
> Karl-Heinzs-MacBook-Pro:exec-maven-plugin kama$ svn ci -F x.diff
> Sending        src/it/mexec-100/pom.xml
> Sending        src/it/mexec-105/pom.xml
> Transmitting file data ..
> Committed revision 19310.
>

It looks like the commit worked.



> svn: E120108: Commit failed (details follow):
> svn: E120108: Error running context: The server unexpectedly closed the
> connection.
> svn: E120108: Additional errors:
> svn: E120108: Error running context: The server unexpectedly closed the
> connection.
>

And the failure came in the post-commit updating of your working copy to
reflect this.




-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/