[TestUnit]Failed: FunctionPullingContainerPoolTests, ActionsApiTests, BasicAuthenticateTests, PackageActionsApiTests
- Dominant language
- Scala
- Stars
- 6.8k
- Forks
- 1.2k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 2
Description
[FunctionPullingContainerPoolTests] failed:
ContainerPool should retry when chosen warmed container is failed to resume
ContainerPool should send ack(success) to scheduler when chosen warmed container is resumed
ContainerPool should use a warmed container when invocationNamespace, action and revision matched
[ActionsApiTests]
Actions API should concurrently get an action with attachment that is not cached
Actions API should ensure WhiskActionMetadata is used to invoke an action
Actions API should ensure old and new action schemas are supported
Actions API should get action using code query parameter
...................
Contributor guide
Research direction
Start by reproducing FunctionPullingContainerPoolTests and the listed ActionsApiTests failures, then inspect the failing assertions and surrounding test setup. Trace the affected container-pool and Actions API entry points to determine whether the failures share a cause. Done means the named tests pass, including warmed-container retry and acknowledgment behavior and the listed action retrieval cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- backend-api-design, cloud, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100