-
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
Bugfixes #1456
Bugfixes #1456
Conversation
@dlonie can you update this branch? Also, @doutriaux1 can you approve this branch soon? |
Added it to my list -- When I'm back on UVCDAT I'll do it first thing. On Tue, Jul 21, 2015 at 10:28 AM, Aashish Chaudhary <
|
Rebased on current master. |
@doutriaux1 this looks good to me. However, you should review it so that we can get it merged soon. |
👍 |
will test on mac and ubunutu on monday |
Okay, thanks! |
@dlonie looks like we need a rebase. |
Otherwise it will reset WIP branches to use master.
@dlonie just rebased don't worry about it. Testing on ubuntu now |
@dlonie did I mess up the rebase? RH6: https://open.cdash.org/viewTest.php?onlyfailed&buildid=3925430 |
ok fixed the rebase issue, much better now: @sankhesh @dlonie looks like label are now behind isolines, not great, which one of you should look into this? |
@doutriaux1 looks like the date of the data indexed has changed - |
Looks like an issue on your machine. All of the isoline tests pass on mine with the rebased changes, and buildbot is happy with it too. The only failure I see is a style issue in the rebased code: https://open.cdash.org/viewTest.php?onlyfailed&buildid=3925493 Also, neither buildbot nor I am getting any of these errors/warnings:
They are present in all of the failing tests on your machine, but not anywhere else. Not sure what's going on with your system. |
I’m more worried about this being an issue with OS I will try on another RH then. |
@sankhesh do you have a RedHat machine accessible, I get loads of errors on another RedHat see: |
I don't. I can try to fire up a CentOS6 VM. |
@doutriaux1 is this hint maybe partially why the error with #1329? In particular I'm noting that it's picking up a lineage from the 2.2.0rc1 branch rather than 2.2.0
|
Folks, Here is a CentOS 6.6 build of master branch that shows the same errors as reported by @doutriaux1. I don't think these issues are related to #1456. Furthermore, I ran into #1192 as well. |
This definitely seems like a VCS issue. I suspected it to be an OpenGL related issue, but the VTK dashboard was clean on this machine. https://open.cdash.org/viewTest.php?onlypassed&buildid=3938803 I still get 23 test failures with CDAT_BUILD_GUI=OFF on the same machine with UV-CDAT: https://open.cdash.org/viewTest.php?onlyfailed&buildid=3938788 |
Since these failures happen on master, without GUI, and VTK works fine on this OS, these errors don't seem to be related to this branch. Since this branch works everywhere else and introduces no new failures on RedHat/CentOS from the ones that we see on master, can this get merged? |
@dlonie I agree. It seems to be related to some other factor that is more related to GL/OS issue. Can yo file a bug? @doutriaux1 what you think? |
@aashish24 I don't think anything, all I know is we can't merge this branch until it passes on our officially platforms... |
@doutriaux1....if master is also failing on this platform, this branch is not causing the problem.... But whatever. I don't really care when/if this makes it in, but that argument makes no sense. |
@doutriaux1 I have to agree with @dlonie here. I think the bugs are not related to this branch unless I am missing something. Also, GL errors are happening because of machine and driver combination. We should file another bug for it. |
@doutriaux1 I looked at the code again. I don't see anything here that could cause GL errors. I highly recommend that we merge this branch as soon as possible. Call me if you have any doubts. |
all i'm saying is it doesn't pass on RH. Feel free to open another issue, fix the issue, merge back in this branch and then we can approve this one. |
Like I said, I don't really care if we hold off on merging this, as long as you realize that enacting that policy while master is failing on RH means that any and all new PRs cannot be merged, so we're essentially freezing master until that is fixed. |
I do realize that. That's why it's important someone fixes it quickly. |
@sankhesh @dlonie @doutriaux1 these errors:
https://open.cdash.org/testDetails.php?test=359872924&build=3938788 Look awfully similar to the X11-related problems I was encountering a while back.. I wonder if with the redhat6.7 (and possibly CentOS) patches that have recently started being pushed, some X11-config issue has cropped up on these machines? I've hit similar issues when using 8-bit vs higher colour modes on forwarding displays, the output of some of the failing test images look suspiciously low-bit to me.. I also wonder whether the data being indexed as noted above could also be an issue - it seems that the date is changing in some of these image tests |
@williams13 what do you think? |
@sankhesh @dlonie @doutriaux1 I also noted a branch lineage difference with a few of these, so: @doutriaux1 is building with a git hash: Whereas @sankhesh is building with a different hash: I wonder if a test (and or the data) or the index of the data is different between these - there have certainly been cases where we've lost merged branches in the master/release tangle: #1329 and #1441 |
@dlonie I'm going to try on master, I didn't realize it's happening there either. If it happens on master a swell then yes I'm ok to merge this one in. |
I think @durack1 is on to something. Google searches on the |
ok lots of failure on master as welll.... merging this in so we can focus on fixing these errors. This means though that I'm going to focus mainly on setting up a buildbot server here so that we can have automatic testing of our officially supported platform AND more combinations of build modes. |
fyi master failures: https://open.cdash.org/viewTest.php?onlyfailed&buildid=3940803 |
thanks @doutriaux1 +1 for @buildbot |
@doutriaux1 @chaosphere2112 @aashish24 @sankhesh
This branch has some bugfixes that were #1450, but since that is delayed due to stability issues, I've pulled some of the useful commits out of it so they can be merged sooner.
Once this is merged, #1450 needs to be rebased on master and when the memory leaks are fixed, #1450 can be merged.