[JIRA] (JENKINS-46523) FATAL: Could not initialize class hudson.util.ProcessTree$UnixReflection

2 views
Skip to first unread message

o.v.nenashev@gmail.com (JIRA)

unread,
Sep 26, 2018, 11:44:04 AM9/26/18
to jenkinsc...@googlegroups.com
Oleg Nenashev reopened an issue
 

The issue is still there. I see it in Java 11 tests

 
Jenkins / Bug JENKINS-46523
FATAL: Could not initialize class hudson.util.ProcessTree$UnixReflection
Change By: Oleg Nenashev
Resolution: Postponed
Status: Closed Reopened
Assignee: Daniel Heid Oleg Nenashev
Add Comment Add Comment
 
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

o.v.nenashev@gmail.com (JIRA)

unread,
Sep 26, 2018, 11:44:04 AM9/26/18
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
Change By: Oleg Nenashev
Component/s: core
Component/s: postbuildscript-plugin

o.v.nenashev@gmail.com (JIRA)

unread,
Sep 26, 2018, 11:44:06 AM9/26/18
to jenkinsc...@googlegroups.com

o.v.nenashev@gmail.com (JIRA)

unread,
Oct 1, 2018, 5:59:06 PM10/1/18
to jenkinsc...@googlegroups.com
Change By: Oleg Nenashev
Status: Fixed but Unreleased Resolved

o.v.nenashev@gmail.com (JIRA)

unread,
Oct 1, 2018, 5:59:07 PM10/1/18
to jenkinsc...@googlegroups.com
Change By: Oleg Nenashev
Status: Reopened Fixed but Unreleased
Resolution: Fixed
Released As: Jenkins 2.144

o.v.nenashev@gmail.com (JIRA)

unread,
Oct 3, 2018, 5:57:35 PM10/3/18
to jenkinsc...@googlegroups.com
Oleg Nenashev updated an issue
Change By: Oleg Nenashev
Labels: java11

timur.suleimanov.ukraine@gmail.com (JIRA)

unread,
Jan 21, 2019, 10:24:02 AM1/21/19
to jenkinsc...@googlegroups.com

arunp1990@gmail.com (JIRA)

unread,
Jul 10, 2019, 8:07:05 AM7/10/19
to jenkinsc...@googlegroups.com

I also faced this issue intermittently. But, the no. of occurrences of failure is really high compared to success. Adding a sleep of 4 minutes at the end of script made it work. Artifactory plugin publishes artifacts after the script finishes. Somehow artifacts are always published, but afterwards, this error happens.

The issue was not reproducible for iOS build happening on the same slave machine. Only Android build had this issue. So, I did not explore along the line of java version problem mentioned here.
Reply all
Reply to author
Forward
0 new messages