Skip to content

Conversation

@Physic69
Copy link
Contributor

@Physic69 Physic69 commented Dec 28, 2025

@Physic69 Physic69 marked this pull request as ready for review December 28, 2025 20:57
@sheharyaar
Copy link
Member

Should the workflow also try to load the kernel module after building just for a better check ?

@carloslack
Copy link
Collaborator

Should the workflow also try to load the kernel module after building just for a better check ?

This would be bordering tests domain IMO

make -j$(nproc)
- name: Verify modules built
run: |
test -f lunatik.ko || test -f lib/lunatik.ko || (echo "Build failed" && exit 1)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Is it really needed to test for lib/lunatik.ko ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Nope, removed it

@Physic69
Copy link
Contributor Author

Physic69 commented Dec 29, 2025

Should the workflow also try to load the kernel module after building just for a better check ?

I feel like, they are not required. This catches most of missed cases (which is rare), XD..
Also added 5.x kernel version as well, as per issue stated 5.x onwards..

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

3 participants