[sage-devel] patchbot false negatives

Please be aware that most tickets reported as Failed by patchbots are false positives: - ApplyFailed: patchbot tests tickets with non-closed dependencies - BuildFailed: 1. the setuptools issue (#16300), 2. patchbot failing to make doc-clean before runs - PluginFailed: at least some coverage

[sage-devel] Re: sage--gram-schmidt

On Friday, May 9, 2014 12:35:30 PM UTC-7, jason wrote: Mike Hansen and I had a conversation about this at one point, and I > think we concluded that instead of looking at the base ring in the case > of SR, we should instead look at the specific matrix and decide if it > was "exact" or an approx

Re: [sage-devel] How to update trac branch after rebasing?

On Friday, 9 May 2014 17:49:58 UTC-6, Andrey Novoseltsev wrote: > > On Friday, 9 May 2014 17:37:02 UTC-6, Michael Orlitzky wrote: >> >> On 05/09/2014 07:10 PM, Andrey Novoseltsev wrote: >> > Hello, >> > >> > I've rebased a branch on top of 6.2, which went fine (branch just adds >> a >> > fil

Re: [sage-devel] How to update trac branch after rebasing?

On Friday, 9 May 2014 17:37:02 UTC-6, Michael Orlitzky wrote: > > On 05/09/2014 07:10 PM, Andrey Novoseltsev wrote: > > Hello, > > > > I've rebased a branch on top of 6.2, which went fine (branch just adds a > > file), but then I couldn't push it via git push ... or git trac push > > with git

Re: [sage-devel] How to update trac branch after rebasing?

On 05/09/2014 07:10 PM, Andrey Novoseltsev wrote: > Hello, > > I've rebased a branch on top of 6.2, which went fine (branch just adds a > file), but then I couldn't push it via git push ... or git trac push > with git insisting that I have to pull. While that worked, it > automatically created an

[sage-devel] How to update trac branch after rebasing?

Hello, I've rebased a branch on top of 6.2, which went fine (branch just adds a file), but then I couldn't push it via git push ... or git trac push with git insisting that I have to pull. While that worked, it automatically created an empty (=no files have changed) merge commit listing all my

[sage-devel] Re: MacOS X binary dists and newer versions of Xcode

On 2014-05-09, leif wrote: > Volker Braun wrote: >> The OSX 10.9 buildbot should have the latest xcode, or at least at most >> 1-2 months old. Definitely >= 5.x. > > So such issues will vanish with the Sage 6.2+ MacOS X binaries (provided > MacOS X users with recent versions of Xcode use recent [

[sage-devel] Re: Docs not building on 6.2

FTR, that is https://groups.google.com/forum/#!topic/sage-devel/QP34tOWDw-0 and it's on my Ubuntu 12.04 LTS (quad core Intel) laptop. On Friday, May 9, 2014 12:37:30 PM UTC-7, KnS wrote: > > Hi group: > > I have been trying to build the doc for SAGE 6.2 on a Mac OSX 10.9.2. The > doc build alway

[sage-devel] Docs not building on 6.2

Hi group: I have been trying to build the doc for SAGE 6.2 on a Mac OSX 10.9.2. The doc build always stops at: [tensor ] writing output... [ 75%] sage/tensor/differential_form_element [tensor ] writing output... [100%] sage/tensor/differential_forms [tensor ] dumping object inventory... d

[sage-devel] Re: sage--gram-schmidt

(CCd to sage-devel) On 5/9/14, 13:32, David Guichard wrote: Is there some deep reason I'm not seeing that G-S doesn't work for SR? It seems like everything should be fine. Is the problem in detecting dependent sets over SR? This keeps me from being able to do simple examples for a linear algebra

[sage-devel] Re: tests related to papers and books

Anne Schilling wrote: On 5/9/14 4:40 AM, leif wrote: Anne Schilling wrote: We actually added tests for our k-Schur function book. But a lot of time, when syntax in Sage changes, these tests just get replaced by others without checking with the authors of the book/paper. git log src/sage/tests

Re: [sage-devel] Re: tests related to papers and books

On 5/9/14 4:40 AM, leif wrote: > Anne Schilling wrote: >> We actually added tests for our k-Schur function book. But a lot of >> time, when syntax in >> Sage changes, these tests just get replaced by others without checking >> with the authors >> of the book/paper. > > git log src/sage/tests/book_

[sage-devel] Re: Testing the pickle jar more thoroughly (many objects in it are broken after unpickling)

Hi Volker, > On Friday, May 9, 2014 5:57:09 PM UTC+2, Peter Bruin wrote: >> >> I just opened a ticket , but I >> thought I'd also send a message to sage-devel to advertise the fact that we >> can't rely on that doctest to ensure backwards compatibility of

[sage-devel] Re: MacOS X binary dists and newer versions of Xcode

Volker Braun wrote: The OSX 10.9 buildbot should have the latest xcode, or at least at most 1-2 months old. Definitely >= 5.x. So such issues will vanish with the Sage 6.2+ MacOS X binaries (provided MacOS X users with recent versions of Xcode use recent [pre-built] versions of Sage as well..

[sage-devel] Re: Testing the pickle jar more thoroughly (many objects in it are broken after unpickling)

On Friday, May 9, 2014 5:57:09 PM UTC+2, Peter Bruin wrote: > > I just opened a ticket , but I > thought I'd also send a message to sage-devel to advertise the fact that we > can't rely on that doctest to ensure backwards compatibility of our > unpickling p

[sage-devel] Re: MacOS X binary dists and newer versions of Xcode

The OSX 10.9 buildbot should have the latest xcode, or at least at most 1-2 months old. Definitely >= 5.x. On Wednesday, May 7, 2014 6:36:43 PM UTC+2, leif wrote: > > Should we put up signs telling people not to use the MacOS X pre-built > binaries (or the MacOS X "app") with Xcode versions >=

[sage-devel] Re: RAM to build Sage

On 2014-05-09, Volker Braun wrote: > We do have a arm machine in Oxford with more than enough ram (afair 4GB). > Dima did some work on finishing the arm port. In any case, its not a ram > issue. indeed. Please review :) http://trac.sagemath.org/ticket/15921 > > > On Friday, May 9, 2014 1:41:44

[sage-devel] Testing the pickle jar more thoroughly (many objects in it are broken after unpickling)

Hello sage-dev, While working on something else, I found out that although there is a doctest that unpickles all objects in the pickle jar, it does not do any kind of sanity check on the resulting objects. This means that unpickling many of these objects has become completely broken over time.

[sage-devel] Re: MacOS X binary dists and newer versions of Xcode

leif wrote: Should we put up signs telling people not to use the MacOS X pre-built binaries (or the MacOS X "app") with Xcode versions >= 5.x? Apparently the deployment targets currently compiled into Sage's GCC (on the MacOS X buildslave[s]) don't work with more recent versions of Xcode (5.x? o

[sage-devel] Re: tests related to papers and books

Jeroen Demeyer wrote: On 2014-05-09 14:08, David Loeffler wrote: It's happened a few times that people have put tests in the sage/tests directory which explicitly require that certain inputs return NotImplementedError, or something similar. Surely we shouldn't have to go through the rigmarole of

[sage-devel] Re: tests related to papers and books

David Loeffler wrote: It's happened a few times that people have put tests in the sage/tests directory which explicitly require that certain inputs return NotImplementedError, or something similar. Surely we shouldn't have to go through the rigmarole of contacting the original author and waiting

Re: [sage-devel] Re: Is there a way to make two_squares faster ? (it uses the interface with GAP)

On 8 May 2014 20:39, leif wrote: > John Cremona wrote: > >> On 8 May 2014 09:30, Jeroen Demeyer > > wrote: >> >> If I'm not mistaken, the problem of writing N as a^2 + b^2 is >> equivalent to finding a square root of -1 modulo N. I know that >> computing

[sage-devel] Re: interact.sagemath.org

On 5/7/14, 0:41, Ivan Andrus wrote: On May 6, 2014, at 11:47 AM, Jason Grout wrote: On 5/5/14, 14:20, Daniel Bell wrote: Hi I am one of the students who was selected for working with Sage for Google Summer of Code. I will be working on the iOS app. One of the features I want to implement i

Re: [sage-devel] Re: tests related to papers and books

On 2014-05-09 14:08, David Loeffler wrote: It's happened a few times that people have put tests in the sage/tests directory which explicitly require that certain inputs return NotImplementedError, or something similar. Surely we shouldn't have to go through the rigmarole of contacting the origina

Re: [sage-devel] Re: RAM to build Sage

On 2014-05-09 14:08, leif wrote: And probably some build- or patchbots should run the tests with 'ulimit -v $SAGE_DOCTEST_MEMORY_CUTOFF' by default. Totally +1. I always did that with a limit of 2.5GB. -- You received this message because you are subscribed to the Google Groups "sage-devel" g

[sage-devel] Re: RAM to build Sage

Jeroen Demeyer wrote: On 2014-05-09 10:55, Julien Puydt wrote: But personally, I don't consider RAM usage by doctests an issue. Perhaps because you don't use old or limited computers? No, because I think that doctest coverage is more important than memory usage of doctests. It is perfectly po

Re: [sage-devel] Re: tests related to papers and books

It's happened a few times that people have put tests in the sage/tests directory which explicitly require that certain inputs return NotImplementedError, or something similar. Surely we shouldn't have to go through the rigmarole of contacting the original author and waiting a year in order to add a

[sage-devel] Re: tests related to papers and books

On Friday, May 9, 2014 1:40:51 PM UTC+2, leif wrote: > > Probably each relevant file should contain a CAPSLOCK header with > information on how to contact the author(s) etc. > DEAR SIR WE HAVE RECENTLY COME INTO POSSESSION OF THIS EXTREMELY VALUABLE DOCTEST FOR WHICH WE WOULD LIKE TO ENLIST YOU

Re: [sage-devel] RAM to build Sage

We do have a arm machine in Oxford with more than enough ram (afair 4GB). Dima did some work on finishing the arm port. In any case, its not a ram issue. On Friday, May 9, 2014 1:41:44 PM UTC+2, mmarco wrote: > > Well, testing, for instance, if everything runs in an ARM machine can be > painf

Re: [sage-devel] RAM to build Sage

On 2014-05-09 13:41, mmarco wrote: And if we want to deliver ARM binaries, we need to test everything there. This does not have to be the case. In fact, at some point we had Solaris and OS X PPC binaries even though not everything was working 100% on those platforms. If there are a few files

Re: [sage-devel] RAM to build Sage

Well, testing, for instance, if everything runs in an ARM machine can be painful. And if we want to deliver ARM binaries, we need to test everything there. El viernes, 9 de mayo de 2014 13:04:20 UTC+2, Jeroen Demeyer escribió: > > On 2014-05-09 10:55, Julien Puydt wrote: > >> But personally, I

[sage-devel] Re: tests related to papers and books

Anne Schilling wrote: We actually added tests for our k-Schur function book. But a lot of time, when syntax in Sage changes, these tests just get replaced by others without checking with the authors of the book/paper. git log src/sage/tests/book_schilling_zabrocki_kschur_primer.py | grep Autho

Re: [sage-devel] RAM to build Sage

On 2014-05-09 10:55, Julien Puydt wrote: But personally, I don't consider RAM usage by doctests an issue. Perhaps because you don't use old or limited computers? No, because I think that doctest coverage is more important than memory usage of doctests. It is perfectly possible to *use* Sage on

Re: [sage-devel] RAM to build Sage

Hi, Le 06/05/2014 19:39, Jeroen Demeyer a écrit : On 2014-05-06 16:53, John Cremona wrote: In practice, it may be hard to gather the informatino on how much RAM tests take You could run them under "ulimit -v" and see when they start to fail. But personally, I don't consider RAM usage by docte

Re: [sage-devel] TOPCOM on OSX 10.9.2

On 9/05/2014, at 2005, Oskar Till wrote: > > Maybe I should try and build from source then. How do I uninstall the version > I have now, is it enough to just drag the Applications/sage folder into the > trash? Yes. -- You received this message because you are subscribed to the Google Groups

[sage-devel] Re: TOPCOM on OSX 10.9.2

Maybe I should try and build from source then. How do I uninstall the version I have now, is it enough to just drag the Applications/sage folder into the trash? /Oskar On Wednesday, May 7, 2014 11:24:01 AM UTC+2, Oskar Till wrote: > > Just as I got my sage to work with topcom on my old laptop,