#2313 closed defect (wontfix)

why did test_filesystem take 494 seconds on the "sickness OpenBSD 5.0 x86 py2.7" builder?

Reported by: daira Owned by:
Priority: normal Milestone: undecided
Component: code Version: 1.10.0
Keywords: performance tests Cc:
Launchpad Bug:

Description (last modified by daira)


allmydata.test.test_system.SystemTest.test_debug_trial ... [OK]
(15.317 secs)
allmydata.test.test_system.SystemTest.test_filesystem ... [OK]
(494.061 secs)
allmydata.test.test_system.SystemTest.test_filesystem_with_cli_in_subprocess ... [OK]
(75.674 secs)
allmydata.test.test_system.SystemTest.test_mutable ... [OK]
(39.956 secs)

Change History (3)

comment:1 Changed at 2014-09-30T19:46:06Z by daira

  • Description modified (diff)

comment:2 Changed at 2014-10-03T17:42:43Z by sickness

Well that buildbot (hosted by me) is on a cheap VPS, so maybe the slowness could be caused by some virtualization layer, or maybe the HOST was overloaded at the time the test did run? I've also noted that sometimes test processes tend to hang there and so I have to reboot the buildbot to take it to a "clean" state again, if you want I can reboot it now and then we can try that test again. (As a side note that VPS is not on OpenBSD 5.0 anymore but it's OpenBSD 5.2, but I'd like to update it to a more recent version like 5.5 or 5.6 as soon as it comes out)

comment:3 Changed at 2020-01-13T20:15:38Z by exarkun

  • Resolution set to wontfix
  • Status changed from new to closed

test_filesystem is frequently slow. It does a huge number of things, many of which are extremely expensive. This doesn't seem especially notable, though in general it would be good for all of test_system to be improved.

The OpenBSD builder is gone and whatever strange happened to a build on it 6 years ago is probably practically lost to the mists of time.

Note: See TracTickets for help on using tickets.