Skip to content
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

cygwin: a cachefunc.py doctest hangs seemingly forever #9169

Closed
williamstein opened this issue Jun 7, 2010 · 10 comments
Closed

cygwin: a cachefunc.py doctest hangs seemingly forever #9169

williamstein opened this issue Jun 7, 2010 · 10 comments

Comments

@williamstein
Copy link
Contributor

On Cygwin, the following test hangs:


            sage: @cached_function
            ... def oddprime_factors(n):
            ...     l = [p for p,e in factor(n) if p != 2]
            ...     return len(l)
            sage: oddprime_factors.precompute(range(1,100), 4)

The above is very fast on any other platform.

This results in a doctest file failure:

sage -t  "devel/sage/sage/misc/cachefunc.py"                
*** *** Error: TIMED OUT! PROCESS KILLED! *** ***
*** *** Error: TIMED OUT! *** ***
 [361.6 s]

CC: @jpflori @dimpase @kcrisman

Component: porting: Cygwin

Reviewer: Jean-Pierre Flori

Issue created by migration from https://trac.sagemath.org/ticket/9169

@kcrisman
Copy link
Member

comment:1

FWIW, this file is now cachefunc.pyx.

@kcrisman
Copy link
Member

comment:2

This same test still fails, though for me it is because of forking errors and an inability to start Singular at times (presumably for that reason).

@jpflori
Copy link
Contributor

jpflori commented Jan 15, 2013

comment:4

On my install (64bits Windows 7 + sage 5.6.rc0) the test passes.

@kcrisman
Copy link
Member

comment:5

That's good to hear. I am frustrated by this forking business. A complete rebase just shifts the error to a different random file that won't be remapped. So I can never tell whether things are really a problem or not.

@dimpase
Copy link
Member

dimpase commented Jan 27, 2013

comment:6

Replying to @kcrisman:

That's good to hear. I am frustrated by this forking business. A complete rebase just shifts the error to a different random file that won't be remapped. So I can never tell whether things are really a problem or not.

Are you working on a 32-bit Windows? I've given up on attempting to use Cygwin on 32-bit systems.

Anyhow, this test works for me too. Let's close this one.

@kcrisman
Copy link
Member

comment:7

I'd feel best if we were able to try on 32-bit XP... though I recognize this may be impossible unless my box stops acting up.

@jpflori
Copy link
Contributor

jpflori commented Jan 30, 2013

comment:8

When the status on my 64 bits Windows 7 looks good enough (which looks close), I'll dig up an old 32 bits install and give it a try.

@jpflori
Copy link
Contributor

jpflori commented Feb 8, 2013

comment:9

This is ok on 32 bits Windows 7, so I'll close it.

@jpflori jpflori removed this from the sage-5.7 milestone Feb 8, 2013
@jdemeyer
Copy link
Contributor

jdemeyer commented Feb 8, 2013

Reviewer: Jean-Pierre Flori

@fchapoton

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants