Originally from D128084 with adjustments made during iteration on bringing up CI.
Details
- Reviewers
philnik Mordante - Group Reviewers
Restricted Project Restricted Project - Commits
- rG7ec6c629052c: [libc++] Add FreeBSD XFAILs in preparation for CI
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
LGTM if the runner in D128084 is happy.
It's close, I also have four tests that had inconsistent or timing-out results that I've just disabled for now to make progress, those will need to be sorted out before the runner can be enabled.
IMO we should fix these issues, but I rather have a CI that tests most of libc++ instead of all of FreeBSD.
Note I really would like to help with the locale stuff, but that requires remote access to a FreeBSD box.
libcxx/test/std/time/time.cal/time.cal.month/time.cal.month.nonmembers/ostream.pass.cpp | ||
---|---|---|
9 | Is there a way to get remote access to a FreeBSD machine? I wouldn't mind to fix these, and upcoming time locale issues, when I have access. |
IMO we should fix these issues, but I rather have a CI that tests most of libc++ instead of all of FreeBSD.
Yes, absolutely. My first priority is to have FreeBSD CI running so that we can prevent regressions. From there we can iterate on fixing these XFAILs.
Is there a way to get remote access to a FreeBSD machine? I wouldn't mind to fix these, and upcoming time locale issues, when I have access.
Sure, I can arrange that. I can give you an account set up with your existing GitHub ssh keys if you like, or send me a public ssh key that you'd like to use.
Is there a way to get remote access to a FreeBSD machine? I wouldn't mind to fix these, and upcoming time locale issues, when I have access.