-
Notifications
You must be signed in to change notification settings - Fork 29
ci: update the tests for no data lost #715
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
daipom
merged 2 commits into
fluent:feature-nodowntime
from
Watson1978:update-data-lost-test
Nov 11, 2024
Merged
ci: update the tests for no data lost #715
daipom
merged 2 commits into
fluent:feature-nodowntime
from
Watson1978:update-data-lost-test
Nov 11, 2024
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
f9cc00c to
6ad32e5
Compare
Update the test to make sure there are no problems even if the Ruby version is updated Signed-off-by: Shizuo Fujita <[email protected]>
56c98dc to
45d2e15
Compare
Signed-off-by: Shizuo Fujita <[email protected]>
45d2e15 to
6f46354
Compare
daipom
approved these changes
Nov 11, 2024
Contributor
daipom
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
kenhys
pushed a commit
that referenced
this pull request
Nov 19, 2024
Update the test to ensure : * There is no issue even if an upgrade is performed that includes a Ruby major version update. * There is no data loss even if data is sent until the main process is replaced. --------- Signed-off-by: Shizuo Fujita <[email protected]>
daipom
pushed a commit
to daipom/fluent-package-builder
that referenced
this pull request
Nov 29, 2024
Update the test to ensure : * There is no issue even if an upgrade is performed that includes a Ruby major version update. * There is no data loss even if data is sent until the main process is replaced. --------- Signed-off-by: Shizuo Fujita <[email protected]>
daipom
pushed a commit
to daipom/fluent-package-builder
that referenced
this pull request
Dec 4, 2024
Update the test to ensure : * There is no issue even if an upgrade is performed that includes a Ruby major version update. * There is no data loss even if data is sent until the main process is replaced. --------- Signed-off-by: Shizuo Fujita <[email protected]>
daipom
pushed a commit
to daipom/fluent-package-builder
that referenced
this pull request
Dec 5, 2024
Update the test to ensure : * There is no issue even if an upgrade is performed that includes a Ruby major version update. * There is no data loss even if data is sent until the main process is replaced. --------- Signed-off-by: Shizuo Fujita <[email protected]>
daipom
pushed a commit
to daipom/fluent-package-builder
that referenced
this pull request
Dec 6, 2024
Update the test to ensure : * There is no issue even if an upgrade is performed that includes a Ruby major version update. * There is no data loss even if data is sent until the main process is replaced. --------- Signed-off-by: Shizuo Fujita <[email protected]> Signed-off-by: Daijiro Fukuda <[email protected]>
daipom
pushed a commit
to daipom/fluent-package-builder
that referenced
this pull request
Dec 10, 2024
Update the test to ensure : * There is no issue even if an upgrade is performed that includes a Ruby major version update. * There is no data loss even if data is sent until the main process is replaced. --------- Signed-off-by: Shizuo Fujita <[email protected]> Signed-off-by: Daijiro Fukuda <[email protected]>
kenhys
pushed a commit
that referenced
this pull request
Dec 11, 2024
Update the test to ensure : * There is no issue even if an upgrade is performed that includes a Ruby major version update. * There is no data loss even if data is sent until the main process is replaced. --------- Signed-off-by: Shizuo Fujita <[email protected]> Signed-off-by: Daijiro Fukuda <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update the test to ensure :