[FFmpeg-trac] #6828(undetermined:new): ffmpeg git master compile error with libva 2.0

[FFmpeg]

#6828: ffmpeg git master compile error with libva 2.0
-------------------------------------+-------------------------------------
             Reporter:  bermond      |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  important    |                Component:
              Version:  git-master   |  undetermined
             Keywords:  regression   |               Resolution:
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0
-------------------------------------+-------------------------------------

Comment (by bermond):

 I could not get a conclusive result with git bisect.

 Initial result is:
 {{{
 $ git bisect start
 $ git bisect bad
 $ git bisect good n3.4
 Bisecting: a merge base must be tested
 [7bec3f78da2533968b7246ff222770582ab4aafb] avcodec/rkmppdec: check wether
 typo
 <build fails with chosen commit 7bec3f78da2533968b7246ff222770582ab4aafb>
 $ git bisect bad
 The merge base 7bec3f78da2533968b7246ff222770582ab4aafb is bad.
 This means the bug has been fixed between
 7bec3f78da2533968b7246ff222770582ab4aafb and
 [01e291a592452f27b3a4e811536aaaf94096e244].
 }}}


 From this point, git bisect cannot proceed any further.

 The first commit in the range provided by git bisect is the "bad merge",
 and it fails to compile, being a bad commit. The second one points to n3.4
 release tag, which compiles fine, being a good commit.

 When bisecting between this range using each one as the bad and good
 commits, git bisect shows nothing:
 {{{
 $ git bisect reset
 $ git bisect start
 $ git bisect bad 7bec3f78da2533968b7246ff222770582ab4aafb
 $ git bisect good 01e291a592452f27b3a4e811536aaaf94096e244
 Some good revs are not ancestors of the bad rev.
 git bisect cannot work properly in this case.
 Maybe you mistook good and bad revs?
 }}}

--
Ticket URL: <https://trac.ffmpeg.org/ticket/6828#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker