[Pdl-porters] Continuous integration and code coverage for GitHub

Hi,

definitely a good idea. I think it might be worth considering to enhance
"before_install:" section to also install external libraries like this:

before_install:
- sudo apt-get install libgsl libhdf libproj libwhatever

--
kmx

Post by Zakariyya Mughal
Hello everyone,
As I am about to continue my clean-up of the test code to use
Test::More, I thought it would be useful to add Travis-CI support to PDL
as well. And I did it!
I have set it up to run the tests on Perl versions 5.10, 5.12, 5.14,
5.16, 5.18, 5.20, and blead. Unfortunately, this is only on a Linux
system, but that itself is still useful. If the builds fail or if the
code coverage decreases, you will receive an alert.
===
Example of a build: <https://travis-ci.org/zmughal/p5-PDL/builds/49113227>
Example of code coverage: <https://coveralls.io/builds/1844232>
===
Patch: <https://github.com/zmughal/p5-PDL/compare/travis-ci>
All one has to do is add this patch and one of the PDLPorters org admins
on GitHub has to enable Travis-CI at <https://travis-ci.org/PDLPorters/pdl>
and Coveralls at <https://coveralls.io/repos/new>.
Cheers,
- Zaki Mughal
_______________________________________________
PDL-porters mailing list
http://mailman.jach.hawaii.edu/mailman/listinfo/pdl-porters

Zakariyya Mughal

2015-02-01 22:41:00 UTC

Post by kmx
Hi,
definitely a good idea. I think it might be worth considering to enhance
- sudo apt-get install libgsl libhdf libproj libwhatever

Thanks for the tip! I'm pushing a .travis.yml with all the deps I got
from

apt-get build-dep -s pdl

right now.

I also just found out that we could possibly use the OS X testing
environment, but it is a limited sign-up thing:
<http://blog.travis-ci.com/2014-05-13-multi-os-feature-available/>.

Cheers,
- Zaki Mughal

Post by kmx
--
kmx

_______________________________________________
PDL-porters mailing list
http://mailman.jach.hawaii.edu/mailman/listinfo/pdl-porters

Zakariyya Mughal

2015-02-01 23:25:04 UTC

Post by kmx
Hi,
definitely a good idea. I think it might be worth considering to enhance
- sudo apt-get install libgsl libhdf libproj libwhatever

Thanks for the tip! I'm pushing a .travis.yml with all the deps I got
from
apt-get build-dep -s pdl
right now.

And that worked! <https://travis-ci.org/zmughal/p5-PDL/builds/49123449>.

- Zaki Mughal

Post by Zakariyya Mughal
I also just found out that we could possibly use the OS X testing
<http://blog.travis-ci.com/2014-05-13-multi-os-feature-available/>.
Cheers,
- Zaki Mughal

Post by kmx
--
kmx

_______________________________________________
PDL-porters mailing list
http://mailman.jach.hawaii.edu/mailman/listinfo/pdl-porters

Joel Berger

2015-02-01 23:34:02 UTC

Yet another great reason to move to github!

Post by kmx
Hi,
definitely a good idea. I think it might be worth considering to

enhance

Post by kmx
- sudo apt-get install libgsl libhdf libproj libwhatever

Thanks for the tip! I'm pushing a .travis.yml with all the deps I got
from
apt-get build-dep -s pdl
right now.

And that worked! <https://travis-ci.org/zmughal/p5-PDL/builds/49123449>.
- Zaki Mughal

Post by Zakariyya Mughal
I also just found out that we could possibly use the OS X testing
<http://blog.travis-ci.com/2014-05-13-multi-os-feature-available/>.
Cheers,
- Zaki Mughal

Post by kmx
--
kmx

Post by Zakariyya Mughal
Hello everyone,
As I am about to continue my clean-up of the test code to use
Test::More, I thought it would be useful to add Travis-CI support to

PDL

Post by Zakariyya Mughal
as well. And I did it!
I have set it up to run the tests on Perl versions 5.10, 5.12, 5.14,
5.16, 5.18, 5.20, and blead. Unfortunately, this is only on a Linux
system, but that itself is still useful. If the builds fail or if the
code coverage decreases, you will receive an alert.
===
Example of a build: <

https://travis-ci.org/zmughal/p5-PDL/builds/49113227>

Post by Zakariyya Mughal
Example of code coverage: <https://coveralls.io/builds/1844232>
===
Patch: <https://github.com/zmughal/p5-PDL/compare/travis-ci>
All one has to do is add this patch and one of the PDLPorters org

admins

Post by Zakariyya Mughal
on GitHub has to enable Travis-CI at <

https://travis-ci.org/PDLPorters/pdl>

Post by Zakariyya Mughal
and Coveralls at <https://coveralls.io/repos/new>.
Cheers,
- Zaki Mughal
_______________________________________________
PDL-porters mailing list
http://mailman.jach.hawaii.edu/mailman/listinfo/pdl-porters

_______________________________________________
PDL-porters mailing list
http://mailman.jach.hawaii.edu/mailman/listinfo/pdl-porters

Zakariyya Mughal

2015-02-05 04:21:59 UTC

Hi again!

I have also added the ability to test PDL builds on Travis-CI with the
bad value support disabled. This is has brought up some tests that might
need to be addressed as can be seen in build #28.8
<https://travis-ci.org/zmughal/p5-PDL/builds/49551418>.

Regards,
- Zaki Mughal

Chris Marshall

2015-02-05 20:30:28 UTC

I took a look at the build logs and it is weird in that the logs didn't
include the full output from the tests. Is that something with the
travis-ci configuration?

How difficult is it to add conditions for testing? It would be very
useful to exercise the possible combinations of:

WITH_BADVAL 0|1
BADVAL_USENAN 0|1
BADVAL_PER_PDL 0|1

And thanks for setting this up. --Chris

Post by Zakariyya Mughal
Hi again!
I have also added the ability to test PDL builds on Travis-CI with the
bad value support disabled. This is has brought up some tests that might
need to be addressed as can be seen in build #28.8
<https://travis-ci.org/zmughal/p5-PDL/builds/49551418>.
Regards,
- Zaki Mughal

https://travis-ci.org/zmughal/p5-PDL/builds/49113227>

https://travis-ci.org/PDLPorters/pdl>

Post by Zakariyya Mughal
and Coveralls at <https://coveralls.io/repos/new>.
Cheers,
- Zaki Mughal

_______________________________________________
PDL-porters mailing list
http://mailman.jach.hawaii.edu/mailman/listinfo/pdl-porters

Zakariyya Mughal

2015-02-05 20:41:25 UTC

Post by Chris Marshall
I took a look at the build logs and it is weird in that the logs didn't
include the full output from the tests. Is that something with the
travis-ci configuration?

To get all the test output, I think I can pass in -v to the TAP harness.
I'll test that in a bit.

By the way, one of the things I'm working on in cleaning up the tests is
to change all the print() statements to use `note()` and `diag()` so
that it will be easier to parse the output automatically.

Post by Chris Marshall
How difficult is it to add conditions for testing? It would be very
WITH_BADVAL 0|1
BADVAL_USENAN 0|1
BADVAL_PER_PDL 0|1

Not very difficult at all. I believe can get that done in the next few
minutes.

Post by Chris Marshall
And thanks for setting this up. --Chris

No problem. I'd still like Windows and OS X testing, but we can't have
everything (yet!).

- Zaki Mughal

https://travis-ci.org/zmughal/p5-PDL/builds/49113227>

https://travis-ci.org/PDLPorters/pdl>

Post by Zakariyya Mughal
and Coveralls at <https://coveralls.io/repos/new>.
Cheers,
- Zaki Mughal

_______________________________________________
PDL-porters mailing list
http://mailman.jach.hawaii.edu/mailman/listinfo/pdl-porters

Zakariyya Mughal

2015-02-06 01:04:02 UTC

Post by Chris Marshall
I took a look at the build logs and it is weird in that the logs didn't
include the full output from the tests. Is that something with the
travis-ci configuration?

To get all the test output, I think I can pass in -v to the TAP harness.
I'll test that in a bit.
By the way, one of the things I'm working on in cleaning up the tests is
to change all the print() statements to use `note()` and `diag()` so
that it will be easier to parse the output automatically.

Post by Chris Marshall
How difficult is it to add conditions for testing? It would be very
WITH_BADVAL 0|1
BADVAL_USENAN 0|1
BADVAL_PER_PDL 0|1

Not very difficult at all. I believe can get that done in the next few
minutes.

OK, done! Build 39 is working with all the BADVAL compilation options
and verbose output <https://travis-ci.org/zmughal/p5-PDL/builds/49684685>

I had to use the flag `--formatter TAP::Formatter::File` to get verbose
output (`-v)` to work with parallel testing (`-j $N`). I got stuck figuring
that out and was going to use the archive feature and
<https://metacpan.org/pod/Archive::TAP::Convert>.

Regards,
- Zaki Mughal

Post by Chris Marshall
And thanks for setting this up. --Chris

No problem. I'd still like Windows and OS X testing, but we can't have
everything (yet!).
- Zaki Mughal

https://travis-ci.org/zmughal/p5-PDL/builds/49113227>

https://travis-ci.org/PDLPorters/pdl>

Post by Zakariyya Mughal
and Coveralls at <https://coveralls.io/repos/new>.
Cheers,
- Zaki Mughal

_______________________________________________
PDL-porters mailing list
http://mailman.jach.hawaii.edu/mailman/listinfo/pdl-porters

Chris Marshall

2015-02-06 11:52:42 UTC

Nice, and thanks!

It appears that something is up with t/pdl_from_string.t not
being able to find at() which is odd since it works when
bad values are enabled.

Also, is it mandatory to have parallel testing? It makes
it difficult to look at the output with all the tests
coming in the log out of order.

--Chris

Post by Chris Marshall
I took a look at the build logs and it is weird in that the logs didn't
include the full output from the tests. Is that something with the
travis-ci configuration?

To get all the test output, I think I can pass in -v to the TAP harness.
I'll test that in a bit.
By the way, one of the things I'm working on in cleaning up the tests is
to change all the print() statements to use `note()` and `diag()` so
that it will be easier to parse the output automatically.

Post by Chris Marshall
How difficult is it to add conditions for testing? It would be very
WITH_BADVAL 0|1
BADVAL_USENAN 0|1
BADVAL_PER_PDL 0|1

Not very difficult at all. I believe can get that done in the next few
minutes.

OK, done! Build 39 is working with all the BADVAL compilation options
and verbose output <https://travis-ci.org/zmughal/p5-PDL/builds/49684685>
I had to use the flag `--formatter TAP::Formatter::File` to get verbose
output (`-v)` to work with parallel testing (`-j $N`). I got stuck figuring
that out and was going to use the archive feature and
<https://metacpan.org/pod/Archive::TAP::Convert>.
Regards,
- Zaki Mughal

Post by Chris Marshall
And thanks for setting this up. --Chris

No problem. I'd still like Windows and OS X testing, but we can't have
everything (yet!).
- Zaki Mughal

https://travis-ci.org/zmughal/p5-PDL/builds/49113227>

https://travis-ci.org/PDLPorters/pdl>

Post by Zakariyya Mughal
and Coveralls at <https://coveralls.io/repos/new>.
Cheers,
- Zaki Mughal

_______________________________________________
PDL-porters mailing list
http://mailman.jach.hawaii.edu/mailman/listinfo/pdl-porters

Zakariyya Mughal

2015-02-07 06:20:21 UTC

Post by Chris Marshall
Nice, and thanks!
It appears that something is up with t/pdl_from_string.t not
being able to find at() which is odd since it works when
bad values are enabled.
Also, is it mandatory to have parallel testing? It makes
it difficult to look at the output with all the tests
coming in the log out of order.

No, it isn't mandatory. I've changed the `.travis.yml` file to run
things serially <https://travis-ci.org/zmughal/p5-PDL/builds/49775446>.

Regards,
- Zaki Mughal

Post by Chris Marshall
--Chris

Post by Chris Marshall
I took a look at the build logs and it is weird in that the logs didn't
include the full output from the tests. Is that something with the
travis-ci configuration?

To get all the test output, I think I can pass in -v to the TAP harness.
I'll test that in a bit.
By the way, one of the things I'm working on in cleaning up the tests is
to change all the print() statements to use `note()` and `diag()` so
that it will be easier to parse the output automatically.

Post by Chris Marshall
How difficult is it to add conditions for testing? It would be very
WITH_BADVAL 0|1
BADVAL_USENAN 0|1
BADVAL_PER_PDL 0|1

Not very difficult at all. I believe can get that done in the next few
minutes.

OK, done! Build 39 is working with all the BADVAL compilation options
and verbose output <https://travis-ci.org/zmughal/p5-PDL/builds/49684685>
I had to use the flag `--formatter TAP::Formatter::File` to get verbose
output (`-v)` to work with parallel testing (`-j $N`). I got stuck figuring
that out and was going to use the archive feature and
<https://metacpan.org/pod/Archive::TAP::Convert>.
Regards,
- Zaki Mughal

Post by Chris Marshall
And thanks for setting this up. --Chris

No problem. I'd still like Windows and OS X testing, but we can't have
everything (yet!).
- Zaki Mughal