-
Notifications
You must be signed in to change notification settings - Fork 14
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
Tests don't seem to pass in 32-bit cygwin #80
Comments
Sorry, but I can't really support cygwin, I have no way to test there. PRs are welcome, though. |
Thanks for the reply @fingolfin. Beyond playing with AppVeyor (which is not practical) I think the Digraphs and Semigroups developers also don't have a way to test on cygwin (and no knowledge about how to develop for it, either). So perhaps we should either explicitly not support 32-bit cygwin too, or at least see about disabling the functionality in Digraphs that requires IO, when using 32-bit cygwin. (Everything seems to be fine with 64-bit for now). @james-d-mitchell |
Just to add that I will consider not supporting 32-bit cygwin by the IO package quite unfortunate - e.g. SCSCP package works under Windows because IO works. I will be happy to help with testing. |
@wilfwilson I tried to fix this in 2f86e9d but can't test it. Of course it'd be nice if somebody could set up AppVeyor for this repository, or try to make Travis Windows support working (which I never tried) |
Thanks @fingolfin, seems like a nice solution, it got rid of some of the failures in
UPDATE: The tests stopped running! Unsurprisingly (since you didn't touch them), the other test files that failed before still fail. |
I feel that 32-bit GAP (at least on Windows) maybe isn't long for this world, what with OSes dropping 32-bit support, so as far as I'm concerned this isn't a priority. |
Ah, my "fix" was a bit overeager. If you could try again... ? Well, what I don't quite get is why it would work in 64 bit Windows?! Because those changes I made are windows specific, not 32 bit windows specific. |
You'll be able to see the result here https://ci.appveyor.com/project/wilfwilson/digraphs/builds/25937245. I wasn't looking at the 64-bit bit stuff yesterday, that also seems to have failed. Let's see what happens now. |
|
Yes, forking is super slow, esp. on 64bit windows, because it has to be emulated in a complicated way. See also gap-system/gap#3513. It's one of the various reasons why I am not a big fan of the idea of "just making io a required package and let's call that our official interface to everything". I really hope that one day, we'll progress beyond POSIX based operating system to something more sane, and wouldn't want to tie GAP closely to that. |
I've been tentatively looking into why Digraphs doesn't work properly in cygwin, at least in 32-bit (seems to be okay in 64-bit now). I'm using AppVeyor to experiment with a 32-bit cygwin setup for GAP and Digraphs. A lot of the problems with Digraphs seem to arise when we want to do things with reading from/writing to files, so I thought I would check how the io package behaves on its own. You can see a build of what happens here and the full log is here: LOG: io-tests-in-cygwin-32bit.txt (the build dies after 1 hour without completing).
I'll copy the most relevant parts of the test failures. In
tst/bugfix.tst
, it seems likeIO_WriteLine
is always off by one; and intst/testgap.tst
it looks like something is really wrong; I don't understand it. Perhaps I'm doing something wrong with my setup, but I thought it was worth pointing this out anyway. This uses the GAPmaster
branch....and then lots more errors like this.
The text was updated successfully, but these errors were encountered: