apparently spurious failure in allmydata.test.test_storage.BucketCounter.test_bucket_counter

[davidsarah]

​http://tahoe-lafs.org/buildbot/builders/FreeStorm%20WinXP-x86%20py2.6/builds/203/steps/test/logs/stdio (wrapped)

[FAIL]: allmydata.test.test_storage.BucketCounter.test_bucket_counter

Traceback (most recent call last):
  File "c:\buildbot_tahoe\freestorm_winxp-x86_py2.6\build\src\allmydata
\test\test_storage.py", line 1448, in _check2
    self.failUnlessIn("Next crawl in 59 minutes", s)
twisted.trial.unittest.FailTest: 'Next crawl in 59 minutes' not in
' Tahoe-LAFS - Storage Server Status Storage Server Status Total disk
 space: 32.20 GB (32201936896) Disk space used: - 6.80 GB (6799753216) ======
 Disk space free (root): 25.40 GB (25402183680) [see 1] Disk space free
 (non-root): 25.40 GB (25402183680) [see 2] Reserved space: - 0 B (0) ======
 Space Available to Tahoe: 25.40 GB (25402183680) Accepting new shares: Yes
 Total buckets: 0 (the number of files and directories for which this server
 is holding a share) Next crawl in 60 minutes (estimated cycle time 63ms)
 Lease Expiration Crawler Expiration Disabled: scan-only mode, no leases
 will be removed Leases will expire naturally, probably 31 days after creation
 or renewal. The following sharetypes will be expired: immutable mutable.
 Next crawl in 5 minutes [1]: Some of this space may be reserved for the
 superuser. [2]: This reports the space available to non-root users, including
 the Tahoe-LAFS node. See this page in JSON '
-------------------------------------------------------------------------------

Notice "Next crawl in 60 minutes" instead of the expected "Next crawl in 59 minutes".

(This is the ticket1074 branch, but I don't think that's relevant to this failure.)

[warner]

I think ffd1c5aca51fc56d was meant to fix this, but it looks like the checkin-comment-scanner didn't spot the instructions to close this ticket.

[davidsarah]

Replying to warner:

I think ffd1c5aca51fc56d was meant to fix this,

You mean f10f9a8646cc72b0.

but it looks like the checkin-comment-scanner didn't spot the instructions to close this ticket.

Right, not sure why.

The last build on Freestorm's XP buildslave where this failed was ​212, and it hasn't failed since f10f9a8646cc72b0 was applied, so marking this as fixed.