On Tuesday, May 7, 2013 7:09:18 PM UTC-7, kcrisman wrote: > > > > On Tuesday, May 7, 2013 9:49:13 PM UTC-4, Kwankyu Lee wrote: >> >> >> I think it is intermittent in the sense that on computers with the >>> problem, it fails consistently when building Sage in parallel; the fix is >>> to then quickly do that one package in series, then remain doing things in >>> parallel (see the ticket or other discussions for details). Are you saying >>> that even when doing ./sage -i zn_poly (so, one thread) it fails? >>> >> >> I just did "./sage -i zn_poly" three times in a row. They all failed. >> > > And there is nothing else particularly heavy running on the computer? > (This appears to be the root cause of the failure, which parallel building > happens to expose since then there is heavy stuff running by definition.) >
For example, can you stop everything on the computer and remote log in to it from another machine, so you're hardly running anything on it? If not, quit all possible applications and try building again. By the way, how much RAM does this machine have (this may not be relevant, but just in case)? -- John -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at http://groups.google.com/group/sage-devel?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
