Re: [Boost-testing] [date_time] marking tests as expected failures onHP-UX/aCC

From: Boris Gubenko (Boris.Gubenko_at_[hidden])
Date: 2007-02-16 17:47:10

I did not get any response to the attached mail and the four date_time
library tests in the attached mail have not been marked as expected
failures on HP-UX/aCC6 (toolset "acc").

Can it be done in the 1.34 timeframe, until this release is still open
for this kind of changes?

The reason marking the tests is important for HP is that we urge our
customers to look at Metacomm website and see for themselves
whether (and how well) the functionality they need is supported, based on
test results. For now, all the information about these tests the customers
get is: "This failure was present in the reference ("last-known-good")
release". This is good, but not good enough :-) These failures have been
investigated and understood and we want the customers to see this
information also.

Thanks,
  Boris

----- Original Message ----- 
From: "Boris Gubenko" <Boris.Gubenko_at_[hidden]>
To: "Running Boost regression tests" <boost-testing_at_[hidden]>
Cc: <boost_at_[hidden]>; "Boris Gubenko" <Boris.Gubenko_at_[hidden]>
Sent: Monday, January 29, 2007 5:24 PM
Subject: [Boost-testing] [date_time] marking tests as expected failures 
onHP-UX/aCC

> Four date_time library tests rely on undefined behaviour: 17.4.3.6 - Other
> functions [lib.res.on.functions]
>
> -2- In particular, the effects are undefined in the following cases:
> ...
>    o if an incomplete type (basic.types) is used as a template argument
>      when instantiating a template component.
>
> These tests fail on HP-UX/aCC because default STL on this platform -- Rogue
> Wave library rw libstd v2.2 -- does not allow this usage (Rogue Wave library
> on Tru64: rw libstd v2.0, as well as gnu libstdc++ and STLport, allow this).
> Attached a reproducer.
>
> In June 2006, I discussed this issue with Jeff Garland. I was going to look
> at creating a patch, but did not have any chance. According to Jeff, "it
> sounds like a major bit of work" and now it is, obviously, too late for
> 1.34. Besides, there is an enhancement request for Rogue Wave library (now
> Apache stdcxx) to allow this usage, so, perhaps, there will be no need to
> mess with the boost date_time library at all.
>
> My understanding from a mail from the 1.34 release manager is that while
> boost libraries' code is frozen for non-essential fixes, explicit failures
> markup file can be updated. So, can the four date_time library tests below
> be marked as expected failures on HP-UX/aCC (toolset name="acc") in both
> 1.34 and the HEAD:
>
>    testdate_input_facet_dll
>    testtime_input_facet
>    testlocal_time_input_facet
>    testdate_input_facet
>
> Thanks,
>  Boris
>
> x.cpp
> -----
> #include <map>
>
> struct string_parse_tree
> {
>  typedef std::multimap<char, string_parse_tree> ptree_coll;
>  ptree_coll m_next_chars;
> };
>
> string_parse_tree x;
>
> bash-2.03$ aCC -V
> aCC: HP aC++/ANSI C B3910B A.06.10 [Mar 22 2006]
> bash-2.03$ aCC -c x.cpp
> "/opt/aCC/include_std/utility", line 100: error #2070: incomplete type is not
>          allowed
>      second_type second;
>                  ^
>          detected during:
> ...
> bash-2.03$ aCC -c -I  $STLPORT_ROOT/stlport x.cpp
> bash-2.03$ g++ -c x.cpp
> bash-2.03$
>
> cxxosf.zko.hp.com> cxx -V
> Compaq C++ V7.1-006 for Compaq Tru64 UNIX V5.1B (Rev. 2650)
> Compiler Driver V7.1-006 (cxx) cxx Driver
> cxxosf.zko.hp.com> cxx -c x.cpp
> cxxosf.zko.hp.com>
>
>
> _______________________________________________
> Boost-Testing mailing list
> Boost-Testing_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-testing
>
>