aboutsummaryrefslogtreecommitdiff
path: root/script
Commit message (Collapse)AuthorAgeFilesLines
* Merge branch 'main' into next-0.10v1.0.0next-0.10Alex Auvolat2024-04-104-13/+14
|\
| * [rel-0.9.4] upgrade version to v0.9.4v0.9.4Alex Auvolat2024-04-081-2/+2
| |
| * jepsen testing of Garage v1.0.0-rc1jepsen-1.0rc1Alex Auvolat2024-04-054-13/+14
| |
* | [next-0.10] bump helm chart versionAlex Auvolat2024-04-031-1/+1
| |
* | [next-0.10] bump version number to 1.0v1.0.0-rc1Alex Auvolat2024-03-281-1/+1
| |
* | [rm-sled] Remove the Sled database engineAlex Auvolat2024-03-081-11/+1
| |
* | [sse-c] Testing for SSE-C encryptionAlex Auvolat2024-03-071-0/+13
|/
* [rel-0.9.3] Bump version to 0.9.3v0.9.3Alex Auvolat2024-03-041-1/+1
|
* [rel-0.9.2] Bump version to v0.9.2v0.9.2rel-0.9.2Alex Auvolat2024-03-011-1/+1
|
* [fix-signed-headers] aws signatures v4: don't actually check Content-Type is ↵Alex Auvolat2024-03-011-3/+1
| | | | | | | | | | | | | | | | signed This page of the AWS docs indicate that Content-Type should be part of the CanonicalHeaders (and therefore SignedHeaders) strings in signature calculation: https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-header-based-auth.html However, testing with Minio Client revealed that it did not sign the Content-Type header, and therefore we broke CI by expecting it to be signed. With this commit, we don't mandate Content-Type to be signed anymore, for better compatibility with the ecosystem. Testing against the official behavior of S3 on AWS has not been done.
* Bump version to 0.9.1v0.9.1rel-v0.9.1Alex Auvolat2024-01-161-1/+1
|
* jepsen: updated results, confirming that task3 worksjepsenAlex Auvolat2023-12-1412-31/+96
|
* jepsen: nlnet task3a seems to fix thingsAlex Auvolat2023-11-162-3/+9
|
* jepsen: add patch and use more complete namesAlex Auvolat2023-11-161-2/+3
|
* jepsen: testingAlex Auvolat2023-10-253-3/+13
|
* jepsen: use 7 nodesAlex Auvolat2023-10-253-0/+4
|
* jepsen: failures with set2 test in --scenario rAlex Auvolat2023-10-251-6/+5
|
* jepsen: fix set2 test omg finally this is so stupidAlex Auvolat2023-10-251-1/+1
|
* jepsen: reconfigure nemesis + add db nemesisAlex Auvolat2023-10-256-107/+134
|
* jepsen: got a failure with set1Alex Auvolat2023-10-241-5/+4
|
* jepsen: fix nemesis to actually generate many operationsAlex Auvolat2023-10-241-24/+33
|
* jepsen: set1 and set2 don't fail anymore ??Alex Auvolat2023-10-243-40/+47
|
* jepsen: more testingAlex Auvolat2023-10-245-35/+84
|
* jepsen: update readmeAlex Auvolat2023-10-201-2/+2
|
* jepsen: code path for nemesis final generatorAlex Auvolat2023-10-202-22/+24
|
* jepsen: add cluster reconfiguration nemesisAlex Auvolat2023-10-204-14/+106
|
* jepsen: register crdt read-after-write is fixed with deleteobject patchAlex Auvolat2023-10-204-9/+9
|
* jepsen: reg2 failure seems to happen only with deleteobjectAlex Auvolat2023-10-203-7/+30
|
* jepsen: errors in reg2 workload under investigationAlex Auvolat2023-10-203-17/+41
|
* jepsen: wip checker for register-like behaviorAlex Auvolat2023-10-201-4/+62
|
* jepsen: fix the list-objects call (?)Alex Auvolat2023-10-193-28/+52
|
* jepsen: investigating listobjects errorAlex Auvolat2023-10-195-10/+39
|
* jepsen: refactoringAlex Auvolat2023-10-195-30/+70
|
* make jepsen test more robust: handle errors and timeouts, fixed access keyAlex Auvolat2023-10-183-26/+36
|
* refactor jepsen codeAlex Auvolat2023-10-185-77/+83
|
* refactor jepsen setup logicAlex Auvolat2023-10-182-47/+96
|
* jepsen: update jepsen and fix garage key infoAlex Auvolat2023-10-182-2/+2
|
* jepsen: update to garage 0.9.0Alex Auvolat2023-10-182-6/+10
|
* reformattingAlex Auvolat2023-10-182-11/+8
|
* Check read-after-write property for setsAlex Auvolat2023-10-181-5/+43
|
* set tests with independant tests togetherAlex Auvolat2023-10-182-20/+42
|
* two set workloads with different checkersAlex Auvolat2023-10-183-8/+18
|
* Add garage set test (this one works :p)Alex Auvolat2023-10-185-21/+95
|
* refactor jepsen testAlex Auvolat2023-10-183-155/+244
|
* remove useless filesAlex Auvolat2023-10-185-310/+3
|
* the fix for increasing timestamps does not make things linearizableAlex Auvolat2023-10-181-2/+3
|
* even without nemesis, s3 get/put/delete is not linearizable (is this normal?)Alex Auvolat2023-10-183-37/+64
|
* better match exceptionsAlex Auvolat2023-10-181-9/+11
|
* jepsen: s3 gets and putsAlex Auvolat2023-10-187-102/+141
|
* jepsen connects to vagrant vmsAlex Auvolat2023-10-188-124/+38
|
generated by cgit v1.2.3 (git 2.25.1) at 2024-11-10 03:48:24 +0000