found a post on builds mailing list with another example of this.
That thread said:
Apparently, Pulsar jobs went wild.
There are 14 processes which consume 9000+ threads
Maybe they'll fix this...
-Marshall
On 1/17/2020 3:24 PM, Richard Eckart de Castilho wrote:
> On 17. Jan 2020, at 21:10,
On 17. Jan 2020, at 21:10, Marshall Schor wrote:
>
> java.lang.OutOfMemoryError: unable to create new native thread
Could be that too many Maven builds crashed/failed on that slave and caused old
Maven processes to hang around. There is a known bug for this on Jenkins since
ages.
Exclude
Now getting a related error:
getting pretty solid Jenkins failure on git pull request:
[Apache UIMA Java SDK (GitHub PR)] $
/home/jenkins/tools/java/latest1.8/bin/java -Xmx4g -Xms4g -cp
[
https://issues.apache.org/jira/browse/UIMA-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17018272#comment-17018272
]
Marshall Schor commented on UIMA-6128:
--
It's being added for both XMI and XCas for both UIMA v2 and
[
https://issues.apache.org/jira/browse/UIMA-6128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marshall Schor updated UIMA-6128:
-
Fix Version/s: 2.10.5SDK
> Allow XMI to be optionally serialized with XML 1.1 instead of only 1.0
[
https://issues.apache.org/jira/browse/UIMA-6128?focusedWorklogId=373792=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-373792
]
ASF GitHub Bot logged work on UIMA-6128:
Author: ASF GitHub Bot
in my case, I was running mvn clean install on uimaj-core (by itself); the test
phase was somehow finding some v2 tests even though I had v3 checked out, and my
windows file explorer (and eclipse) both showed no such test files were in the
working dir.
I probably made some foolish kind of error
On 17. Jan 2020, at 18:02, Marshall Schor wrote:
>
> I guess a moral of this story is to not do git switch between uima v2 and v3,
> but instead do something that erases the local working directory, and then
> does
> a checkout again.
When I do a switch between v2 and v3, I always run a "mvn
While working on UIMA-6128, I at one point switched my local repo to master,
made a new branch from this, and merged into that the v2 master, to pick up the
6128 change.
To my surprise, when I tried running a test build on uimaj-core (which had the
changes), the test failed, running 2 test
after maybe 5 retries, it seems to have worked...
On 1/17/2020 10:52 AM, Marshall Schor wrote:
> Hi,
>
> I'm getting pretty solid git pull Jenkins build errors of the form :
>
> fatal: unable to create thread: Resource temporarily unavailable
> fatal: index-pack failed
>
> when the Jenkins tries
Hi,
I'm getting pretty solid git pull Jenkins build errors of the form :
fatal: unable to create thread: Resource temporarily unavailable
fatal: index-pack failed
when the Jenkins tries to check out the Pull Request. Googling this shows other
apache projects get this from time to time. Is there
[
https://issues.apache.org/jira/browse/UIMA-6128?focusedWorklogId=373632=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-373632
]
ASF GitHub Bot logged work on UIMA-6128:
Author: ASF GitHub Bot
12 matches
Mail list logo
