Re: running CI tests before package sponsorship
Hi Steve,
You can run the test suite yourself on your local machine with either
autopkgtest (using a chroot/schroot/pbuilder/vm/etc) or without isolation
using sadt from devscripts.
Running the tests yourself only tests against the hardware you have available
and so isn't probing different architectures, but then ci.debian.net doesn't
either.
It is possible to build and run tests from gitlab CI. You can write your own
code for that or see an existing project for it:
https://salsa.debian.org/salsa-ci-team/pipeline
(I'm not sure I like the way it has been implemented in that project but it's
an option for you)
Gitlab CI is still not probing many architectures.
Established maintainers can get access to porterboxes with various
architectures to do their own testing and debugging on different hardware. I
don't know whether that's going to be an option for you, however.
To the source of your problem -- what sort of comparisons are you having
trouble with? It's generally best that numerical tests use some sort of
"almost equals" test probing only an acceptable number of significant figures;
that should then pass on all architectures. Would it help to point to the
specific code at this stage?
Cheers
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stuart@nanonanonano.net
Debian Developer http://www.debian.org/ stuart@debian.org
GPG fingerprint 90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Reply to: