Skip to content

Conversation

@StefanKurek
Copy link
Collaborator

This should be identical with this PR #542, but instead of having a separate app called sqlserver, this adds new metrics to the existing mssql application with a version configuration parameter to differentiate between old and new.

@StefanKurek StefanKurek added the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 25, 2022
@kokoro-team kokoro-team removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 25, 2022
@StefanKurek StefanKurek added the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 25, 2022
@kokoro-team kokoro-team removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 25, 2022
@StefanKurek StefanKurek added the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 26, 2022
@kokoro-team kokoro-team removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 26, 2022
@StefanKurek StefanKurek added the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 26, 2022
@kokoro-team kokoro-team removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 26, 2022
@StefanKurek StefanKurek added the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 26, 2022
@kokoro-team kokoro-team removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 26, 2022
@StefanKurek StefanKurek added the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 26, 2022
@kokoro-team kokoro-team removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 26, 2022
@StefanKurek StefanKurek added the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 26, 2022
@kokoro-team kokoro-team removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 26, 2022
@StefanKurek StefanKurek added the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 26, 2022
@kokoro-team kokoro-team removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 26, 2022
@StefanKurek StefanKurek added the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 26, 2022
@kokoro-team kokoro-team removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 26, 2022
@StefanKurek
Copy link
Collaborator Author

All tests pass:
image

@StefanKurek StefanKurek added the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 27, 2022
@kokoro-team kokoro-team removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Apr 27, 2022
@schmikei schmikei added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 21, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 21, 2022
@schmikei schmikei added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 21, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 21, 2022
@ridwanmsharif ridwanmsharif added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 22, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 22, 2022
@ridwanmsharif ridwanmsharif added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 22, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 22, 2022
@ridwanmsharif ridwanmsharif added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 23, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 23, 2022
@qingling128
Copy link
Contributor

The failed Windows build is a known issue (fixed separately already).

Once rebased, this can be merged.

@schmikei schmikei added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 24, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 24, 2022
@schmikei schmikei added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 24, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 24, 2022
@schmikei schmikei added the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 24, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Jun 24, 2022
@schmikei
Copy link
Collaborator

Third party test passed, Ops Agent Upgrade failed because of

=== CONT  TestUpgradeOpsAgent/windows-2019
    ops_agent_test.go:1693: WaitForMetric(metric=agent.googleapis.com/cpu/utilization, extraFilters=[]) failed: exhausted retries
--- FAIL: TestUpgradeOpsAgent (0.00s)
    --- PASS: TestUpgradeOpsAgent/windows-2012-r2 (750.55s)
    --- FAIL: TestUpgradeOpsAgent/windows-2019 (1270.42s)

@qingling128 @ridwanmsharif I don't believe this is a blocker, but do you have any thoughts?

@qingling128
Copy link
Contributor

Third party test passed, Ops Agent Upgrade failed because of

=== CONT  TestUpgradeOpsAgent/windows-2019
    ops_agent_test.go:1693: WaitForMetric(metric=agent.googleapis.com/cpu/utilization, extraFilters=[]) failed: exhausted retries
--- FAIL: TestUpgradeOpsAgent (0.00s)
    --- PASS: TestUpgradeOpsAgent/windows-2012-r2 (750.55s)
    --- FAIL: TestUpgradeOpsAgent/windows-2019 (1270.42s)

@qingling128 @ridwanmsharif I don't believe this is a blocker, but do you have any thoughts?

Forgot to mention: The TestUpgradeOpsAgent was a known issue that was fixed separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants