feat: introduce a new workflow to verify build script on multi platforms

[spencercjh]

CLOSE #176

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
kyanos	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 20, 2024 2:04pm

[hengyoush]

Thanks for your contribution!

Here are some suggestions I have:

1. I think we can add a workflow specifically for testing whether the build can be done on multiple platforms, while the current test.yml is mainly used for e2e tests and it build kyanos on Ubuntu 22.04 only .
2. Initially, we can add tests for Ubuntu only. The test environment should include multiple versions of Ubuntu and both ARM/AMD architectures (use matrix). The main focus is to test whether init_env.sh can complete the build. Other platforms like CentOS, Fedora, etc., can be added later.
3. I think we can skip adding go test for now because many tests are currently broken and need to be fixed, which will take some time.

What do you think?

[spencercjh]

Thanks for your contribution!

Here are some suggestions I have:

1. I think we can add a workflow specifically for testing whether the build can be done on multiple platforms, while the current test.yml is mainly used for e2e tests and it build kyanos on Ubuntu 22.04 only .
2. Initially, we can add tests for Ubuntu only. The test environment should include multiple versions of Ubuntu and both ARM/AMD architectures. The main focus is to test whether init_env.sh can complete the build. Other platforms like CentOS, Fedora, etc., can be added later.
3. I think we can skip adding go test for now because many tests are currently broken and need to be fixed, which will take some time.

What do you think?

You're right.

Also I have to take some time to get a working Ubuntu workspace.😅

[spencercjh]

Thanks for your contribution!

Here are some suggestions I have:

1. I think we can add a workflow specifically for testing whether the build can be done on multiple platforms, while the current test.yml is mainly used for e2e tests and it build kyanos on Ubuntu 22.04 only .
2. Initially, we can add tests for Ubuntu only. The test environment should include multiple versions of Ubuntu and both ARM/AMD architectures (use matrix). The main focus is to test whether init_env.sh can complete the build. Other platforms like CentOS, Fedora, etc., can be added later.
3. I think we can skip adding go test for now because many tests are currently broken and need to be fixed, which will take some time.

What do you think?

I attempted to implement your suggestions, but I found that the free version on GitHub (as opposed to the Team and Enterprise versions) does not support ARM64 runners: https://docs.github.com/en/actions/using-github-hosted-runners/using-larger-runners/about-larger-runners

[spencercjh]

kyanos/init_env.sh

Lines 11 to 30 in 4be0227

	if [ ${release_num} == "20.10" ]; then
	CLANG_NUM=-10
	elif [ ${release_num} == "21.04" ]; then
	CLANG_NUM=-11
	elif [ ${release_num} == "21.10" ]; then
	CLANG_NUM=-12
	elif [ ${release_num} == "22.04" ]; then
	CLANG_NUM=-12
	elif [ ${release_num} == "22.10" ]; then
	CLANG_NUM=-12
	elif [ ${release_num} == "23.04" ];then
	CLANG_NUM=-15
	elif [ ${release_num} == "23.10" ];then
	CLANG_NUM=-15
	elif [ ${release_num} == "24.04" ];then
	CLANG_NUM=-18
	else
	echo "used default CLANG Version"
	CLANG_NUM=
	fi

The Ubuntu version here doesn't exactly match the Ubuntu version in the runner provided by GitHub. You need to open another PR to change it. I'm sorry that I don't really understand the constraints of these distro and CLANG versions. That's why the test for ubuntu-20.04 fails now.

[spencercjh]

To minimize the size of this PR, the workflow that governs the formatting and style of the code should be placed in a separate workflow yaml file.

[hengyoush]

Just add one check:

if [ ${release_num} == "20.04" ]; then
  CLANG_NUM=-10

I tested it on Ubuntu 20.04 and it works fine. @spencercjh