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

Fixing EKS and performanceTracking Integration Tests #370

Merged
merged 26 commits into from
Nov 2, 2023

Conversation

bhanuba
Copy link
Contributor

@bhanuba bhanuba commented Oct 30, 2023

Description of the issue

Found out that few integration tests were failing. These tests used to be running successfully previously.
-EKS Integration
-performanceTrackingtest

Description of changes

-Changed from heredoc syntax (<<POLICY) to jsonencode for fixing the EKS Integration test.
-The validators path was changed but not redirected in main.tf. Fixed by redirecting to the correct path.

License

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Tests

Fix for EKS integration test: https://github.com/aws/amazon-cloudwatch-agent/actions/runs/6673973151
Fix for performanceTrackingtest : https://github.com/aws/amazon-cloudwatch-agent/actions/runs/6648952606

Screenshot 2023-10-30 at 3 57 40 PM Screenshot 2023-10-30 at 4 01 00 PM

@bhanuba bhanuba requested a review from a team as a code owner October 30, 2023 17:33
@okankoAMZ
Copy link
Contributor

Nit: The title of the PR can be named better

@okankoAMZ
Copy link
Contributor

The performance test looks good but can you double check the dynamo database to see if it saved the test correctly (maybe a screenshot). Does this also work for traces?

@zhihonl
Copy link
Contributor

zhihonl commented Oct 30, 2023

Please rename the title of the PR. It is not descriptive enough. Also provide more details for Description of the issue and Description of changes sections. It does not tell the reviewers what the actual issue is and what you did to fix the issues.

@@ -80,8 +80,8 @@ var testTypeToTestConfig = map[string][]testConfig{
testDir: "./test/acceptance",
targets: map[string]map[string]struct{}{"os": {"ubuntu-20.04": {}}},
},
// skipping FIPS test as the test cannot be verified
// neither ssh nor SSM works after a reboot once FIPS is enabled
//skipping FIPS test as the test cannot be verified
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: likely your formatters but we don't need these changes

]
}
POLICY
assume_role_policy = jsonencode({
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Description of the PR isn't clear so can you explain what was the reasons for this change

"cp -r amazon-cloudwatch-agent-test/test/xray/resources /home/ec2-user/",
"export AWS_REGION=${var.region}",
"cd ./validator/validators",
"ls -lirt",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Do we need ls -lirt and pwd command here?

@@ -129,6 +129,7 @@ func (suite *MetricBenchmarkTestSuite) TestAllInSuite() {
case computetype.EKS:
log.Println("Environment compute type is EKS")
for _, testRunner := range getEksTestRunners(env) {
fmt.Println("testRunner---------", testRunner.Env)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Is this print line needed?

@bhanuba bhanuba changed the title Integration failure test Fixing Integration test failures Oct 30, 2023
@bhanuba bhanuba requested a review from zhihonl October 30, 2023 20:02
@bhanuba bhanuba assigned bhanuba and okankoAMZ and unassigned bhanuba Oct 30, 2023
@bhanuba bhanuba changed the title Fixing Integration test failures Fixing EKS and performanceTracking Integration Tests Oct 31, 2023
@bhanuba bhanuba merged commit cc44437 into aws:main Nov 2, 2023
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.

3 participants