-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
Properly fix CI #14
Comments
see issue #14 Change-Id: I5a4239747ccea577258c33a1174bbf6b81794e6f
ok well it's "fixed" (i.e. hacked around) on Travis now; won't know about GitHub Actions until those actually decide to run again, though... |
"fixed" now on GitHub Actions, too, but only by doing the same hacking-around-the-problem that I did on Travis, so I'm leaving this open until I come up with a proper fix... |
Current failures being ignored and/or hacked around are:
|
(note on the checklist: fixing the |
I think I've made some progress on the last 2 items on the checklist, and have checked them off for now... |
Update on the last one, about |
CI systems now have incompatible BFD headers installed on them, which get picked up during the build, and cause it to fail. We'll need to either find a way to ignore them, add compatibility with them, or just not install them in the first place?
The text was updated successfully, but these errors were encountered: