Skip to content

Conversation

@Hweinstock
Copy link
Contributor

@Hweinstock Hweinstock commented Jan 29, 2025

Problem

#6117
#6457

These issues keep popping up, regardless of the the thresholds. The performance tests are causing more problems then they are solving. Real performance regressions would be captured in telemetry.

Solution

skip all performance tests, revisit once there is less flakiness.


  • Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
  • Your code changes must meet the guidelines in CONTRIBUTING.md.
  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@Hweinstock
Copy link
Contributor Author

Hweinstock commented Jan 29, 2025

/runIntegrationTests

@jpinkney-aws
Copy link
Contributor

I wonder if we should just start skipping these since they're generating so much flakiness? Maybe we can re-visit them when they're in flare and gets a much more accurate number

@Hweinstock
Copy link
Contributor Author

Yeah, I think thats likely for the best. It doesn't seem to matter how hight the thresholds are set, it somehow always breaks it.

@Hweinstock Hweinstock changed the title test(flaky): increase thresholds for flaky performance tests. test(flaky): skip all performance tests. Jan 29, 2025
@github-actions
Copy link

  • This pull request modifies code in src/* but no tests were added/updated.
    • Confirm whether tests should be added or ensure the PR description explains why tests are not required.

@Hweinstock Hweinstock marked this pull request as ready for review January 29, 2025 17:06
@Hweinstock Hweinstock requested a review from a team as a code owner January 29, 2025 17:06
@Hweinstock Hweinstock merged commit 82cae41 into aws:master Jan 31, 2025
29 of 32 checks passed
@Hweinstock Hweinstock deleted the perf/flaky branch January 31, 2025 16:32
s7ab059789 pushed a commit to s7ab059789/aws-toolkit-vscode that referenced this pull request Feb 19, 2025
## Problem
aws#6117
aws#6457

These issues keep popping up, regardless of the the thresholds. The
performance tests are causing more problems then they are solving. Real
performance regressions would be captured in telemetry.

## Solution
skip all performance tests, revisit once there is less flakiness. 

---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants