-
Notifications
You must be signed in to change notification settings - Fork 74
Introduce FreeBSD CI #142
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
base: master
Are you sure you want to change the base?
Introduce FreeBSD CI #142
Conversation
|
89a29b5
to
ddf41bf
Compare
Can we get this in? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but I am not a maintainer. @langou is the one who usually merged my PRs, but I do not want to over-burden any single maintainer. If it's possible to know something about the communication channels and/or schedules of people, it will help us avoid pings.
@arrowd could you resolve the open comments (only authors and collaborators can do that). It would also be nice if the steps can be separated either as different GH actions steps or with echo "::group::"
1, and if the ctests could be run even if they are failing. These can be addressed in a separate PR though.
Footnotes
c55d4b0
to
f41a0c6
Compare
Tests are not run at the moment because they cause the job to hang (or are they take so much time?)
This will be investigated later.