13903449c7
Sometimes the upload that is supposed to fail due to excess usage would pass. This looks to be because it's overwriting another object uploaded earlier in the test and deleting the old pointer. If tally happened to run after the pointer is deleted but before the current upload reaches the live accounting check, it might pass through. The solution is to upload to a different path each time. Change-Id: Ie6c825b9c6eab9ed53426ae262e7997bcb6beb7f |
||
|---|---|---|
| .. | ||
| live | ||
| reportedrollup | ||
| rollup | ||
| tally | ||
| bucketstats.go | ||
| bucketusage.go | ||
| common.go | ||
| db_test.go | ||
| db.go | ||
| projectusage_test.go | ||
| projectusage.go | ||