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

Transition to GitHub Actions for CI. #1568

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

Conversation

shaleh
Copy link
Collaborator

@shaleh shaleh commented Feb 27, 2020

Add the following as CI running with GitHub Actions.

rustfmt is run first essentially as a quick smoke test. If the PR is poorly formatted we can stop quickly.

clippy is then run. This acts as a code sanity and compilation check for the actual tests will be run.

Finally, each platform runs their tests. This only happens if both rustfmt and clippy succeed.

@db48x
Copy link
Collaborator

db48x commented Mar 16, 2020

Looks like the Clippy test is running autogen, configure, etc first. Is that necessary, or can it be skipped?

@shaleh
Copy link
Collaborator Author

shaleh commented Mar 16, 2020

Clippy has to be able to build the project. Which requires make-docfile, globals.h, etc etc.

@agraven
Copy link
Collaborator

agraven commented Aug 7, 2020

Closing and re-opening to regenerate expired build logs

@agraven agraven closed this Aug 7, 2020
@agraven agraven reopened this Aug 7, 2020
@agraven
Copy link
Collaborator

agraven commented Aug 7, 2020

The linux no gui builds fails with a few errors like

frame.c:79:1: error: no previous prototype for ‘fget_internal_border_width’ [-Werror=missing-prototypes]
 fget_internal_border_width(const struct frame *f)

which I guess means frame.h isn't being loaded properly, which is strange, because none of the other build have this issue. I'll look into it some more

@db48x
Copy link
Collaborator

db48x commented Aug 7, 2020

I see that fget_internal_border_width is inside an #ifdef HAVE_WINDOW_SYSTEM; perhaps the call to it should be similarly ifdef'd?

@agraven
Copy link
Collaborator

agraven commented Aug 7, 2020

It's specifically the set of functions from line 1555 to 1558. Strange. I'm gonna mess around on my local system to see if I can reproduce and fix it.

@agraven
Copy link
Collaborator

agraven commented Aug 7, 2020

Part of the issue seems to be that -Wmissing-prototype is elevated from warning to error in CI, but not otherwise.

@db48x
Copy link
Collaborator

db48x commented Aug 7, 2020

I think it's fine for it to be an error, as long as it is consistent between normal and CI builds. To fix the error, I'm pretty sure we can just put an ifdef around the definitions of these functions, just like there's one around the declarations.

@agraven
Copy link
Collaborator

agraven commented Aug 7, 2020

That's what I ended up doing and it worked. Now I just can't figure out why the mac build is failing. I've looked at the build log but don't see where the error is

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

Successfully merging this pull request may close these issues.

None yet

3 participants