Re: Speeding up the ATH

> Am 28.09.2017 um 20:51 schrieb Stephen Connolly > : > > > On Thu 28 Sep 2017 at 19:11, Mark Waite > wrote: > On Thu, Sep 28, 2017 at 11:43 AM Jesse Glick

Re: Speeding up the ATH

On Thu, Sep 28, 2017 at 6:31 PM, Ullrich Hafner wrote: > In order to verify core PRs just use the smoke tests. You can select the > corresponding tests on your own by changing the annotated tests. Yes I have seen this, though I think there is no one really keeping

Re: Speeding up the ATH

> Am 28.09.2017 um 16:42 schrieb Mark Waite : > > > [..] > > Do we have any way of associating historical acceptance test harness failures > to a cause of those failures? > I found a lot of regressions in my plugins with theses tests, though I don’t have any

Re: Speeding up the ATH

> Am 28.09.2017 um 15:45 schrieb Jesse Glick : > > After the fiasco of Jenkins 2.80 some of us have been discussing ways > to speed up `acceptance-test-harness` to the point where it would be > practical to run all or part of it against core more frequently, > perhaps even

Re: Speeding up the ATH

On Thu 28 Sep 2017 at 20:33, Jesse Glick wrote: > On Thu, Sep 28, 2017 at 2:51 PM, Stephen Connolly > wrote: > > writing good acceptance tests is a high skill and not something that > > can be easily crowdsourced. > > Agreed. In particular

Re: Speeding up the ATH

On Thu, Sep 28, 2017 at 2:51 PM, Stephen Connolly wrote: > writing good acceptance tests is a high skill and not something that > can be easily crowdsourced. Agreed. In particular we should not be asking GSoC contributors to write new acceptance tests. Every PR

Re: Speeding up the ATH

On Thu 28 Sep 2017 at 19:11, Mark Waite wrote: > On Thu, Sep 28, 2017 at 11:43 AM Jesse Glick wrote: > >> On Thu, Sep 28, 2017 at 10:42 AM, Mark Waite >> wrote: >> > Do we have any way of associating historical

Re: Speeding up the ATH

On Thu, Sep 28, 2017 at 2:11 PM, Mark Waite wrote: > Would we consider a policy that flaky tests are deleted, rather than > tolerated? Or `@Ignore`d, sure. > I've understood that Kent Beck has mentioned that they delete flaky tests at > facebook, rather than just

Re: Speeding up the ATH

On Thu, Sep 28, 2017 at 11:43 AM Jesse Glick wrote: > On Thu, Sep 28, 2017 at 10:42 AM, Mark Waite > wrote: > > Do we have any way of associating historical acceptance test harness > > failures to a cause of those failures? > > Not that I am

Re: Speeding up the ATH

On Thu, Sep 28, 2017 at 10:42 AM, Mark Waite wrote: > Do we have any way of associating historical acceptance test harness > failures to a cause of those failures? Not that I am aware of. > could such data be gathered from some sample of recent runs of the >

Re: Speeding up the ATH

(replies inline) On Thu, 28 Sep 2017, Jesse Glick wrote: > After the fiasco of Jenkins 2.80 some of us have been discussing ways > to speed up `acceptance-test-harness` to the point where it would be > practical to run all or part of it against core more frequently, > perhaps even in core PR

Re: Debugging HtmlUnit: FailingHttpStatusCodeException 500 Server Error

Ooh, right, thanks! In case there will be another newbie reading this: The output from "mvn package" contains the last exception thrown, but it's not the whole log! Running the individual test gave the full log: mvn test -Dtest=com.google.jenkins.plugins.storage.ClassicUploadStepTest In my

Re: Speeding up the ATH

On Thu, Sep 28, 2017 at 7:45 AM Jesse Glick wrote: > After the fiasco of Jenkins 2.80 some of us have been discussing ways > to speed up `acceptance-test-harness` to the point where it would be > practical to run all or part of it against core more frequently, > perhaps

Speeding up the ATH

After the fiasco of Jenkins 2.80 some of us have been discussing ways to speed up `acceptance-test-harness` to the point where it would be practical to run all or part of it against core more frequently, perhaps even in core PR builds. Part of the problem is that the test infrastructure has a ton

Re: Debugging HtmlUnit: FailingHttpStatusCodeException 500 Server Error

A 500 server error is an indication that an exception was thrown in the backend when the http request was made. You should see another stacktrace in the log just before the FailingHttpstatusCodeException. /B 2017-09-27 22:53 GMT+02:00 'Alexandra Goultiaeva' via Jenkins Developers <

Jenkins 2.73.2 LTS RC testing started

Hello everyone, Latest LTS RC was made public and it is ready to be tested. Release is scheduled for 2017-10-11. Report your findings in this thread or on the test plan wiki page. Download bits from http://mirrors.jenkins-ci.org/war-stable-rc/2.73.2/jenkins.war Check community maintained LTS