Bug#831248: maxima: FTBFS: tests failures

2016-10-01 Thread Camm Maguire
Greetings!  I think I have a solution with this next upload.  Please let
me know if this looks solid to you.

Take care,

Lucas Nussbaum  writes:

> Hi,
>
> Would you like me to try on a node with more RAM, to exclude that?
>
> Lucas
>
>
> On 28/09/16 at 16:17 -0400, Camm Maguire wrote:
>> When trying to supply the proper arguments to sbuild, I get
>> 
>> +--+
>> | Finished Timed Build Commands  
>>   |
>> +--+
>> 
>> 
>> bash -i /dev/tty 2>/dev/tty
>> --
>> 
>> /bin/sh: 1: cannot open /dev/tty: No such device or address
>> 
>> E: Command 'bash -i /dev/tty 2>/dev/tty' failed to run.
>> 
>> 
>> Take care,
>> 
>> Lucas Nussbaum  writes:
>> 
>> > On 28/09/16 at 12:40 -0400, Camm Maguire wrote:
>> >> Greetings, and thanks!  Not being the sbuild expert, my preliminary
>> >> attempts at getting a shell in the proper environment after the point of
>> >> failure are unsuccessful.  How is this done?
>> >> 
>> >> (failure goes away without the sbuild)
>> >
>> > Have you tried building inside the chroot using schroot?
>> >
>> > Lucas
>> >
>> >
>> >
>> >
>> >
>> >
>> 
>> -- 
>> Camm Maguire c...@maguirefamily.org
>> ==
>> "The earth is but one country, and mankind its citizens."  --  Baha'u'llah
>> 
>
>
>
>

-- 
Camm Maguirec...@maguirefamily.org
==
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah



Bug#831248: maxima: FTBFS: tests failures

2016-09-28 Thread Lucas Nussbaum
On 26/09/16 at 19:26 +, Camm Maguire wrote:
> tags 831248 unreproducible
> severity 831248 important
> thanks
> 
> Greetings!  I cannot reproduce this, but can imagine how this might be
> triggered.  Can you detail your setup, especially how much ram/swap was
> available at runtime?  Can I ssh into this environment?

Hi,

It's failing reproducibly here for some time. The nodes I used are
either EC2 m4.large (8 GB RAM) or m4.xlarge (16 GB RAM) instances. No
swap.

I can provide a machine where you could SSH to. Please send me your SSH
key.
 
Lucas



Bug#831248: maxima: FTBFS: tests failures

2016-09-26 Thread Camm Maguire
tags 831248 unreproducible
severity 831248 important
thanks

Greetings!  I cannot reproduce this, but can imagine how this might be
triggered.  Can you detail your setup, especially how much ram/swap was
available at runtime?  Can I ssh into this environment?

Take care,

Lucas Nussbaum  writes:

> Source: maxima
> Version: 5.38.0-3
> Severity: serious
> Tags: stretch sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20160714 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part (hopefully):
>> make[2]: Entering directory '/«PKGBUILDDIR»'
>> make[2]: Nothing to be done for 'all-am'.
>> make[2]: Leaving directory '/«PKGBUILDDIR»'
>> make[1]: Leaving directory '/«PKGBUILDDIR»'
>> echo ':lisp (setq maxima::*maxima-started* nil si::*optimize-maximum-pages* 
>> t si::*code-block-reserve* (make-array 1000 :element-type (quote 
>> character) :static t))(si::sgc-on nil)(si::gbc t)(si::save-system "foo")' | 
>> ./maxima-local && mv foo src/binary-gcl/maxima
>> Maxima 5.38.0 http://maxima.sourceforge.net
>> using Lisp GNU Common Lisp (GCL) GCL 2.6.12
>> Distributed under the GNU Public License. See the file COPYING.
>> Dedicated to the memory of William Schelter.
>> The function bug_report() provides bug reporting information.
>> (%i1) chmod +x ./maxima-local
>> touch tests/tests-gcl.log
>> ./maxima-local -g --lisp=gcl --batch-string="run_testsuite();"  >tmp 2>&1 & \
>>  j=$! ; echo Waiting on pid $j ; \
>>  tail -f --pid=$j --retry tests/tests-gcl.log tmp & wait $j
>> Waiting on pid 25726
>> tail: warning: --retry only effective for the initial open
>> ==> tests/tests-gcl.log <==
>> 
>> ==> tmp <==
>> 
>> Maxima 5.38.0 http://maxima.sourceforge.net
>> using Lisp GNU Common Lisp (GCL) GCL 2.6.12
>> Distributed under the GNU Public License. See the file COPYING.
>> Dedicated to the memory of William Schelter.
>> The function bug_report() provides bug reporting information.
>> (%i1) run_testsuite()
>> Running tests in rtest_rules: 103/103 tests passed
>> Running tests in rtestnset: 597/597 tests passed
>> Running tests in rtest1: 180/180 tests passed (not counting 1 expected 
>> errors)
>> Running tests in rtest1a: 27/27 tests passed
>> Running tests in rtest2: 144/144 tests passed (not counting 2 expected 
>> errors)
>> Running tests in rtest4: 93/93 tests passed
>> Running tests in rtest5: start address -T 0x28f2010 start address -T 
>> 0x2922ae0 start address -T 0x292a250 start address -T 0x292e730 start 
>> address -T 0x2932bb0 start address -T 0x293b6b0 start address -T 0x2940800 
>> start address -T 0x2944360 80/80 tests passed
>> Running tests in rtest6: 39/39 tests passed
>> Running tests in rtest6a: 62/62 tests passed
>> Running tests in rtest6b: 16/16 tests passed
>> Running tests in rtest7: 85/85 tests passed
>> Running tests in rtest9: 89/89 tests passed
>> Running tests in rtest9a: 76/76 tests passed
>> Running tests in rtest10: 62/62 tests passed (not counting 2 expected errors)
>> Running tests in rtest11: 181/181 tests passed
>> Running tests in rtest13: 23/23 tests passed
>> Running tests in rtest13s: 17/17 tests passed
>> Running tests in rtest14: 418/418 tests passed
>> Running tests in rtest15: 334/334 tests passed
>> Running tests in rtest16: 540/540 tests passed
>> Running tests in rtestode: 90/90 tests passed
>> Running tests in rtestode_zp: 30/30 tests passed
>> Running tests in rtest3: 149/149 tests passed
>> Running tests in rtest8: 
>> ** Problem 133 ***
>> Input:
>> (compile(foo17), first(quad_qags(foo17, u, - 1, 0)))
>> 
>> 
>> Result:
>> Compiling /tmp/gazonk_25726_0.lsp.
>> End of Pass 1.  
>> End of Pass 2.  
>> error-catch
>> 
>> This differed from the expected result:
>> - 0.359753467469551
>> 
>> 163/164 tests passed
>> 
>> The following 1 problem failed: (133)
>> Running tests in rtest12: 79/79 tests passed (not counting 2 expected errors)
>> Running tests in rexamples: 137/137 tests passed
>> Running tests in rtesthyp: 423/423 tests passed (not counting 6 expected 
>> errors)
>> Running tests in rtest_hypgeo: 291/291 tests passed (not counting 1 expected 
>> errors)
>> Running tests in rtestmt19937: 15/15 tests passed
>> Running tests in rtest_allnummod: 544/544 tests passed
>> Running tests in rtestconjugate: 136/136 tests passed
>> Running tests in rtestsum: 306/306 tests passed (not counting 4 expected 
>> errors)
>> Running tests in rtest_trig: 160/160 tests passed
>> Running tests in rtest_zeta: 22/22 tests passed
>> Running tests in rtest_diff_invtrig: 22/22 tests passed
>> Running tests in rtest_scalarp: 20/20 tests passed
>> Running tests in rtest_everysome: 84/84 tests passed
>> Running tests in rtestint: 287/287 tests passed
>> Running tests in rtest_numth: 201/201 tests passed
>> Running tests in rtestifactor: 25/25 tests passed
>> Running tests in rtest_equal: 207/207 tests passed (not counting 2 

Bug#831248: maxima: FTBFS: tests failures

2016-07-14 Thread Lucas Nussbaum
Source: maxima
Version: 5.38.0-3
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160714 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build on
amd64.

Relevant part (hopefully):
> make[2]: Entering directory '/«PKGBUILDDIR»'
> make[2]: Nothing to be done for 'all-am'.
> make[2]: Leaving directory '/«PKGBUILDDIR»'
> make[1]: Leaving directory '/«PKGBUILDDIR»'
> echo ':lisp (setq maxima::*maxima-started* nil si::*optimize-maximum-pages* t 
> si::*code-block-reserve* (make-array 1000 :element-type (quote character) 
> :static t))(si::sgc-on nil)(si::gbc t)(si::save-system "foo")' | 
> ./maxima-local && mv foo src/binary-gcl/maxima
> Maxima 5.38.0 http://maxima.sourceforge.net
> using Lisp GNU Common Lisp (GCL) GCL 2.6.12
> Distributed under the GNU Public License. See the file COPYING.
> Dedicated to the memory of William Schelter.
> The function bug_report() provides bug reporting information.
> (%i1) chmod +x ./maxima-local
> touch tests/tests-gcl.log
> ./maxima-local -g --lisp=gcl --batch-string="run_testsuite();"  >tmp 2>&1 & \
>   j=$! ; echo Waiting on pid $j ; \
>   tail -f --pid=$j --retry tests/tests-gcl.log tmp & wait $j
> Waiting on pid 25726
> tail: warning: --retry only effective for the initial open
> ==> tests/tests-gcl.log <==
> 
> ==> tmp <==
> 
> Maxima 5.38.0 http://maxima.sourceforge.net
> using Lisp GNU Common Lisp (GCL) GCL 2.6.12
> Distributed under the GNU Public License. See the file COPYING.
> Dedicated to the memory of William Schelter.
> The function bug_report() provides bug reporting information.
> (%i1) run_testsuite()
> Running tests in rtest_rules: 103/103 tests passed
> Running tests in rtestnset: 597/597 tests passed
> Running tests in rtest1: 180/180 tests passed (not counting 1 expected errors)
> Running tests in rtest1a: 27/27 tests passed
> Running tests in rtest2: 144/144 tests passed (not counting 2 expected errors)
> Running tests in rtest4: 93/93 tests passed
> Running tests in rtest5: start address -T 0x28f2010 start address -T 
> 0x2922ae0 start address -T 0x292a250 start address -T 0x292e730 start address 
> -T 0x2932bb0 start address -T 0x293b6b0 start address -T 0x2940800 start 
> address -T 0x2944360 80/80 tests passed
> Running tests in rtest6: 39/39 tests passed
> Running tests in rtest6a: 62/62 tests passed
> Running tests in rtest6b: 16/16 tests passed
> Running tests in rtest7: 85/85 tests passed
> Running tests in rtest9: 89/89 tests passed
> Running tests in rtest9a: 76/76 tests passed
> Running tests in rtest10: 62/62 tests passed (not counting 2 expected errors)
> Running tests in rtest11: 181/181 tests passed
> Running tests in rtest13: 23/23 tests passed
> Running tests in rtest13s: 17/17 tests passed
> Running tests in rtest14: 418/418 tests passed
> Running tests in rtest15: 334/334 tests passed
> Running tests in rtest16: 540/540 tests passed
> Running tests in rtestode: 90/90 tests passed
> Running tests in rtestode_zp: 30/30 tests passed
> Running tests in rtest3: 149/149 tests passed
> Running tests in rtest8: 
> ** Problem 133 ***
> Input:
> (compile(foo17), first(quad_qags(foo17, u, - 1, 0)))
> 
> 
> Result:
> Compiling /tmp/gazonk_25726_0.lsp.
> End of Pass 1.  
> End of Pass 2.  
> error-catch
> 
> This differed from the expected result:
> - 0.359753467469551
> 
> 163/164 tests passed
> 
> The following 1 problem failed: (133)
> Running tests in rtest12: 79/79 tests passed (not counting 2 expected errors)
> Running tests in rexamples: 137/137 tests passed
> Running tests in rtesthyp: 423/423 tests passed (not counting 6 expected 
> errors)
> Running tests in rtest_hypgeo: 291/291 tests passed (not counting 1 expected 
> errors)
> Running tests in rtestmt19937: 15/15 tests passed
> Running tests in rtest_allnummod: 544/544 tests passed
> Running tests in rtestconjugate: 136/136 tests passed
> Running tests in rtestsum: 306/306 tests passed (not counting 4 expected 
> errors)
> Running tests in rtest_trig: 160/160 tests passed
> Running tests in rtest_zeta: 22/22 tests passed
> Running tests in rtest_diff_invtrig: 22/22 tests passed
> Running tests in rtest_scalarp: 20/20 tests passed
> Running tests in rtest_everysome: 84/84 tests passed
> Running tests in rtestint: 287/287 tests passed
> Running tests in rtest_numth: 201/201 tests passed
> Running tests in rtestifactor: 25/25 tests passed
> Running tests in rtest_equal: 207/207 tests passed (not counting 2 expected 
> errors)
> Running tests in rtest_abs: 93/93 tests passed
> Running tests in rtest_taylor: 149/149 tests passed (not counting 8 expected 
> errors)
> Running tests in rtest_dot: 60/60 tests passed
> Running tests in rtest_mset: 92/92 tests passed
> Running tests in rtest_boolean: 116/116 tests passed
> Running tests in rtest_round: 101/101 tests passed
> Running tests in rtest_map: 99/99 tests passed (not counting 3 expected 
>