Boost regression notification (2006-10-12 [RC_1_34_0])
Boost Regression test failures Report time: 2006-10-12T11:00:35Z This report lists all regression test failures on release platforms. Detailed report: http://engineering.meta-comm.com/boost-regression/CVS-RC_1_34_0/developer/is... 75 failures in 13 libraries filesystem (2) io (1) iostreams (8) mpl (6) parameter (6) program_options (9) python (9) random (1) rational (5) serialization (18) spirit (7) test (2) utility (1) |filesystem| mbcopy: sun-5.8 wide_test: sun-5.8 |io| ios_state_unit_test: gcc-4.1.0_linux_x86_64 |iostreams| bzip2_test: msvc-7.1 msvc-8.0 example_test: vc-6_5-stlport finite_state_filter_test: cw-9.4 gzip_test: msvc-7.1 msvc-8.0 zlib_test: msvc-7.1 msvc-8.0 |mpl| multiset: gcc-4.0.3_linux gcc-4.1.0_linux gcc-4.1.0_linux_x86_64 gcc-4.1.1_sunos_i86pc gcc-4_0_3_tru64 vector_c: sun-5.8 |parameter| optional_deduced_sfinae: sun-5.8 preprocessor_deduced: sun-5.8 python_test: qcc-3.3.5_gpp sun-5.8 sfinae: borland-5_8_2 vc-6_5-stlport |program_options| cmdline_test_dll: cw-9.4 options_description_test_dll: cw-9.4 parsers_test_dll: cw-9.4 positional_options_test_dll: cw-9.4 unicode_test_dll: borland-5_8_2 cw-9.4 variable_map_test_dll: borland-5_8_2 cw-9.4 winmain_dll: cw-9.4 |python| numpy: darwin-4.0.1 gcc-3.3.6 gcc-3.4.4 slice: darwin-4.0.1 gcc-3.3.6 gcc-3.4.4 vc-6_5 vc-6_5-stlport vc-7_0 |random| random_test: intel-linux-9.0 |rational| rational_test: borland-5_6_4 sun-5.8 vc-6_5 vc-6_5-stlport vc-7_0 |serialization| test_class_info_load_text_warchive: vc-6_5 test_contained_class_binary_archive_dll: gcc-3.2.3_linux test_contained_class_xml_archive: gcc-3.2.3_linux test_non_default_ctor2_text_archive: qcc-3.3.5_cpp test_non_default_ctor2_text_archive_dll: qcc-3.3.5_cpp test_non_default_ctor2_text_warchive: qcc-3.3.5_cpp test_non_default_ctor2_text_warchive_dll: qcc-3.3.5_cpp test_reset_object_address: vc-7_0 test_reset_object_address_dll: vc-7_0 test_simple_class_binary_archive_dll: vc-6_5 test_simple_class_text_archive_dll: vc-6_5 test_simple_class_text_warchive_dll: vc-6_5 test_simple_class_xml_archive_dll: vc-6_5 test_simple_class_xml_warchive_dll: vc-6_5 test_variant_xml_archive: borland-5_8_2 test_variant_xml_archive_dll: borland-5_8_2 test_variant_xml_warchive: borland-5_8_2 test_variant_xml_warchive_dll: borland-5_8_2 |spirit| action_tests: qcc-3.3.5_cpp qcc-3.3.5_gpp action_tests_debug: qcc-3.3.5_cpp qcc-3.3.5_gpp mix_and_match_trees: sun-5.8 typeof_iterator: intel-vc8-win-9.1 msvc-8.0 |test| parameterized_test_test: vc-6_5 vc-6_5-stlport |utility| operators_test: gcc-3.4.5_linux_x86_64
Douglas Gregor said: (by the date of Thu, 12 Oct 2006 12:00:48 -0400)
75 failures in 13 libraries filesystem (2) io (1) iostreams (8) mpl (6) parameter (6) program_options (9) python (9) random (1) rational (5) serialization (18) spirit (7) test (2) utility (1)
Hi Doug, after 10 minutes (no more), including some googling I produced this: 75 failures in 13 libraries (37 are from non-broken platforms) non-broken broken filesystem 0 2 io 1 iostreams 7 8 mpl 5 6 parameter 2 6 program_options 0 9 python 8 9 random 1 rational 3 5 serialization 4 18 spirit 4 7 test 1 2 utility 1 The key function here is string.ljust(). If you like this, here is the diff -u @@ -409,18 +409,17 @@ str(len(self.libraries)) + ' libraries') if any_broken_platforms: message += ' (' + str(self.numReportableFailures()) + ' are from non-broken platforms)' - message += '\n' + message += '\n\n non-broken broken\n' # Display the number of failures per library for k in sorted_keys( self.libraries ): library = self.libraries[k] num_failures = library.numFailures() - message += (' ' + library.name + ' (' + message += (' ' + library.name.ljust(22) + ' ' + str(library.numReportableFailures())) if library.numReportableFailures() < num_failures: - message += (' of ' + str(num_failures) - + ' failures are from non-broken platforms') - message += ')\n' + message += (' ' + str(num_failures)) + message += '\n' pass # If we have any broken platforms, tell the user how we're -- Janek Kozicki |
On 2006-10-12, Janek Kozicki <janek_listy@wp.pl> wrote:
Hi Doug, after 10 minutes (no more), including some googling I produced this: 75 failures in 13 libraries (37 are from non-broken platforms) non-broken broken filesystem 0 2 io 1 iostreams 7 8 [...]
The "broken" heading does not tally with the value. It should either be named "total", or the value in the column should have "non-broken" subtracted from it... (The latter seems more useful.) phil -- change name before "@" to "phil" for email
Phil Richards said: (by the date of Thu, 12 Oct 2006 21:47:06 +0100 (BST))
On 2006-10-12, Janek Kozicki <janek_listy@wp.pl> wrote:
Hi Doug, after 10 minutes (no more), including some googling I produced this: 75 failures in 13 libraries (37 are from non-broken platforms) non-broken broken filesystem 0 2 io 1 iostreams 7 8 [...]
The "broken" heading does not tally with the value. It should either be named "total", or the value in the column should have "non-broken" subtracted from it... (The latter seems more useful.)
of course I'm sorry, I was too quick :) -- Janek Kozicki |
Janek Kozicki said: (by the date of Fri, 13 Oct 2006 07:42:25 +0200) ok. maybe you will like this: 75 failures in 13 libraries (37 are from non-broken platforms) non-broken broken total filesystem 0 2 2 io 1 iostreams 7 1 8 mpl 5 1 6 parameter 2 4 6 program_options 0 9 9 python 8 1 9 random 1 rational 3 2 5 serialization 4 14 18 spirit 4 3 7 test 1 1 2 utility 1 To get this: utility 1 0 1 simply comment the line marked with [1] The code for that: message += (str(self.numFailures()) + ' failures in ' + str(len(self.libraries)) + ' libraries') if any_broken_platforms: message += ' (' + str(self.numReportableFailures()) + ' are from non-broken platforms)' message += '\n\n non-broken broken total\n' # Display the number of failures per library for k in sorted_keys( self.libraries ): library = self.libraries[k] num_failures = library.numFailures() message += (' ' + library.name.ljust(22) + ' ' + str(library.numReportableFailures()).ljust(9) ) # [1] comment this "if" line if library.numReportableFailures() < num_failures: message += (' ' + str(num_failures - library.numReportableFailures() ).ljust(8) + ' ' + str(num_failures)) message += '\n' pass Anyway, I'm off with that. Take it or not :) -- Janek Kozicki |
"Janek Kozicki" <janek_listy@wp.pl> wrote
Janek Kozicki said: (by the date of Fri, 13 Oct 2006 07:42:25 +0200)
ok. maybe you will like this:
75 failures in 13 libraries (37 are from non-broken platforms)
non-broken broken total filesystem 0 2 2 io 1 iostreams 7 1 8 mpl 5 1 6 ...
FWIW, in the outlook express viewer, this doesn't look pretty at all... there is no alighnment whatsoever :( Regards, Arkadiy
On Oct 13, 2006, at 7:59 AM, Arkadiy Vertleyb wrote:
"Janek Kozicki" <janek_listy@wp.pl> wrote
Janek Kozicki said: (by the date of Fri, 13 Oct 2006 07:42:25 +0200)
ok. maybe you will like this:
75 failures in 13 libraries (37 are from non-broken platforms)
non-broken broken total filesystem 0 2 2 io 1 iostreams 7 1 8 mpl 5 1 6 ...
FWIW, in the outlook express viewer, this doesn't look pretty at all... there is no alighnment whatsoever :(
Same issue here with Apple Mail. Would tabs produce better results? filesystem 0 2 2 io 1 iostreams 7 1 8 mpl 5 1 6 Hmmm... Cheers, Doug
"Doug Gregor" <dgregor@cs.indiana.edu> wrote
On Oct 13, 2006, at 7:59 AM, Arkadiy Vertleyb wrote:
"Janek Kozicki" <janek_listy@wp.pl> wrote
Janek Kozicki said: (by the date of Fri, 13 Oct 2006 07:42:25 +0200)
ok. maybe you will like this:
75 failures in 13 libraries (37 are from non-broken platforms)
non-broken broken total filesystem 0 2 2 io 1 iostreams 7 1 8 mpl 5 1 6 ...
FWIW, in the outlook express viewer, this doesn't look pretty at all... there is no alighnment whatsoever :(
Same issue here with Apple Mail. Would tabs produce better results?
filesystem 0 2 2 io 1 iostreams 7 1 8 mpl 5 1 6
They might -- just try to use more tabs after the library name... Regards, Arkadiy
Doug Gregor said: (by the date of Fri, 13 Oct 2006 10:31:43 -0400)
ok. maybe you will like this:
75 failures in 13 libraries (37 are from non-broken platforms)
non-broken broken total filesystem 0 2 2 io 1 iostreams 7 1 8 mpl 5 1 6 ...
FWIW, in the outlook express viewer, this doesn't look pretty at all... there is no alighnment whatsoever :(
Same issue here with Apple Mail. Would tabs produce better results?
filesystem 0 2 2 io 1 iostreams 7 1 8 mpl 5 1 6
Hmmm...
this is strange if you are using fixed size font. That function string.ljust(N) simply adds spaces until desired length is achieved. I think that tabs will not help here, or if the will fix the alignment for AppleMail it will be broken for other mail readers. You can verify this by running the script in a terminal (with --debug ;) So I guess that status quo is a better solution.... :/ -- Janek Kozicki |
On 2006-10-13, Doug Gregor <dgregor@cs.indiana.edu> wrote:
Same issue here with Apple Mail. Would tabs produce better results?
Almost never... Tabs that work for an Outlook message don't work when translated to 8 characters in a fixed width font. It is rather odd/sad for any mail reader not to be able to render the message in a fixed width font correctly. Short of sending out a multipart MIME message with two alternatives (text and, say, html) I can't see a general solution. phil -- change name before "@" to "phil" for email
Arkadiy Vertleyb wrote:
"Janek Kozicki" <janek_listy@wp.pl> wrote
Janek Kozicki said: (by the date of Fri, 13 Oct 2006 07:42:25 +0200)
ok. maybe you will like this:
75 failures in 13 libraries (37 are from non-broken platforms)
non-broken broken total filesystem 0 2 2 io 1 iostreams 7 1 8 mpl 5 1 6 ...
FWIW, in the outlook express viewer, this doesn't look pretty at all... there is no alighnment whatsoever :(
Change your display font to a fixed width font (Courier New) and you'll hopefully get proper alignment. Tabs won't help either, as you cannot change the tab settings in plain text. I think it's reasonable to require using a fixed with font if proper alignment is important in plain text mails. Markus
"Markus Schöpflin" <markus.schoepflin@comsoft.de> wrote
Arkadiy Vertleyb wrote:
"Janek Kozicki" <janek_listy@wp.pl> wrote
Janek Kozicki said: (by the date of Fri, 13 Oct 2006 07:42:25 +0200)
ok. maybe you will like this:
75 failures in 13 libraries (37 are from non-broken platforms)
non-broken broken total filesystem 0 2 2 io 1 iostreams 7 1 8 mpl 5 1 6 ...
FWIW, in the outlook express viewer, this doesn't look pretty at all... there is no alighnment whatsoever :(
Change your display font to a fixed width font (Courier New) and you'll hopefully get proper alignment.
Well, changing font to fixed doesn't affect anything for me. Maybe I am doing something wrong or maybe outlook is doing something wrong -- I am not sure. In any case, requiring to use a fixed font seems too strong to me. I would rather leave everything as it is now. Regards, Arkadiy
participants (6)
-
Arkadiy Vertleyb -
Doug Gregor -
Douglas Gregor
-
Janek Kozicki -
Markus Schöpflin -
Phil Richards