[vtk-developers] [VTK 0014170]: Segfault in vtkSmartVolumeMapper

[Biddiscombe, John A.]

Not very impressed with this gerrit stuff. In the old days I’d commit a change and the next morning the dashboard would show the files updated and the tests run (this code wasn’t tested, so I’m not expecting problems).

How will I know when to monitor the dashboard when the commits sit inside gerrit until one day something presumably happens?

JB

From: Biddiscombe, John A.
Sent: 15 July 2013 17:17
To: Biddiscombe, John A.; David Cole; Bill Lorensen
Cc: vtk-developers at vtk.org
Subject: RE: [vtk-developers] [VTK 0014170]: Segfault in vtkSmartVolumeMapper

On another machine the change-ID is generated correctly. So I’ve pushed from there.



From: vtk-developers-bounces at vtk.org<mailto:vtk-developers-bounces at vtk.org> [mailto:vtk-developers-bounces at vtk.org] On Behalf Of Biddiscombe, John A.
Sent: 15 July 2013 16:03
To: David Cole; Bill Lorensen
Cc: vtk-developers at vtk.org<mailto:vtk-developers at vtk.org>
Subject: Re: [vtk-developers] [VTK 0014170]: Segfault in vtkSmartVolumeMapper

I did the setup stuff first and tried many times to redo the commit, but it won’t generate one. Unfortunalty, I’m trying to work on another branch and if I switch back to the topic branch the entire paraview will rebuild again ☹ so I’m reluctant to experiment.

JB


From: David Cole [mailto:dlrdave at aol.com]
Sent: 15 July 2013 16:00
To: Bill Lorensen; Biddiscombe, John A.
Cc: vtk-developers at vtk.org<mailto:vtk-developers at vtk.org>
Subject: Re: [vtk-developers] [VTK 0014170]: Segfault in vtkSmartVolumeMapper

> I can’t do a gerrit push because it keeps asking for an Id and I don’t want to make one up!
>
> Where do I get it from?


It comes from the stuff set up by the setup for development script.

If you made the commit before running the script, it won’t have one.

If you just do “git commit --amend” now on that commit, one should be added for you.

Then you should be able to push.


HTH,
David C.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20130717/3181d438/attachment.html>