> if you want, you could fix the ChangeLog entry in place, but don't add a
> new one for that change.
Done,
Dominique
Hi Dominique,
> Thanks for the tip. What should I do now? Should I fix the ChangeLog entry
> and add a new one or do nothing?
if you want, you could fix the ChangeLog entry in place, but don't add a
new one for that change.
Rainer
--
Thanks for the tip. What should I do now? Should I fix the ChangeLog entry and
add a new one or do nothing?
Dominique
Le 2 avr. 2014 à 12:47, Rainer Orth a écrit :
> domi...@lps.ens.fr (Dominique Dhumieres) writes:
>
>> r...@cebitec.uni-bielefeld.de (Rainer Orth) wrote:
>>> Sure, patch preap
domi...@lps.ens.fr (Dominique Dhumieres) writes:
> r...@cebitec.uni-bielefeld.de (Rainer Orth) wrote:
>> Sure, patch preapproved.
>
> Commited as r208983:
>
> 2014-04-01 Dominique d'Humieres
> Rainer Orth
>
> PR libgcj/55637
> * testsuite/libjava.lang/so
r...@cebitec.uni-bielefeld.de (Rainer Orth) wrote:
> Sure, patch preapproved.
Commited as r208983:
2014-04-01 Dominique d'Humieres
Rainer Orth
PR libgcj/55637
* testsuite/libjava.lang/sourcelocation.xfail: New file.
Index: libjava/testsuite/libjava.la
domi...@lps.ens.fr (Dominique Dhumieres) writes:
>> The libjava sourcelocation output test has been FAILing on mainline for
>> more than a year, with no sign of anything happening to resolve that.
>> To reduce testsuite noise, I suggest to XFAIL the test. ...
>
> Would it be possible to backport
> The libjava sourcelocation output test has been FAILing on mainline for
> more than a year, with no sign of anything happening to resolve that.
> To reduce testsuite noise, I suggest to XFAIL the test. ...
Would it be possible to backport the fix to 4.8?
TIA,
Dominique
Bryce McKinlay writes:
> The fix for this is to have libjava use libbackttrace to get source
> line numbers, rather than rely on external addr2line.
I see. Doesn't sound exactly like 4.9 material, though.
Thanks.
Rainer
--
-
On Thu, Feb 20, 2014 at 12:05 PM, Rainer Orth
wrote:
> The libjava sourcelocation output test has been FAILing on mainline for
> more than a year, with no sign of anything happening to resolve that.
> To reduce testsuite noise, I suggest to XFAIL the test. In all mainline
> test results from feb
The libjava sourcelocation output test has been FAILing on mainline for
more than a year, with no sign of anything happening to resolve that.
To reduce testsuite noise, I suggest to XFAIL the test. In all mainline
test results from february, only a single set of testresults that
included libjava r
10 matches
Mail list logo
