search

felipeprov / include-what-you-use

Automatically exported from code.google.com/p/include-what-you-use
Other
0 stars 0 forks source link

iwyu test fails in badinc.cc #4

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?  Give the *exact* arguments passed

python run_iwyu_tests.py

What is the expected output? What do you see instead?

Expected: OK
Output Instead:

[..]
ERROR:root:Test failed for tests/badinc.cc

---
tests/badinc.cc:580: expecting 2 diagnostics; actually had 1:
I1_Class needs a declaration, but does not provide or directly #include one.

---
[..]

F
======================================================================
FAIL: testIwyuWorks (__main__.IwyuTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "run_iwyu_tests.py", line 68, in testIwyuWorks
    self.assert_(not failed_tests, 'Failed tests: %s' % ' '.join(failed_tests))
AssertionError: Failed tests: tests/badinc.cc

----------------------------------------------------------------------
Ran 1 test in 12.055s

FAILED (failures=1)

What version of the product are you using? On what operating system?

iwyu 0.1 with svn llvm and svn clang. Ubuntu 10.10 64bit.

Please provide any additional information below.

..

Original issue reported on code.google.com by daniel.v...@googlemail.com on 5 Feb 2011 at 1:31

GoogleCodeExporter commented 9 years ago 
Not sure what might be going on.  The test passes for me.  You'll probably have 
to try to debug this (I have some tips on the wiki page, but debugging these 
things isn't easy), at least, and optimally also construct a patch that fixes 
the problem :-), whatever it might be.

Original comment by csilv...@gmail.com on 7 Feb 2011 at 6:45

GoogleCodeExporter commented 9 years ago 
We think we've figured out the problem here: there was code that was comparing 
dangling pointers (of temporary objects that had gone out of scope) and 
sometimes those comparisons were spuriously succeeding because the memory 
happened to be allocated at the same place.  I've got a fix pending, and should 
be in the tree shortly.  Hopefully this will fix the problem for you.

Original comment by csilv...@gmail.com on 24 Feb 2011 at 9:16

GoogleCodeExporter commented 9 years ago 
After some hickups in the last weeks, in svn 86 I get no more errors running 
the tests. So I would consider this issue solved.

Original comment by daniel.v...@googlemail.com on 18 Mar 2011 at 10:09

GoogleCodeExporter commented 9 years ago 
Great to hear!

Original comment by csilv...@gmail.com on 18 Mar 2011 at 11:16