tree ba9fca18d6e553253264d92254f3fba20943b1df
parent cb15ed5365a633e91b67c4b6680f6dd5a3fc8ef5
author Jean de Klerk <deklerk@google.com> 1553100969 -0600
committer Jean de Klerk <deklerk@google.com> 1553102718 +0000

storage: relax bucket and object deletion

Currently, TestIntegration_UpdateRetentionExpirationTime creates a
bucket and an object, sets a bucket RetentionPeriod, checks the
RetentionPeriod was set in the server, then sets the RetentionPeriod to
0 and deletes the bucket and object.

However, a RetentionPeriod of less than a day is explicitly called out
as best effort and not guaranteed.

Therefore, occasionally our tests fail in the cleanup step because the
RetentionPeriod is still active (the 0 has not been propogated).

This CL changes the test to log the error rather than fail on the error.
The next time tests get run, the test init step tries to clean up
outstanding buckets, so we'll eventually have the cleanup behavior.

Fixes #1284

Change-Id: I28572bbfddbaf1df3e56dd163dbff1e7a64667f6
Reviewed-on: https://code-review.googlesource.com/c/gocloud/+/39190
Reviewed-by: Emmanuel Odeke <emmanuel@orijtech.com>