--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1bd559a1-7c52-4a60-91ad-9c2f97ebe8d5%40googlegroups.com.
Oleg, how does this test pass for you (and presumably the CI system that gated this change) with the interactiveBreak invocation intact?
I created https://github.com/jenkinsci/jenkins/pull/4142 to get us past this blockage.
On Tue, Aug 6, 2019 at 8:42 AM Kohsuke Kawaguchi <k...@kohsuke.org> wrote:
Thanks Lloyd. With Surefire 2.20.1, the error message changes more explicitly to timeout: https://gist.github.com/kohsuke/4d31b8dbcbfe1926e71ccba08f7f9555The test case in question includes an invocation of 'interactiveBreak', which is surely wrong? When I remove that line, the test passes.Oleg, how does this test pass for you (and presumably the CI system that gated this change) with the interactiveBreak invocation intact?
On Tue, Aug 6, 2019 at 12:57 AM Lloyd Chang <lloyd...@gmail.com> wrote:
clarification: the quoted version number "2.20.1" was Surefire, and not Jenkins.--
On Tuesday, August 6, 2019 at 12:36:21 AM UTC-7, Lloyd Chang wrote:> We have it fixed in 2.20.1.
On Monday, August 5, 2019 at 11:54:30 PM UTC-7, Oleg Nenashev wrote:I was unable to reproduce it locally on Maven 3.6.0 and Windows.Would it be possible to provide a crashdump?Thanks in advance,Oleg
On Tuesday, August 6, 2019 at 6:53:57 AM UTC+2, Kohsuke Kawaguchi wrote:Currently the release of 2.188 is stuck due to a failing jenkins.triggers.TriggerTest. The log is https://gist.github.com/kohsuke/7ba26b2d9f4a2a49d832610d069d0ab4I'll look into this further later, but if anyone has any thoughts on what might be wrong, that'd be greatly appreciated.--Kohsuke Kawaguchi
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 jenkin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1bd559a1-7c52-4a60-91ad-9c2f97ebe8d5%40googlegroups.com.
--Kohsuke Kawaguchi--Kohsuke Kawaguchi
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/l2vGNx289vE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5bae9334-db08-4753-b893-c8fb8187ccc2%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/5bae9334-db08-4753-b893-c8fb8187ccc2%40googlegroups.com.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAPfivLB5R0y3MYOUYHpSzZMsJCOMmUY1XiwtnAWY_b5pHaib0w%40mail.gmail.com.
--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1053517a-513b-4ba6-92ab-ca5c3abed392%40googlegroups.com.
I think 2.189 finally went through.
On Wed, Aug 7, 2019 at 7:57 AM Kohsuke Kawaguchi <k...@kohsuke.org> wrote:
Yep, still investigating. I'm burning 2.188 and moving to 2.189.
On Wed, Aug 7, 2019 at 5:41 AM Oleg Nenashev <o.v.n...@gmail.com> wrote:
It looks like the new release attempt did not go well--There was https://repo.jenkins-ci.org/snapshots/org/jenkins-ci/main/jenkins-war/2.188-SNAPSHOT/ deployed this night, and the release is not there so far.
On Tuesday, August 6, 2019 at 8:24:32 PM UTC+2, Jesse Glick wrote:On Tue, Aug 6, 2019 at 12:12 PM Oleg Nenashev <o.v.n...@gmail.com> wrote:
> Should we just mark the method as `@Restricted(NoExternalUse.class)` in JTH so that all production build fail by default?
Would have no effect—access modifiers are ignored in test sources.
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 jenkin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1053517a-513b-4ba6-92ab-ca5c3abed392%40googlegroups.com.
--Kohsuke Kawaguchi--Kohsuke Kawaguchi
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/98e5b0ea-9462-4cd7-bc65-bf91f7cdf87e%40googlegroups.com.
OK. Thanks for the heads-up
--To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/98e5b0ea-9462-4cd7-bc65-bf91f7cdf87e%40googlegroups.com.
Kohsuke Kawaguchi