aws / aws/aws-toolkit-vscode

CI: failing CodeCatalyst E2E test: updateDevEnvironment causes InternalException

Open
#3,339 6 comments 0 reactions 0 assignees View on GitHub
service:codecatalyst tests-ci-cd
Dominant language
TypeScript
Stars
2k
Forks
807
Avg merge
10h 12m
Merged PRs (30d)
7

Description

## Problem

CC e2e tests failing on https://github.com/aws/aws-toolkit-vscode/commit/61bbc248221ac21e30fa74aaec20a12cae59c10a

```
1) Test how this codebase uses the CodeCatalyst API
Dev Environment functionality
connects to a running Dev Environment:
Error: Dev Environment failed to start (FAILED): test-alias-16817597…
at /codebuild/output/src753672424/src/github.com/aws/aws-toolkit-vscode/src/shared/clients/codecatalystClient.ts:534:27
at processTicksAndRejections (node:internal/process/task_queues:96:5)

2) Test how this codebase uses the CodeCatalyst API
Dev Environment functionality
stops a running Dev Environment, then starts it up again:
Error: Dev env 8c7c9a6c-4ed4-4b5c-8626-33024bc7b708 did not transition to one of the following statuses before timeout: "RUNNING"
at backend_1 (src/testE2E/codecatalyst/client.test.ts:528:23)
at Generator.next ()
at fulfilled (src/testE2E/codecatalyst/client.test.ts:9:58)
at processTicksAndRejections (node:internal/process/task_queues:96:5)

3) Test how this codebase uses the CodeCatalyst API
Dev Environment functionality
updates the properties of an existing dev environment:
InternalException: An internal error has occurred while processing your request
```

## Full build log

- [buildlog.txt.gz](https://github.com/aws/aws-toolkit-vscode/files/11255432/buildlog.txt.gz)

## Solution

- ✅ does it need to be reported to the service team?
- is it a false positive? can the test harness make this clearer (by reporting relevant info, but not too much info, in the logs), or guard against it?
- print the related request-id with the failure?

Contributor guide

Open the contributing guide

Research direction

Start with src/testE2E/codecatalyst/client.test.ts around line 528 and src/shared/clients/codecatalystClient.ts around line 534, then review the linked full build log. Determine whether the failures are a service issue or a false positive, and whether diagnostics or guarding should change; done means the failure cause and an actionable test-harness or reporting change are established.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, typescript
Domain
cloud, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.