allthingssecurity commented on PR #28137: URL: https://github.com/apache/camel/pull/28137#issuecomment-6285553505
CI failures, fixed in 48ca9f8c3b48. All three tests asserted the behaviour this PR changes: - `S3StreamUploadTimestampNamingStrategyIT` required the base file `fileTest.txt`, and this PR removes it: the first upload is now timestamped too. The test now checks that all 40 keys are `fileTest-<timestamp>.txt` with a timestamp inside the run, and that no `fileTest.txt` exists. The 80 and 120 counts in the CI log came from surefire reruns in the same bucket. - `S3StreamUploadTimestampTimeoutIT`, iteration 2: the first object listed is iteration 1's `fileTest-<ts1>.txt`, and `ts1` is earlier than iteration 2's start, so the range assert failed. Awaitility retried until the timer uploaded iteration 2's object, and then the count was `expected: <1> but was: <2>`. Before this PR, iteration 2 replaced iteration 1's object. Iteration i now expects i objects, all timestamp-named within the run, with a total size of 9 × 23 × i bytes. - `S3StreamUploadTimeoutIT` (random naming) has the same shape. It passed only because it listed before the timer ran. I changed it the same way: i objects, 7 × 23 × i bytes. The camel-aws2-s3 unit tests pass (106 run, 0 failures). I could not run the ITs locally (no Docker here), so CI will be their first run. This branch and #28136 still merge cleanly (checked with `git merge-tree`). _Claude Code on behalf of allthingssecurity_ -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
