[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Matthias Kraft commented on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error We are observing this issue with Jenkins 1.480.3 on RedHat Enterprise Linux Server and SUSE Linux Enterprise Server running on a Mainframe (s390x) using current IBM JDK 7 SR4. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Matthias Kraft edited a comment on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error We are observing this issue with Jenkins 1.480.3 on RedHat Enterprise Linux Server and SUSE Linux Enterprise Server running on a Mainframe (s390x) using current IBM JDK 7 SR4. A very interesting observation is that on AIX - which also doesn't have an Oracle JDK - a message appears: "Failed to load native POSIX impl; falling back on Java impl. Unsupported OS." - and everything seems to work out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Matthias Kraft edited a comment on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error We are observing this issue with Jenkins 1.480.3 on RedHat Enterprise Linux Server and SUSE Linux Enterprise Server running on a Mainframe (s390x) using current IBM JDK 7 SR4. A very interesting observation is that on AIX and HP-UX - which also don't have an Oracle JDK - a message appears: "Failed to load native POSIX impl; falling back on Java impl. Unsupported OS." - and everything seems to work out. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Matthias Kraft commented on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error A possible solution might be lined out in these comments: http://jira.codehaus.org/browse/JRUBY-6712 This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Jesse Glick commented on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error @makr: newer versions of Jenkins on Java 7+ will not exhibit this error because they use a different code path. By the way anyone using proprietary or unusual platforms should not expect that Jenkins core developers will be able to reproduce their problems. Debug it yourself and file a pull request if you want a prompt fix. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Valentin Baranov commented on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error We have the similar problem on Windows Server. Can you tell in which Jenkins version will the fix be available? This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Dave Hunt commented on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error We had a similar issue to this (but with Ubuntu slaves) that was resolved by switching to Oracle's JDK from Open JDK. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira -- You received this message because you are subscribed to the Google Groups Jenkins Issues group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Jesse Glick updated JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error @brevilo true but this was filed on Linux, for which Java 7 is available on all platforms I know about. Change By: Jesse Glick (23/Jan/13 5:04 PM) Summary: archiveartifactshangsonia64slave duetoJNAinitializationerror Component/s: ssh-slaves This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Oliver Bock commented on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error @jglick Agreed. I'd love to use this workaround on OS X as well. This (and/or the related issue) is a long standing issue that's really precluding us from doing actual CI right now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
[JIRA] (JENKINS-15682) archive artifacts hangs on ia64 slave due to JNA initialization error
Oliver Bock edited a comment on JENKINS-15682 archive artifacts hangs on ia64 slave due to JNA initialization error @jglick Agreed. I'd love to use this workaround on OS X 10.4 as well. This (and/or the related issue) is a long standing issue that's really precluding us from doing actual CI right now. This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira
