Skip to content

Conversation

@ddelnano
Copy link
Member

@ddelnano ddelnano commented Feb 13, 2025

Summary: Remove go 1.16 and 1.17. Add Go 1.22 and 1.23 into dynamic tracer test matrix

Once Go 1.16 and 1.17 are removed from the repo, we can pursue go dependency upgrades like #2115. I also added Go 1.22 and 1.23 (the latest versions) to dynamic tracer tests that ideally should cover multiple go versions.

Relevant Issues: N/A

Type of change: /kind cleanup

Test Plan: Existing tests

Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
@ddelnano ddelnano requested review from a team as code owners February 13, 2025 19:04
pl_cc_bpf_test(
name = "go_tls_trace_bpf_test",
timeout = "moderate",
timeout = "long",
Copy link
Member Author

@ddelnano ddelnano Feb 13, 2025

Choose a reason for hiding this comment

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

While running builds against #2115, I noticed that this test times out occasionally after merging #2116. This is because we added 2 go versions and only removed one (diff). Increasing the timeout should solve that problem.

Copy link
Member

Choose a reason for hiding this comment

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

Given that go1.24 was recently released and the golang policy is to old support upto two versions too old, I think. you can drop 1.18. I'd probably also suggest dropping 1.19 too.
IMO increasing the test matrix too much doesn't seem worth it.

Copy link
Member Author

Choose a reason for hiding this comment

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

Yea, I agree that we should deprecate those soon.

Omid had concerns that there might be older Go versions in use by end users despite Go's policy. I know of a few end users in this situation, so I might consider how to keep that test coverage without having our own dependencies tied to it.

If I decide to abandon keeping that coverage, at least its much easier to drop old support now with the dynamic logging stuff figured out. So a subsequent removal will be much easier.

@ddelnano
Copy link
Member Author

As for the @pixie-io/stirling review, Omid and I discussed this change and was aligned with removing these Go versions (#2116 (review)). So I'm going to move forward with this change.

@ddelnano ddelnano merged commit fb868c6 into pixie-io:main Feb 14, 2025
35 of 36 checks passed
@ddelnano ddelnano deleted the ddelnano/remove-go-1-16-1-17-and-more-version-coverage branch February 14, 2025 18:03
ddelnano added a commit to ddelnano/pixie that referenced this pull request Aug 6, 2025
…t matrix (pixie-io#2120)

Summary: Remove go 1.16 and 1.17. Add Go 1.22 and 1.23 into dynamic
tracer test matrix

Once Go 1.16 and 1.17 are removed from the repo, we can pursue go
dependency upgrades like pixie-io#2115. I also added Go 1.22 and 1.23 (the
latest versions) to dynamic tracer tests that ideally should cover
multiple go versions.

Relevant Issues: N/A

Type of change: /kind cleanup

Test Plan: Existing tests

---------

Signed-off-by: Dom Del Nano <ddelnano@gmail.com>
GitOrigin-RevId: fb868c6
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