> On Mar 22, 2016, at 19:20, Jesse Glick <[email protected]> wrote: > > On Sun, Mar 20, 2016 at 12:01 PM, Kanstantsin Shautsou > <[email protected]> wrote: >> AFAIR it only warning and you could ignore it. > > Yes, I think it is a bug in Remoting, probably not your fault. > > -- > You received this message because you are subscribed to a topic in the Google > Groups "Jenkins Developers" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-dev/tTJG_6eiWPg/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/jenkinsci-dev/CANfRfr0DfZGzHuRBo38qv_eG8cKabWWC84aN_VfN8wnK60og-A%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. I see difference traces when dealing with cloud. I.e. ServletException class not found for some magic getShel call. Sometimes i think async monitors causing traces because slave closed and deleted and some async work is in progress. Maybe Stephen C. knows where is architecture issue in all this async/sync work.
-- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2395E2FF-0D4B-4410-9126-8C685C5E467B%40gmail.com. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Message signed with OpenPGP using GPGMail
