-
Notifications
You must be signed in to change notification settings - Fork 68
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
issue1538 durack1 update Cython 0.22.1 to 0.23.3 #1540
issue1538 durack1 update Cython 0.22.1 to 0.23.3 #1540
Conversation
@doutriaux1 on
|
@doutriaux1 looks to be a similar missing test image issue on garant along with a behavior change with overplotting hatching or similar |
Looks like |
@doutriaux1 is |
on and off, playing with it. I will resubmit yours. But only the RHs are up at the moment, Mac decided to not let me in... |
@doutriaux1 the |
@doutriaux1 |
@doutriaux1 looks like |
@durack1 I restarted Xfvb, I 'm afraid some bad PR went in.... |
and no they're not choking I just went to look, just seem to be taking forever... |
@aashish24 I just double check a bunch of tests are now failing on RH6... Checking Ubuntu as well... These used to work, I'm going to go back slowly and see last commit that worked... I think some PR went in too hastily. |
According to cdash 77c1c61bece had only 1 failure on ocean only. The only commits merged after that are the following:
|
@jbeezley yes i went way way back and it still shows up the same errors whereas crunchy is stable. So something happened to oceanonly. That's good in the sense that it means our code is not broken! |
@doutriaux1 and using my interactive session (and a fresh build from the
|
@doutriaux1 and what has been upgraded since 20th August 2015 (and some other selected updates dating back to 27th July 2015 - the redhat 6.7 update):
|
@durack1 I'm at a loss here. crunchy still works and it seems to have been upgraded as well... Trying with MESA now, if that still fails let's go for a reboot... |
@doutriaux1 yep I think that sounds like a good idea.. I'll poll other users in the interim.. |
@doutriaux1 |
@durack1 please stop pushing PR for now, we have do let the bots deal with the 2.4 branches first. Thanks |
@doutriaux1 I'm not touching this.. Just hoping the buildbots can run an accurate test against the PR however.. |
@doutriaux1 Assuming you haven't changed the tangelo proxy. It builds on push not on PR, so any push to this repository that updates the SHA of any branch will trigger it. |
yes so that's why I was asking @durack1 to try to refrain to trigger any rebuild until after the release because we push more frequently when near the release and we need to see the results as fast as possible. |
5f17a01
to
601e6ca
Compare
601e6ca
to
ff979a9
Compare
@doutriaux1 looks like the same The segfault in |
c542046
to
ceaffae
Compare
@doutriaux1 @chaosphere2112 at least travis doesn't discriminate my PR queue priority.. Look at those shiny green ticks.. |
@durack1 All part of @doutriaux1's cunning plan to slowly drive you mad 😈 |
why slowly? Oh yes it's more fun to watch the process |
|
@doutriaux1 @chaosphere2112 have the lower class PR citizens queues started running yet? |
….22.1To0.23.1 issue1538 durack1 update Cython 0.22.1 to 0.23.3
@durack1 happy now? 😉 |
@doutriaux1 well at least that's one less PR to block up the |
Fix #1538 - Update Cython 0.22.1 to 0.23.1