Your message dated Thu, 21 Jan 2016 19:56:05 -0800
with message-id <[email protected]>
and subject line Re: [pkg-php-pear] Bug#812263: symfony: FTBFS with GCC 6: test
suite failure
has caused the Debian Bug report #812263,
regarding FTBFS: Test suite failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
812263: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=812263
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: symfony
Version: 2.7.9+dfsg-1
Severity: normal
User: [email protected]
Usertags: ftbfs-gcc-6 gcc-6-unknown
This package fails to build with GCC 6. GCC 6 has not been released
yet, but it's expected that GCC 6 will become the default compiler for
stretch.
Unfortunately, it's not clear from the log why the build failed.
It's possible there's a bug in this package or in GCC. It's also
possible I reported a non-issue, although I tried to avoid that.
I apologize in advance if this is the case.
If you have some time to look into this issue, that'd be great. If
not, I can re-test the package with GCC 6 in a few weeks time.
You can find a snapshot of GCC 6 in experimental. To build with
GCC 6, you can set CC=gcc-6 CXX=g++-6 explicitly.
You may be able to find out more about this issue at
https://gcc.gnu.org/gcc-6/changes.html
> sbuild (Debian sbuild) 0.67.0 (26 Dec 2015) on dl580gen9-02.hlinux
...
> There was 1 failure:
>
> 1) Symfony\Component\Finder\Tests\Iterator\SortableIteratorTest::testAccept
> with data set #2 (3, array(array('/tmp/symfony_finder/foo/bar.tmp',
> '/tmp/symfony_finder/test.php'), array('/tmp/symfony_finder/.git',
> '/tmp/symfony_finder/.foo', '/tmp/symfony_finder/.foo/.bar',
> '/tmp/symfony_finder/.foo/bar', '/tmp/symfony_finder/test.py',
> '/tmp/symfony_finder/foo', '/tmp/symfony_finder/toto',
> '/tmp/symfony_finder/toto/.git', '/tmp/symfony_finder/foo bar'),
> array('/tmp/symfony_finder/.bar')))
> Failed asserting that two arrays are equal.
> --- Expected
> +++ Actual
> @@ @@
> Array (
> - 0 => '/tmp/symfony_finder/.foo'
> - 1 => '/tmp/symfony_finder/.foo/.bar'
> - 2 => '/tmp/symfony_finder/.foo/bar'
> - 3 => '/tmp/symfony_finder/.git'
> + 0 => '/tmp/symfony_finder/.bar'
> + 1 => '/tmp/symfony_finder/.foo'
> + 2 => '/tmp/symfony_finder/.foo/.bar'
> + 3 => '/tmp/symfony_finder/.foo/bar'
> 4 => '/tmp/symfony_finder/foo'
> 5 => '/tmp/symfony_finder/foo bar'
> 6 => '/tmp/symfony_finder/test.py'
> 7 => '/tmp/symfony_finder/toto'
> 8 => '/tmp/symfony_finder/toto/.git'
> )
>
--
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
--- Begin Message ---
* David Prévot <[email protected]> [2016-01-21 23:48]:
> > Can you reproduce?
>
> Since it has been uploaded four days ago, built by at least two persons
> involved in the upload, and also on buildd [0], I’d say no a priori. I
> just confirmed by building it again on another up to date machine
> without any issue.
>
> 0: https://buildd.debian.org/status/package.php?p=symfony&suite=unstable
>
> There is not much information about the setup used to produce the error,
> so I do not have any idea about the issue.
Ok, let's close it.
--
Martin Michlmayr
Linux for HPE Helion, Hewlett Packard Enterprise
--- End Message ---
