distribution/registry/storage/driver
Stephen J Day 0322c3bf1f registry/storage/driver: checking that non-existent path returns PathNotFoundError
Issue #1186 describes a condition where a null tags response is returned when
using the s3 driver. The issue seems to be related to a missing
PathNotFoundError in s3. This change adds a test for that to get an idea of the
lack of compliance across storage drivers. If the failures are manageable,
we'll add this test condition and fix the s3 driver.

Signed-off-by: Stephen J Day <stephen.day@docker.com>
2015-12-08 12:04:03 -08:00
..
azure Remove half-baked Storage Driver IPC support 2015-06-29 16:52:12 -07:00
base Add a generic error type to capture non-typed errors 2015-11-03 11:19:44 -08:00
factory Remove half-baked Storage Driver IPC support 2015-06-29 16:52:12 -07:00
filesystem Add a generic error type to capture non-typed errors 2015-11-03 11:19:44 -08:00
gcs Add a generic error type to capture non-typed errors 2015-11-03 11:19:44 -08:00
inmemory Add a generic error type to capture non-typed errors 2015-11-03 11:19:44 -08:00
middleware Make Storage Driver API calls context aware. 2015-04-27 15:58:58 -07:00
oss Add a generic error type to capture non-typed errors 2015-11-03 11:19:44 -08:00
rados Add a generic error type to capture non-typed errors 2015-11-03 11:19:44 -08:00
s3 Add a generic error type to capture non-typed errors 2015-11-03 11:19:44 -08:00
swift Use bulk delete to remove segments in Swift driver 2015-12-04 12:16:49 +01:00
testsuites registry/storage/driver: checking that non-existent path returns PathNotFoundError 2015-12-08 12:04:03 -08:00
fileinfo.go Move storagedriver package to registry/storage/driver 2015-02-11 12:43:04 -08:00
storagedriver.go Fix comment for PathRegexp 2015-12-04 22:14:21 +03:00