[Paraview-developers] communication errors

[Biddiscombe, John A.]

Utkarsh

Any approximate idea of when this might make it into master. I cherry-picked 4 commits from next which stop the wrong tag messages, but the client still locks up, so paraview (client/server) is still essentially unusable for me. I do some more digging to try to see if any more patches might be required, but until it goes into master, I guess I won't be certain I've got what I need.

ta

JB

-----Original Message-----
From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com] 
Sent: 28 July 2011 18:52
To: Biddiscombe, John A.
Cc: paraview-developers at paraview.org
Subject: Re: [Paraview-developers] communication errors

NO! Switching to next is like working with the most-experimental
branch. All changes that don't cause dashboard issues are moved to
master every week (on Friday) in what we are calling "Gatekeeper
Meetings".

Utkarsh

On Thu, Jul 28, 2011 at 11:24 AM, Biddiscombe, John A. <biddisco at cscs.ch> wrote:
> Should I just switch to next instead of master?
>
>
>
> -----Original Message-----
> From: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Sent: 28 July 2011 16:12
> To: Biddiscombe, John A.
> Cc: paraview-developers at paraview.org
> Subject: Re: [Paraview-developers] communication errors
>
> "Wrong tag messages" started showing up as a consequence of a commit
> to fix the progress bar that made it to git-master before we switched
> to the new style worflow. That issue is currently being addressed on
> git-next and will make it to master (hopefull soon).
>
> Not sure what this is. Try attaching a debugger, but a break point in
> the error-macro and look at the call-stack. Does it show anything
> fishy?
>
> Utkarsh
>
> On Thu, Jul 28, 2011 at 7:06 AM, Biddiscombe, John A. <biddisco at cscs.ch> wrote:
>> I get this (error at end) a lot these days when I run in parallel. The server appears to keep on running (I'm using 64 cores on the viz cluster, client on a windows machine - but it still happens even when running only on the windows machine with 4 pvservers).
>>
>> I suspect it is something to do with my plugins - though this usually happens during an update when I rotate the model or something - sometimes during filter operation. (Note, not using our steering stuff, only standard MPI based modules for readers/filters etc)
>>
>> How can I debug this and find out what is going wrong? I suspect it's something I've done because it only happens after applying my filters - but I never use paraview for anything else anyway - so it's a self selecting case. I don';t know that it doesn't do this when I run paraview without my stuff (if you follow me).
>>
>> JB
>>
>>
>> ERROR: In ..\..\..\..\Code\pv-meshless\VTK\Common\vtkSocket.cxx, line 572
>> vtkClientSocket (00000000097394A0): Socket error in call to send. An established connection was aborted by the software in your host machine.
>>
>> ERROR: In ..\..\..\..\Code\pv-meshless\VTK\Parallel\vtkSocketCommunicator.cxx, line 716
>> vtkSocketCommunicator (0000000009711450): Could not send tag.
>>
>> (I also get a lot of 'received wrong tag messages' but not today, so I'm posting this one)
>>
>> --
>> John Biddiscombe,                            email:biddisco @ cscs.ch
>> http://www.cscs.ch/
>> CSCS, Swiss National Supercomputing Centre  | Tel:  +41 (91) 610.82.07
>> Via Cantonale, 6928 Manno, Switzerland      | Fax:  +41 (91) 610.82.82
>>
>>
>> _______________________________________________
>> Paraview-developers mailing list
>> Paraview-developers at paraview.org
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>