I would agree 99% of the time but if it is indeed the case that nothing can be done about it in the near future or without considerable effort/funding then it's as Bill says, more of a distraction.<br><br><div class="gmail_quote">
On Thu, Jan 14, 2010 at 1:10 PM, David Gobbi <span dir="ltr"><<a href="mailto:david.gobbi@gmail.com">david.gobbi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
If the errors are indeed genuine (even if they are brought about by<br>
peculiarities in the system architecture), then they should stay on<br>
the dashboard, shouldn't they?<br>
<br>
Just my 2 cents, though I'm not sure if I've understood the issue completely.<br>
<font color="#888888"><br>
- David<br>
</font><div><div></div><div class="h5"><br>
<br>
On Thu, Jan 14, 2010 at 10:57 AM, Dave Partyka <<a href="mailto:dave.partyka@kitware.com">dave.partyka@kitware.com</a>> wrote:<br>
> I am actually more inclined to just disable metaIO on that machine as it<br>
> doesn't appear to have issues anywhere else. If no one objects I will set<br>
> VTK_USE_METAIO off as it defaults to ON for that machine.<br>
><br>
> On Thu, Jan 14, 2010 at 12:54 PM, Bill Lorensen <<a href="mailto:bill.lorensen@gmail.com">bill.lorensen@gmail.com</a>><br>
> wrote:<br>
>><br>
>> Not specualting, just doing the best I can with my limited knowledge.<br>
>><br>
>> On Thu, Jan 14, 2010 at 12:42 PM, Francois Bertel<br>
>> <<a href="mailto:francois.bertel@kitware.com">francois.bertel@kitware.com</a>> wrote:<br>
>> > Stop speculating, the issue is in metaio. Here is the reason of the<br>
>> > failure and there is unfortunately no trivial solution right now (even<br>
>> > for Brad King!):<br>
>> ><br>
>> > From an private thread of discussion involving me, Luis, Julien Jomier<br>
>> > and Brad King, Dec 4 2009:<br>
>> ><br>
>> > Brad King said:<br>
>> ><br>
>> > "<br>
>> > $ nm libvtkmetaio.so | grep ElementByteOrderFix<br>
>> > .vtkmetaio::MetaArray::ElementByteOrderFix() T 271508768 172<br>
>> > .vtkmetaio::MetaImage::ElementByteOrderFix(long) T 269262912<br>
>> > 180<br>
>> > ...<br>
>> ><br>
>> > $ nm libvtkIO.so| grep ElementByteOrderFix<br>
>> > ...<br>
>> > vtkmetaio::MetaImage::ElementByteOrderFix(long long) U -<br>
>> ><br>
>> > Something is causing streamoff to be a different size in one of vtkIO's<br>
>> > translation units than in metaio's translation units. It's probably the<br>
>> > KWSys Configure.h that defines _LARGEFILE_SOURCE and related macros<br>
>> > (this<br>
>> > was something Andy Cedilnik added at some point to "guarantee" LFS<br>
>> > support<br>
>> > in all Kitware projects)."<br>
>> ><br>
>> > Brad King said:<br>
>> ><br>
>> > "<br>
>> > [I recommends to] teach MetaIO about large file support.<br>
>> ><br>
>> > Doing it right is a bit tricky. This is one of those cases that<br>
>> > requires<br>
>> > users of a library to define macros before including its headers. We<br>
>> > have<br>
>> > generally avoided this requirement by configuring feature settings into<br>
>> > header files such as vtkConfigure.h. However, the problem here is that<br>
>> > enabling large file support means defining a macro like<br>
>> > _LARGEFILE_SOURCE<br>
>> > in *every* translation unit before any *system* header is included.<br>
>> > This<br>
>> > cannot be done reliably in a place like vtkConfigure.h because users<br>
>> > could<br>
>> > write this:<br>
>> ><br>
>> > #include <stdio.h><br>
>> > #include <vtkObject.h> /* Uh oh, _LARGEFILE_SOURCE is defined too late!<br>
>> > */<br>
>> ><br>
>> > By the time our configured header gets included, the system API has<br>
>> > already<br>
>> > been loaded without large file support! If instead we require users to<br>
>> > add -D_LARGEFILE_SOURCE on the command line then it will apply to the<br>
>> > system API no matter when it is included.<br>
>> ><br>
>> > A better approach is this:<br>
>> ><br>
>> > # CMakeLists.txt<br>
>> > # ... try compiles to detect proper LFS_MACRO ...<br>
>> > add_definitions(-D${LFS_MACRO})<br>
>> ><br>
>> > /* <a href="http://myconfig.h.in" target="_blank">myconfig.h.in</a> */<br>
>> > #ifndef @LFS_MACRO@<br>
>> > # error "This source requires -D@LFS_MACRO@"<br>
>> > #endif<br>
>> ><br>
>> > The LFS_MACRO value can be put in the FooConfig.cmake file for use by<br>
>> > outside projects.<br>
>> ><br>
>> > Unfortunately we did not understand this problem back when the macros<br>
>> > were<br>
>> > put in KWSys, and changing it there now is very hard for compatibility<br>
>> > :(<br>
>> > "<br>
>> ><br>
>> ><br>
>> > On Thu, Jan 14, 2010 at 12:30 PM, Dave Partyka<br>
>> > <<a href="mailto:dave.partyka@kitware.com">dave.partyka@kitware.com</a>> wrote:<br>
>> >> Humm I didn't noticed that it was using nightly CMake. I<br>
>> >> most certainly will<br>
>> >> give it a shot. Thanks for pointing that out!<br>
>> >><br>
>> >> On Thu, Jan 14, 2010 at 12:27 PM, Bill Lorensen<br>
>> >> <<a href="mailto:bill.lorensen@gmail.com">bill.lorensen@gmail.com</a>><br>
>> >> wrote:<br>
>> >>><br>
>> >>> Dave,<br>
>> >>><br>
>> >>> I noticed that this build is using cmake2.9. Have you tried it with<br>
>> >>> cmake2.8?<br>
>> >>><br>
>> >>> Bill<br>
>> >>><br>
>> >>> On Thu, Jan 14, 2010 at 11:54 AM, Dave Partyka<br>
>> >>> <<a href="mailto:dave.partyka@kitware.com">dave.partyka@kitware.com</a>><br>
>> >>> wrote:<br>
>> >>> > I just fixed all the compile errors late last week and now it just<br>
>> >>> > has<br>
>> >>> > test<br>
>> >>> > failures. I'll keep prodding at it.<br>
>> >>> ><br>
>> >>> > On Thu, Jan 14, 2010 at 11:52 AM, Bill Lorensen<br>
>> >>> > <<a href="mailto:bill.lorensen@gmail.com">bill.lorensen@gmail.com</a>><br>
>> >>> > wrote:<br>
>> >>> >><br>
>> >>> >> Folks,<br>
>> >>> >><br>
>> >>> >> Late October was the last time the site <a href="http://v20n17.pbm.ihost.com" target="_blank">v20n17.pbm.ihost.com</a> had a<br>
>> >>> >> green dashboard.<br>
>> >>> >><br>
>> >>> >> Could the owner of this build please take a look and see if the<br>
>> >>> >> problems can be resolved? Currently it is reporting 610 failing<br>
>> >>> >> tests:<br>
>> >>> >> <a href="http://www.cdash.org/CDash/viewTest.php?onlyfailed&buildid=514704" target="_blank">http://www.cdash.org/CDash/viewTest.php?onlyfailed&buildid=514704</a><br>
>> >>> >><br>
>> >>> >> Or, perhaps we no longer support this compiler: AIX00C518-xlC ?<br>
>> >>> >><br>
>> >>> >> Bill<br>
>> >>> >> _______________________________________________<br>
>> >>> >> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>> >>> >><br>
>> >>> >> Visit other Kitware open-source projects at<br>
>> >>> >> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>> >>> >><br>
>> >>> >> Follow this link to subscribe/unsubscribe:<br>
>> >>> >> <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
>> >>> >><br>
>> >>> ><br>
>> >>> ><br>
>> >><br>
>> >><br>
>> >> _______________________________________________<br>
>> >> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>> >><br>
>> >> Visit other Kitware open-source projects at<br>
>> >> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>> >><br>
>> >> Follow this link to subscribe/unsubscribe:<br>
>> >> <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
>> >><br>
>> >><br>
>> >><br>
>> ><br>
>> ><br>
>> ><br>
>> > --<br>
>> > François Bertel, PhD | Kitware Inc. Suite 204<br>
>> > 1 (518) 371 3971 x113 | 28 Corporate Drive<br>
>> > | Clifton Park NY 12065, USA<br>
>> > _______________________________________________<br>
>> > Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>> ><br>
>> > Visit other Kitware open-source projects at<br>
>> > <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>> ><br>
>> > Follow this link to subscribe/unsubscribe:<br>
>> > <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
>> ><br>
>> ><br>
>> _______________________________________________<br>
>> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>><br>
>> Visit other Kitware open-source projects at<br>
>> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>><br>
>> Follow this link to subscribe/unsubscribe:<br>
>> <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
><br>
> Visit other Kitware open-source projects at<br>
> <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
><br>
> Follow this link to subscribe/unsubscribe:<br>
> <a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
><br>
><br>
><br>
</div></div></blockquote></div><br>