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
Don't run pcre test suite on Cygwin #24756
Comments
Commit: |
Branch: u/embray/cygwin/pcre/check |
Author: Erik Bray |
New commits:
|
comment:2
Just a question: do you build R on Cygwin? I ask because R needs PCRE and a broken PCRE might yield a broken R. This is how we found out about the PCRE issues on Solaris. Or maybe only specific parts of PCRE are broken that are not used by R on Cygwin. |
comment:4
I don't know--there's like one test for PCRE that fails but I haven't looked into it. The full tests for R have never passed on Cygwin either; see #22866. But I'll run them again to see if any of them are "obviously" regexp related (I'd be surprised). I'd certainly like to address #22866 but it's low priority short of actual bug reports from users (and I don't think many people are installing Sage in order to use R on Windows...) |
comment:5
Replying to @embray:
On Solaris, even the build of R fails with the broken PCRE. So it seems that the Cygwin problem is not that severe. The only thing that I'm missing in this branch is a comment saying that we don't run the testsuite on Cygwin because it fails always in a way which doesn't seem to affect other packages. positive review if you add that. |
Reviewer: Jeroen Demeyer |
Branch pushed to git repo; I updated commit sha1. New commits:
|
comment:8
I think the additional comment is mostly superfluous since there's already a link to the original ticket, which could also be updated with a note about this. But I don't object. New commits:
|
Changed branch from u/embray/cygwin/pcre/check to |
See #24628 comment:10
Component: porting: Cygwin
Author: Erik Bray
Branch/Commit:
e4e85e8
Reviewer: Jeroen Demeyer
Issue created by migration from https://trac.sagemath.org/ticket/24756
The text was updated successfully, but these errors were encountered: