From: Wheeler, F. W (G. Research) <wh...@ge...> - 2010-03-08 20:26:15
|
Yes, I mean build errors. Looks like they have already been fixed. I did not see them in later dashboard builds. In a few minutes I'll send another email about a Linux/gcc test build. Fred > -----Original Message----- > From: Brendan McCane [mailto:bre...@gm...] > Sent: Monday, March 08, 2010 3:24 PM > To: Wheeler, Frederick W (GE, Research) > Cc: Vxl-maintainers > Subject: Re: [Vxl-maintainers] vxl 1.14 beta 1 - MSVS 8.0 XP > test build > > Urk. By errors I assume you mean build errors? If so, that is bad. Is > someone working on fixing those errors? Or have they already been > fixed? > > On 9 March 2010 03:40, Wheeler, Frederick W (GE, Research) > <wh...@ge...> wrote: > > > > On a MSVC 8.0 XP build of 1.14b1 I get a few errors in > > clsfy_random_forest_builder.cxx. These are the only > errors. The same > > errors appeared on this dashboard build from about 4 days ago: > > > > http://www.cdash.org/CDash/viewBuildError.php?buildid=554720 > > > > Test results ... > > > > 96% tests passed, 33 tests failed out of 814 > > > > Total Test time (real) = 155.05 sec > > > > The following tests FAILED: > > 395 - clsfy_test_binary_hyperplane (Not Run) > > 396 - clsfy_test_binary_pdf_classifier (Not Run) > > 397 - clsfy_test_k_nearest_neighbour (Not Run) > > 398 - clsfy_test_smo_1 (Not Run) > > 399 - clsfy_test_rbf_svm_smo (Not Run) > > 400 - clsfy_test_adaboost (Not Run) > > 401 - clsfy_test_direct_boost (Not Run) > > 402 - clsfy_test_binary_threshold_1d (Not Run) > > 403 - clsfy_test_mean_square_1d (Not Run) > > 404 - clsfy_test_logit_loss_function (Not Run) > > 405 - clsfy_test_binary_hyperplane_logit (Not Run) > > 406 - clsfy_test_binary_1d_wrapper (Not Run) > > 407 - clsfy_test_binary_tree (Not Run) > > 408 - clsfy_test_random_forest (Not Run) > > 493 - mfpf_test_edge_finder (Not Run) > > 494 - mfpf_test_norm_corr1d (Not Run) > > 495 - mfpf_test_norm_corr2d (Not Run) > > 496 - mfpf_test_profile_pdf (Not Run) > > 497 - mfpf_test_region_pdf (Not Run) > > 498 - mfpf_test_region_finder (Not Run) > > 499 - mfpf_test_pose (Not Run) > > 500 - mfpf_test_mr_point_finder (Not Run) > > 501 - mfpf_test_patch_data (Not Run) > > 502 - mfpf_test_dp_snake (Not Run) > > 503 - mfpf_test_pose_predictor (Not Run) > > 647 - bsta_test_parzen_sphere (Failed) > > 655 - bsta_test_beta (Failed) > > 660 - bsta_algo_test_von_mises_update (Failed) > > 661 - bsta_algo_test_beta_updater (Failed) > > 699 - brip_test_mask (Failed) > > 722 - bvxm_test_rpc_registration_process (Failed) > > 747 - brec_test_part_hierarchy_learner (Failed) > > 778 - test_octree_kernel_operator (Failed) > > Errors while running CTest > > NMAKE : fatal error U1077: '"C:\Program Files\CMake > 2.8\bin\ctest.exe"' > > : return code '0x8' > > Stop. > > > > > > > >> -----Original Message----- > >> From: Brendan McCane [mailto:bre...@gm...] > >> Sent: Monday, March 08, 2010 12:04 AM > >> To: Vxl-maintainers > >> Subject: [Vxl-maintainers] vxl 1.14 beta 1 > >> > >> G'day Maintainers, > >> > >> I've packaged up a beta release for vxl 1.14. I have > tested it on a 64 > >> bit linux machine (running Fedora 8) with the following results: > >> > >> 98% tests passed, 13 tests failed out of 817 > >> > >> The following tests FAILED: > >> 104 - vnl_test_sparse_matrix (SEGFAULT) > >> 651 - bsta_test_parzen_sphere (Failed) > >> 659 - bsta_test_beta (Failed) > >> 662 - bsta_algo_test_mean_shift (Failed) > >> 664 - bsta_algo_test_von_mises_update (Failed) > >> 665 - bsta_algo_test_beta_updater (Failed) > >> 702 - brip_test_mask (Failed) > >> 704 - brip_test_extrema (OTHER_FAULT) > >> 725 - bvxm_test_rpc_registration_process (Failed) > >> 739 - bmdl_classify_process (SEGFAULT) > >> 750 - brec_test_part_hierarchy_learner (Failed) > >> 753 - brec_test_hierarchy_detector2 (SEGFAULT) > >> 781 - test_octree_kernel_operator (Failed) > >> Errors while running CTest > >> > >> The main concern for me is test 104 failing, although I > have a vague > >> feeling we have discussed this issue before (couldn't find > it in the > >> archives though). It seems to be a persistent failure on > the dashboard > >> too. I'm not sure if we want to do anything about it. > >> > >> Could someone download and test the release candidate please > >> (especially on a Windows machine). > >> > >> -- > >> Cheers, > >> > >> Brendan > >> > >> -------------------------------------------------------------- > >> ---------------- > >> Download Intel® Parallel Studio Eval > >> Try the new software tools for yourself. Speed compiling, find bugs > >> proactively, and fine-tune applications for parallel performance. > >> See why Intel Parallel Studio got high marks during beta. > >> http://p.sf.net/sfu/intel-sw-dev > >> _______________________________________________ > >> Vxl-maintainers mailing list > >> Vxl...@li... > >> https://lists.sourceforge.net/lists/listinfo/vxl-maintainers > >> > > > > > -------------------------------------------------------------- > ---------------- > > Download Intel® Parallel Studio Eval > > Try the new software tools for yourself. Speed compiling, find bugs > > proactively, and fine-tune applications for parallel performance. > > See why Intel Parallel Studio got high marks during beta. > > http://p.sf.net/sfu/intel-sw-dev > > _______________________________________________ > > Vxl-maintainers mailing list > > Vxl...@li... > > https://lists.sourceforge.net/lists/listinfo/vxl-maintainers > > > > > > -- > Cheers, > > Brendan > |