-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Fix tests on Solaris #3864
Fix tests on Solaris #3864
Conversation
Could not assign reviewer from: |
06263a7
to
2cd820e
Compare
0283661
to
9dcb999
Compare
@tgross can you please help me with the buildbot failure? I have no idea what is wrong and how can I fixt it... |
@@ -63,3 +65,5 @@ pub const AT_386_FPINFO_NONE: u32 = 0; | |||
pub const AT_386_FPINFO_FXSAVE: u32 = 1; | |||
pub const AT_386_FPINFO_XSAVE: u32 = 2; | |||
pub const AT_386_FPINFO_XSAVE_AMD: u32 = 3; | |||
} | |||
} |
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.
Can you fix the indentation?
src/unix/solarish/x86_64.rs
Outdated
cfg_if! { | ||
if #[cfg(target_os = "solaris")] { | ||
use xrs_t; | ||
} | ||
} | ||
|
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.
Could you just use the full path to xrs_t
where it is used, rather than having a single cfg
ed import here? I'm not sure this is doing anything anyway.
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.
Well, not sure what is proper fix. Now I use:
cfg_if! {
if #[cfg(target_os = "solaris")] {
use unix::solarish::solaris;
}
}
..
pub uc_xrs: solaris::xrs_t,
I left a comment above but I think I'm not sure why FreeBSD failed but it looks spurious. Are tests currently failing on these platforms? It would be great to add @rustbot author based on the above comments. It would probably be good for @pfmooney to take another look at some point too. |
Out of all the similar GitHub usernames 😄 that really is an unbelievable coincidence
Thanks for taking a look :) I think it's a different struct though (mentioned above), this crate is unfortunately pretty macro-heavy so the error messages are a bit obscure. |
3da4674
to
0bbd84d
Compare
@tgross35 can you please have another look? Now it fails somewhere else and I don't know how to proceed again... |
Sorry, slipped under my radar. I think the error is just saying that Just comment |
☔ The latest upstream changes (presumably #3867) made this pull request unmergeable. Please resolve the merge conflicts. |
eab1ea0
to
3bbc12c
Compare
I think this looks okay but I am not able to test on the relevant systems. @pfmooney would you be able to double check this? |
☔ The latest upstream changes (presumably #3990) made this pull request unmergeable. Please resolve the merge conflicts. |
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.
Sorry I didn't merge this already, I think it should be good with a rebase.
3bbc12c
to
578b51a
Compare
Hm, not sure why freebsd is failing but it seems to be happening on everything |
Have no idea. Doesn't seem to be related. |
578b51a
to
ec3c338
Compare
It appears Solaris doesn't support epoll; only Illumos does. And as of rust-lang/libc#3864, the libc crate won't declare the epoll libc interface on Solaris. So disable epoll support on Solaris in rustix too.
* Disable epoll support on Solaris. It appears Solaris doesn't support epoll; only Illumos does. And as of rust-lang/libc#3864, the libc crate won't declare the epoll libc interface on Solaris. So disable epoll support on Solaris in rustix too. * Add epoll documentation links for illumos. * Add a documentation reference for ptsname for illumos. * Enable the epoll tests on illumos and redox. * Enable the openpty tests on illumos.
pub const POSIX_FADV_NORMAL: ::c_int = 0; | ||
pub const POSIX_FADV_RANDOM: ::c_int = 1; | ||
pub const POSIX_FADV_SEQUENTIAL: ::c_int = 2; | ||
pub const POSIX_FADV_WILLNEED: ::c_int = 3; | ||
pub const POSIX_FADV_DONTNEED: ::c_int = 4; | ||
pub const POSIX_FADV_NOREUSE: ::c_int = 5; |
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.
It looks like these, plus POLLRDHUP above, were accidentally deleted maybe in a bad merge. I'll roll a fix in for these in #3999.
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.
Sorry about that.
(backport <rust-lang#3864>) (cherry picked from commit ec3c338)
(backport <rust-lang#3864>) (cherry picked from commit ec3c338)
(backport <rust-lang#3864>) (cherry picked from commit ec3c338)
(backport <rust-lang#3864>) (cherry picked from commit ec3c338)
* Disable epoll support on Solaris. It appears Solaris doesn't support epoll; only Illumos does. And as of rust-lang/libc#3864, the libc crate won't declare the epoll libc interface on Solaris. So disable epoll support on Solaris in rustix too. * Add epoll documentation links for illumos. * Add a documentation reference for ptsname for illumos. * Enable the epoll tests on illumos and redox. * Enable the openpty tests on illumos.
* Disable epoll support on Solaris. It appears Solaris doesn't support epoll; only Illumos does. And as of rust-lang/libc#3864, the libc crate won't declare the epoll libc interface on Solaris. So disable epoll support on Solaris in rustix too. * Add epoll documentation links for illumos. * Add a documentation reference for ptsname for illumos. * Enable the epoll tests on illumos and redox. * Enable the openpty tests on illumos.
Tested (libc-test) on both Solaris and Illumos (with latest stable Omnios). All tests are passing.
Illumos changes can be checked against https://github.com/illumos/illumos-gate
Solaris changes can be checked only with installed Solaris CBE release (https://blogs.oracle.com/solaris/post/announcing-the-first-oracle-solaris-114-cbe) or using Solaris 11.4 machine at Cfarm (https://portal.cfarm.net/machines/list/).