-
Notifications
You must be signed in to change notification settings - Fork 114
[test] Add a test for cancellable #529
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
Open
sebsto
wants to merge
11
commits into
swift-server:main
Choose a base branch
from
sebsto:sebsto/test-cancellable
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+119
−31
Open
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
3b190c3
add a test for cancellable
sebsto abdda82
move service lifecycle test in a separate file
sebsto 4d3479a
license header
sebsto 36dc6f1
Merge branch 'main' into sebsto/test-cancellable
sebsto dcbda48
add more details error message + warning
sebsto 07a05df
add error code
sebsto bbe834f
add delay on test for cleaning up
sebsto 70dc8c1
increase test delay
sebsto b1527ff
increase test delay
sebsto de5e31c
change some test names for clarity
sebsto 14e80d9
put second runtime in a task group
sebsto File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
46 changes: 46 additions & 0 deletions
46
Tests/AWSLambdaRuntimeTests/LambdaRuntime+ServiceLifeCycle.swift
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,46 @@ | ||
//===----------------------------------------------------------------------===// | ||
// | ||
// This source file is part of the SwiftAWSLambdaRuntime open source project | ||
// | ||
// Copyright (c) 2024 Apple Inc. and the SwiftAWSLambdaRuntime project authors | ||
// Licensed under Apache License v2.0 | ||
// | ||
// See LICENSE.txt for license information | ||
// See CONTRIBUTORS.txt for the list of SwiftAWSLambdaRuntime project authors | ||
// | ||
// SPDX-License-Identifier: Apache-2.0 | ||
// | ||
//===----------------------------------------------------------------------===// | ||
|
||
#if ServiceLifecycleSupport | ||
@testable import AWSLambdaRuntime | ||
import ServiceLifecycle | ||
import Testing | ||
import Logging | ||
|
||
@Suite | ||
struct LambdaRuntimeServiceLifecycleTests { | ||
@Test | ||
func testLambdaRuntimeGracefulShutdown() async throws { | ||
let runtime = LambdaRuntime { | ||
(event: String, context: LambdaContext) in | ||
"Hello \(event)" | ||
} | ||
|
||
let serviceGroup = ServiceGroup( | ||
services: [runtime], | ||
gracefulShutdownSignals: [.sigterm, .sigint], | ||
logger: Logger(label: "TestLambdaRuntimeGracefulShutdown") | ||
) | ||
try await withThrowingTaskGroup(of: Void.self) { group in | ||
group.addTask { | ||
try await serviceGroup.run() | ||
} | ||
// wait a small amount to ensure we are waiting for continuation | ||
try await Task.sleep(for: .milliseconds(100)) | ||
|
||
await serviceGroup.triggerGracefulShutdown() | ||
} | ||
} | ||
} | ||
#endif |
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
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
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
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.
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.
When I run all the tests in parallel this test fails quite regularly as the second task gets run before the first. I don't think you can rely on a sleep to ensure the two tasks are run in order. Maybe you should care which order they run in, just that one throws a
LambdaRuntimeError
. Do the error check before thetaskGroup.next()
I'm pretty sure you can get rid of the test that you can run the second runtime after the failure. Is it really valid to have two separate runtimes, run in the the same lambda?