automate testing of large files #435

New Issue

zooko · 2008-06-02T19:15:02Z

zooko commented

2008-06-02 19:15:02 +00:00

Per #346 (increase share-size field to 8 bytes, remove 12GiB filesize limit), it appears that we've deployed some bugs in Tahoe v1.0 which only manifest when you try to upload a file larger than about 4 billion bytes.

This reminds us that we really want to have automated testing for these parts of the code. This ticket is to make a test which is automated in the sense that a human isn't required to do anything in order to perform the test and collect the results. There will be a separate ticket for the separate question of whether tests of large files should be automatically launched by e.g. a buildbot policy without human intervention.

Per #346 (increase share-size field to 8 bytes, remove 12GiB filesize limit), it appears that we've deployed some bugs in Tahoe v1.0 which only manifest when you try to upload a file larger than about 4 billion bytes. This reminds us that we really want to have automated testing for these parts of the code. This ticket is to make a test which is automated in the sense that a human isn't required to do anything in order to perform the test and collect the results. There will be a separate ticket for the separate question of whether tests of large files should be automatically *launched* by e.g. a buildbot policy without human intervention.

zooko added the

labels 2008-06-02 19:15:02 +00:00

zooko added this to the 1.1.0 milestone 2008-06-02 19:15:02 +00:00

zooko commented

2008-06-02 20:27:30 +00:00

See also #437 (automatically schedule tests of large files).

zooko commented

2009-03-28 19:40:52 +00:00

Moving this out of the 1.3.1 Milestone.

zooko added this to the eventually milestone 2009-03-28 19:40:52 +00:00

zooko commented

2010-10-22 15:48:57 +00:00

This was long ago fixed by changeset:6c4019ec33e7a253 (see also changeset:466014f66fbccff7, changeset:8c37b8e3af2f4d1b).

(But see also #437 (automatically scheduled tests of large files).)

This was long ago fixed by changeset:6c4019ec33e7a253 (see also changeset:466014f66fbccff7, changeset:8c37b8e3af2f4d1b). (But see also #437 (automatically scheduled tests of large files).)

zooko added the

fixed

label 2010-10-22 15:48:57 +00:00

zooko closed this issue

2010-10-22 15:48:57 +00:00

davidsarah commented

2010-10-22 23:42:38 +00:00

Replying to zooko:

This was long ago fixed by changeset:6c4019ec33e7a253 (see also changeset:466014f66fbccff7, changeset:8c37b8e3af2f4d1b).

Well, [test_large_share]source:src/allmydata/test/test_storage.py@4665#L267 is currently disabled. But yes, the test exists, and it passed last time I tested it on my machine (Windows), during the 1.8.0 release process.

Perhaps the test could detect platforms that are known to support sparse files, so that we can reenable it on those platforms? That would be a reasonable alternative to #437, I think.

Replying to [zooko](/tahoe-lafs/trac-2024-07-25/issues/435#issuecomment-66692): > This was long ago fixed by changeset:6c4019ec33e7a253 (see also changeset:466014f66fbccff7, changeset:8c37b8e3af2f4d1b). Well, [test_large_share]source:src/allmydata/test/test_storage.py@4665#L267 is currently disabled. But yes, the test exists, and it passed last time I tested it on my machine (Windows), during the 1.8.0 release process. Perhaps the test could detect platforms that are known to support sparse files, so that we can reenable it on those platforms? That would be a reasonable alternative to #437, I think.

Sign in to join this conversation.