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

Issue1126 durack1 matplotlib1.4.3 update #1329

Merged
merged 4 commits into from Jun 1, 2015

Conversation

@durack1
Copy link
Member

@durack1 durack1 commented May 19, 2015

fix #1126 - Update matplotlib 1.4.2 to 1.4.3

@durack1
Copy link
Member Author

@durack1 durack1 commented May 19, 2015

@aashish24 @jbeezley @doutriaux1 it seems that timeouts are causing build grief with travis again https://travis-ci.org/UV-CDAT/uvcdat/builds/63255084 - maybe my attempted travis_wait solution tried in #1129 and documented at http://docs.travis-ci.com/user/build-timeouts/#Build-times-out-because-no-output-was-received could resolve this?

@durack1
Copy link
Member Author

@durack1 durack1 commented May 22, 2015

@jbeezley @aashish24 additionally, it seems that the same single column of pixels along right hand side of test image is appearing again: https://open.cdash.org/displayImage.php?imgid=383269

@aashish24
Copy link
Contributor

@aashish24 aashish24 commented May 22, 2015

@durack1 looks like it trigged both this time. What did we miss?

@durack1
Copy link
Member Author

@durack1 durack1 commented May 22, 2015

@aashish24 weird, it seems like these tests are really flaky, it's failed, then passed, failed then passed.. I think the issue with the buildbot was that they weren't triggered until later as another PR was already being tested..

@aashish24
Copy link
Contributor

@aashish24 aashish24 commented May 22, 2015

that shouldn't cause this trouble. I haven't see something like this before (with other branches). It seems to be happening only with yours? Is that right?

@durack1
Copy link
Member Author

@durack1 durack1 commented May 22, 2015

I'm only familiar with what's happening with my PRs.. So I can't make any useful statement on your question above.. But, yes it's happening to mine..

@durack1
Copy link
Member Author

@durack1 durack1 commented Jun 1, 2015

@doutriaux1 this PR seems good to go..

@doutriaux1
Copy link
Contributor

@doutriaux1 doutriaux1 commented Jun 1, 2015

could plot something with it, approving

doutriaux1 added a commit that referenced this issue Jun 1, 2015
….3Update

Issue1126 durack1 matplotlib1.4.3 update
@doutriaux1 doutriaux1 merged commit 5aa5c8c into master Jun 1, 2015
4 checks passed
@doutriaux1 doutriaux1 deleted the issue1126_durack1_matplotlib1.4.3Update branch Jun 1, 2015
@durack1
Copy link
Member Author

@durack1 durack1 commented Jul 24, 2015

@aashish24 @doutriaux1 it appears that this PR is no longer in master (a similar situation to #1441) can you restore and merge back into master?

@aashish24
Copy link
Contributor

@aashish24 aashish24 commented Jul 24, 2015

How that happened? Did someone forced push master?

@durack1
Copy link
Member Author

@durack1 durack1 commented Jul 24, 2015

@aashish24 not sure, I believe this got tangled up with problems with the 2.2.0 release branch changes being merged back into master.. It's the 2nd such case that I've become aware of.. I'll keep my eyes open for more, there probably are additional cases..

@doutriaux1
Copy link
Contributor

@doutriaux1 doutriaux1 commented Jul 28, 2015

@sankhesh that ight help (or be the cause) of your PySide/PyQt issues

From: "Paul J. Durack" <notifications@github.commailto:notifications@github.com>
Reply-To: UV-CDAT/uvcdat <reply@reply.github.commailto:reply@reply.github.com>
Date: Monday, July 27, 2015 at 3:25 PM
To: UV-CDAT/uvcdat <uvcdat@noreply.github.commailto:uvcdat@noreply.github.com>
Cc: Charles Doutriaux <doutriaux1@llnl.govmailto:doutriaux1@llnl.gov>
Subject: Re: [uvcdat] Issue1126 durack1 matplotlib1.4.3 update (#1329)

@doutriaux1https://github.com/doutriaux1 pinging you on this too..


Reply to this email directly or view it on GitHubhttps://github.com//pull/1329#issuecomment-125366128.

@sankhesh
Copy link
Contributor

@sankhesh sankhesh commented Jul 28, 2015

I don't think this is the issue. However, I can merge these changes in my basemap_build branch with other fixes.

@doutriaux1
Copy link
Contributor

@doutriaux1 doutriaux1 commented Jul 28, 2015

sankhesh added a commit that referenced this issue Jul 28, 2015
This brings back changes introduced in 0cb99f3.
Addresses issue #1126 #1329
@durack1 durack1 mentioned this pull request Jul 28, 2015
sankhesh added a commit that referenced this issue Sep 3, 2015
This brings back changes introduced in 0cb99f3.
Addresses issue #1126 #1329
sankhesh added a commit that referenced this issue Sep 3, 2015
This brings back changes introduced in 0cb99f3.
Addresses issue #1126 #1329
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

4 participants