Closed
Bug 1311903
Opened 8 years ago
Closed 8 years ago
Fix semantics of TTL update in batch uploads
Categories
(Cloud Services Graveyard :: Server: Sync, defect)
Cloud Services Graveyard
Server: Sync
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rfkelly, Unassigned)
References
Details
As noted in [1], there are two tests that are currently being skipped in the batch-uploads functional suite:
syncstorage/tests/functional/test_storage.py:TestStorage.test_batch_ttl_update
syncstorage/tests/functional/test_storage.py:TestStoragetest_batch_ttl_is_based_on_commit_timestamp
They're both related to TTLs and will faily if unskipped, it may imply that our TTL handling is incorrect.
[1] https://github.com/mozilla-services/server-syncstorage/issues/39
Reporter | ||
Comment 1•8 years ago
|
||
Fix in progress at https://github.com/mozilla-services/server-syncstorage/pull/44
Reporter | ||
Comment 2•8 years ago
|
||
The above-linked PR was merged.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•2 years ago
|
Product: Cloud Services → Cloud Services Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•