Re: continuous testing

As long as I'm trying to follow topics, related to continuous testing with github actions, I always see ubuntu-based scenarios. What about macOS and Windows? Do we have rakudo images for these? Best regards, Vadim Belman > On Jan 1, 2022, at 5:14 AM, JJ Merelo wrote: > > Try the new GitHub a

Re: continuous testing

Hi, El sáb, 1 ene 2022 a las 12:44, Richard Hainsworth () escribió: > JJ > Thanks. That is very useful. One interesting question. > > I notice from this setup that you chart the COMMITS, and the raku program > uses 'say' to output the results. > That's not really needed, it's just a bit of goldp

Re: continuous testing

JJ Thanks. That is very useful. One interesting question. I notice from this setup that you chart the COMMITS, and the raku program uses 'say' to output the results. But how do you access these charted results? Regards, Richard On 01/01/2022 10:14, JJ Merelo wrote: Try the new GitHub action

Re: continuous testing

Try the new GitHub actions with the recently renovated Docker image. See it in action, for instance, here: https://github.com/JJ/p6-pod-load/blob/master/.github/workflows/test.yaml El vie, 31 dic 2021 a las 19:57, Richard Hainsworth () escribió: > Thanks > On 31/12/2021 18:27, Fernando Santagata

Re: continuous testing

Thanks On 31/12/2021 18:27, Fernando Santagata wrote: Hi Richard, this is a link to the GitHub official documentation: https://docs.github.com/en/actions You can also copy a configuration from another project and adapt it to your needs. For example this on

Re: continuous testing

Hi Richard, this is a link to the GitHub official documentation: https://docs.github.com/en/actions You can also copy a configuration from another project and adapt it to your needs. For example this one installs some C libraries, some module dependencies and runs the tests: https://github.com/f

Re: continuous testing

Fernando, Thanks. Any link / blog / article about how to set up GitHub action up for Raku? Regards, Richard On 31/12/2021 16:52, Fernando Santagata wrote: Hi Richard, apparently Travis CI has discontinued its free open source plan. I switched to GitHub actions; don't know what's available on

Re: continuous testing

Hi Richard, apparently Travis CI has discontinued its free open source plan. I switched to GitHub actions; don't know what's available on other platforms. On Fri, Dec 31, 2021 at 5:43 PM Richard Hainsworth wrote: > I noticed that the .travis files have been removed from some distributions. > > A

Re: Continuous testing

Maybe not the proper thread, ... but may be nice to know or even helpful ... Using native integers I did not know which integer to choose when a C type int was specified in a function signature. It is known that, depending on processor or compiler, an int could have 16 or 32 bits size and a lo

Re: Continuous testing

On 12/23/20 7:45 PM, JJ Merelo wrote: You can probably use AppVeyor. It's got good support for Windows, although you'll have to write for it specifically. This one seems to use it, for instance https://github.com/MARTIMM/gnome-native Hi Richard, JJ i

Re: Continuous testing

You can probably use AppVeyor. It's got good support for Windows, although you'll have to write for it specifically. This one seems to use it, for instance https://github.com/MARTIMM/gnome-native El mié, 23 dic 2020 a las 16:35, Richard Hainsworth () escribió: > Hi to everyone. > > Hope you all h

Re: Continuous testing tools

On 6/9/06, Adam Kennedy <[EMAIL PROTECTED]> wrote: http://ali.as/pita.html The above gave a 404, but http://ali.as/pita/ worked.

Re: Continuous testing tools

Michael G Schwern wrote: On 6/9/06, A. Pagaltzis <[EMAIL PROTECTED]> wrote: * Adam Kennedy <[EMAIL PROTECTED]> [2006-06-09 18:35]: > Sorry for the lack of information, but PITA's design is fairly > ambitious, Hmm, I just saw this: http://googleresearch.blogspot.com/2006/04/our-conference-on-

Re: Continuous testing tools

On 6/9/06, A. Pagaltzis <[EMAIL PROTECTED]> wrote: * Adam Kennedy <[EMAIL PROTECTED]> [2006-06-09 18:35]: > Sorry for the lack of information, but PITA's design is fairly > ambitious, Hmm, I just saw this: http://googleresearch.blogspot.com/2006/04/our-conference-on-automated-testing.html Th

Re: Continuous testing tools

* Adam Kennedy <[EMAIL PROTECTED]> [2006-06-09 18:35]: > Sorry for the lack of information, but PITA's design is fairly > ambitious, Hmm, I just saw this: http://googleresearch.blogspot.com/2006/04/our-conference-on-automated-testing.html The submission deadline has already passed, but I figure

Re: Continuous testing tools

--- Adam Kennedy wrote: > I know it's somewhat vapour at the moment, and I'm keeping somewhat > quiet, but the new post-Audrey'fied PITA design is aiming at exactly > what you have described. Thanks for the reminder about PITA. I'd (unforgivably) forgotten about that project when I first enquire

Re: Continuous testing tools

Hi Andrew I know it's somewhat vapour at the moment, and I'm keeping somewhat quiet, but the new post-Audrey'fied PITA design is aiming at exactly what you have described. Initial deployment targets include a pugs smoker, parrot smoker, and CPAN Testers 2. Of course, I have no idea how you

Re: Continuous testing tools

Sorry for the lack of information, but PITA's design is fairly ambitious, and until the core testing loop is completed, absolutely every other part of it would block waiting for me to finish. So I've kept things mostly under wraps. With the core almost done (we've had to scrap a major componen

Re: Continuous testing tools

Nik Clayton wrote: > Geoffrey Young wrote: > >>> Since you're using C++, you can probably use libtap >>> (http://www.onlamp.com/pub/a/onlamp/2006/01/19/libtap.html and >>> http://jc.ngo.org.uk/trac-bin/trac.cgi/wiki/LibTap) for writing the >>> tests and >>> then you could use a Perl harnes to coll

Re: Continuous testing tools

Geoffrey Young wrote: Since you're using C++, you can probably use libtap (http://www.onlamp.com/pub/a/onlamp/2006/01/19/libtap.html and http://jc.ngo.org.uk/trac-bin/trac.cgi/wiki/LibTap) for writing the tests and then you could use a Perl harnes to collect those results. just out of curiosity

Re: Continuous testing tools

Moin, On Thursday 08 June 2006 18:10, Chris Dolan wrote: > On Jun 8, 2006, at 10:39 AM, Tels wrote: > > On my todo (well, wish list) is still a project that works rouhgly > > like a > > server/client model. > > > > You upload a snapshot to the server, it notifies the clients, they > > download the

Re: Continuous testing tools

On Jun 8, 2006, at 10:39 AM, Tels wrote: On my todo (well, wish list) is still a project that works rouhgly like a server/client model. You upload a snapshot to the server, it notifies the clients, they download the package, run the tests and report the result back. Reports are viewed on t

Re: Continuous testing tools

Moin, On Thursday 08 June 2006 15:11, Michael Peters wrote: > Andrew Savige wrote: > > We are looking at introducing continuous builds/smoke tests at > > work across a number of platforms (mainly Windows and Unix), > > building a number of different languages (mainly C++). > > > > I quick google u

Re: Continuous testing tools

> Since you're using C++, you can probably use libtap > (http://www.onlamp.com/pub/a/onlamp/2006/01/19/libtap.html and > http://jc.ngo.org.uk/trac-bin/trac.cgi/wiki/LibTap) for writing the tests and > then you could use a Perl harnes to collect those results. just out of curiosity, has anyone got

Re: Continuous testing tools

Andrew Savige wrote: > We are looking at introducing continuous builds/smoke tests at > work across a number of platforms (mainly Windows and Unix), > building a number of different languages (mainly C++). > > I quick google uncovered the list below. > > Anyone got any advice? I would advise k