Skip to content
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

unreliable test: resetClientComponentLatencyTime should reset state variables #6525

Open
Hweinstock opened this issue Feb 7, 2025 · 0 comments
Labels
bug We can reproduce the issue and confirmed it is a bug. codewhisperer partner-team Triggers issue routing to owner team tests-ci-cd

Comments

@Hweinstock
Copy link
Contributor

Hweinstock commented Feb 7, 2025

Test Details

  • Name of test: resetClientComponentLatencyTime should reset state variables
  • OS of failure: Mac
  • VSCode version of failure (minimum/insider/stable): insiders
  • Link to failing run: https://github.com/aws/aws-toolkit-vscode/actions/runs/13187725420/job/36813766367
  • Link to failing test:
    it('resetClientComponentLatencyTime should reset state variables', function () {
    session.invokeSuggestionStartTime = 100
    session.preprocessEndTime = 200
    session.sdkApiCallStartTime = 300
    session.fetchCredentialStartTime = 400
    session.firstSuggestionShowTime = 500
    sut.setSdkApiCallEndTime()
    sut.setAllPaginationEndTime()
    sut.setFirstResponseRequestId('aFakeRequestId')
    sut.resetClientComponentLatencyTime()
    assert.strictEqual(session.invokeSuggestionStartTime, 0)
    assert.strictEqual(session.preprocessEndTime, 0)
    assert.strictEqual(session.sdkApiCallStartTime, 0)
    assert.strictEqual(session.fetchCredentialStartTime, 0)
    assert.strictEqual(session.firstSuggestionShowTime, 0)
    assert.strictEqual(sut.sdkApiCallEndTime, 0)
    assert.strictEqual(sut.allPaginationEndTime, 0)
    assert.strictEqual(sut.firstResponseRequestId, '')
    })

Log of Test Failure

  1) telemetryHelper
       clientComponentLatency
         resetClientComponentLatencyTime should reset state variables:

      AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:

100 !== 0

      + expected - actual

      -100
      +0
@Hweinstock Hweinstock added tests-ci-cd partner-team Triggers issue routing to owner team codewhisperer labels Feb 7, 2025
@justinmk3 justinmk3 added partner-team Triggers issue routing to owner team bug We can reproduce the issue and confirmed it is a bug. and removed partner-team Triggers issue routing to owner team labels Feb 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug We can reproduce the issue and confirmed it is a bug. codewhisperer partner-team Triggers issue routing to owner team tests-ci-cd
Projects
None yet
Development

No branches or pull requests

2 participants