'Bad file descriptor' after checkout from Jenkins

[Kristian]

Hey,

I have a strange problem: I have downloaded the source code of a project under a Windows 7, unzipped it and committed the source code as it was into a svn repo.

Then, Jenkins checked out that project to a CentOS 7 32bit slave. On that machine, I tried to start a configure script manually, but I get a lot of 'Bad file descriptor' messages. Then I deleted that file, and updated the directory with local svn command.

I tried to start the configure script again, and it worked.

In the job, the setting "Repository Browser" was set to "(Auto)".

Is that a problem of Jenkins? Or is there a setting of myself, which generates this strange behaviour.

Additional information:

* svn --version gives:
svn, version 1.9.2 (r1703836)
   compiled Oct 29 2015, 18:34:58 on i686-pc-linux-gnu

Copyright (C) 2015 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.3.8
  - handles 'http' scheme
  - handles 'https' scheme

The following authentication credential caches are available:

* Plaintext cache in /root/.subversion
* GPG-Agent