[sage-devel] git trac fails to checkout a remote branch

2018-11-29 Thread Emmanuel Charpentier
Trying to test Trac#26791 : charpent@zen-book-flip:/usr/local/sage-8$ git trac checkout 26791 Loading ticket #26791... Checking out Trac #26791 remote branch u/gh-timokau/rpy2-build-typo -> local branch t/26791/rpy2-build-typo... Traceback (most recent ca

Re: [sage-devel] Re: git trac fails to checkout a remote branch

2018-11-29 Thread Dima Pasechnik
On Thu, Nov 29, 2018 at 10:43 PM Emmanuel Charpentier wrote: > > The problem might be on trac : git branch --remote | grep 26791 diesn't > return anything... Why? git repo itself does not know anything about trac tickets. It's git trac extension that tries to match tickets to branches somehow.

[sage-devel] Re: git trac fails to checkout a remote branch

2018-11-29 Thread Emmanuel Charpentier
The problem might be on trac : git branch --remote | grep 26791 diesn't return anything... Le jeudi 29 novembre 2018 23:27:04 UTC+1, Emmanuel Charpentier a écrit : > > Trying to test Trac#26791 : > > charpent@zen-book-flip:/usr/local/sage-8$ git trac check

Re: [sage-devel] git trac fails to checkout a remote branch

2018-11-29 Thread Dima Pasechnik
Use plain git. Suppose you're on branch called foo git fetch trac u/gh-timokau/rpy2-build-typo git checkout -b rpy2-build-typo FETCH_HEAD at this point you have created a local branch called rpy2-build-typo which is more or less what trac extension is supposed to do. Test is, and then do git che

Re: [sage-devel] Re: doctest quality and patchbots

2018-11-29 Thread E. Madison Bray
On Thu, Nov 29, 2018 at 12:19 PM Jeroen Demeyer wrote: > > On 2018-11-29 10:38, E. Madison Bray wrote: > > But I sometimes get failures in tests depending on which order the > > *files* were run in. That's what I'm talking about. > > But that's really unusual (and unrelated to --randorder). I gu

Re: [sage-devel] Re: doctest quality and patchbots

2018-11-29 Thread Jeroen Demeyer
On 2018-11-29 10:38, E. Madison Bray wrote: But I sometimes get failures in tests depending on which order the *files* were run in. That's what I'm talking about. But that's really unusual (and unrelated to --randorder). Do you have *any* concrete example of such a failure? -- You received

Re: [sage-devel] Re: doctest quality and patchbots

2018-11-29 Thread 'Martin R' via sage-devel
Actually, I find it more problematic that sage -t --long may pass (which is what the patchbots check), but sage -t fails (which is what most users running the tests probably see) Martin Am Donnerstag, 29. November 2018 10:38:54 UTC+1 schrieb E. Madison Bray: > > On Wed, Nov 28, 2018 at 12:25 PM

Re: [sage-devel] Re: doctest quality and patchbots

2018-11-29 Thread E. Madison Bray
On Wed, Nov 28, 2018 at 12:25 PM Jeroen Demeyer wrote: > > On 2018-11-28 09:17, E. Madison Bray wrote: > > +1 There are several tests which, when run in an unusual order, result > > in random failures. This is obviously a failure of test isolation if > > nothing else, and such cases *should* be r