Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions test/src/test/java/hudson/util/AtomicFileWriterPerfTest.java
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,7 @@
import org.junit.Test;
import org.jvnet.hudson.test.Issue;
import org.jvnet.hudson.test.JenkinsRule;
import org.junit.Ignore;

public class AtomicFileWriterPerfTest {

Expand All @@ -22,7 +23,15 @@ public class AtomicFileWriterPerfTest {
* <p>
* So using slightly more than the worse value obtained above should avoid making this flaky and still catch
* <strong>really</strong> bad performance regressions.
*
* <p>Update December 2018: for some reason, this test started causing failures in CI suddenly.
* Was analyzed in https://github.com/jenkinsci/jenkins/pull/3788, to summarize the performances in ci.jenkins.io are
* wildly varying, to say the least, between 2.5 seconds, and 1 min 9 seconds!
*
* So bumping this here to 70 seconds, so we keep being able to catch huge regressions if someone touches the Jenkins
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

obsolete comment

* serialization lower layers/AtomicFileWriter...
*/
@Ignore("cf https://github.com/jenkinsci/jenkins/pull/3788 : flaky in CI for low storage performance apparently")
@Issue("JENKINS-34855")
@Test(timeout = 50 * 1000L)
public void poorManPerformanceTestBed() throws Exception {
Expand Down