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

WIP: update GitHub workflow to use cyd #5204

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

rjbs
Copy link
Collaborator

@rjbs rjbs commented Jan 9, 2025

No description provided.

Sphinx warns if the width of the underline falls short of the header text!
@rjbs rjbs force-pushed the test-with-cyd branch 9 times, most recently from 302f5fc to d5fc15a Compare January 9, 2025 02:14
Comment on lines 63 to 54
working-directory: cassandane
run: setpriv --reuid=cyrus --regid=mail --clear-groups --inh-caps='-chown,-dac_override,-dac_read_search,-fowner,-fsetid,-kill,-setgid,-setuid,-setpcap,-linux_immutable,-net_bind_service,-net_broadcast,-net_admin,-net_raw,-ipc_lock,-ipc_owner,-sys_module,-sys_rawio,-sys_chroot,-sys_ptrace,-sys_pacct,-sys_admin,-sys_boot,-sys_nice,-sys_resource,-sys_time,-sys_tty_config,-mknod,-lease,-audit_write,-audit_control,-setfcap,-mac_override,-mac_admin,-syslog,-wake_alarm,-block_suspend,-audit_read,-cap_38,-cap_39,-cap_40' ./testrunner.pl --slow -f prettier -j 8 !Test::Core
run: cyd test
Copy link
Contributor

Choose a reason for hiding this comment

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

CI for this one is failing on the Test::Core tests, which we used to skip in CI (!Test::Core at the end of the run command), but with this change I guess they're no longer skipped.

These tests prove that Cassandane can detect when Cyrus crashed -- which means, if these tests succeed, and everything else also succeeded, then nothing crashed. When these tests fail (or are skipped), that means Cassandane can't detect Cyrus crashes, and tests that result in Cyrus crashes might accidentally report success if the test itself didn't notice the crash.

So it would be good to not skip them, but I never figured out how to get them working in CI. On a normal system, you need to configure a few things to get crashed processes to dump core. On CI, between all the layers of docker and stuff, I don't know what's configured or where to change it.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Interesting. They must(?) be passing in Docker for cyd/dar to work, so it'll be something more constrained on GitHub Actions.

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