On Wed, Sep 5, 2012 at 1:58 PM, Gary Dunn <[hidden email]> wrote:
> On Wed, Sep 5, 2012 at 12:38 AM, Frank Shearar <[hidden email]> wrote: >> On 5 September 2012 05:29, Herbert König <[hidden email]> wrote: >>> Hi Gary, >>> >>> Am 04.09.2012 23:59, schrieb Gary Dunn: >>> >>>> Happy to test on FreeBSD. Just set up a box with 9.1 RC1 and Enlightenment >>>> WM without Gnome. Just got Squeak working a few minutes ago, in fact. Where >>>> do I get a test image? And how do I execute the test suit? I know I did this >>>> a few years back ... old age, you know, can't recall any details. >>> >>> >>> First step: >>> download the Squeak all in one from Squeak site. From the top menu bar >>> choose "Apps" "Preference browser". In the search field write "update" and >>> change the last part of the "Update Url" from "Squeak..." to trunk. >>> >>> World Menu, "Help", "Update code from Server", have a cup of tea. Remember >>> to punch the necessary holes into the firewall so squeak can act as a >>> server, can't help with this. >> >> Please rather test the image that the CI builds: >> http://squeakci.org/job/UpdateFromLastRelease/lastSuccessfulBuild/artifact/*zip*/archive.zip >> This is a clean, no-tests-yet-run, fully up-to-date image, so you (-) >> don't have time for a cup of tea but (+) also test the precise image >> that the build server tests. >> >> frank > > Downloaded the zip, unpacked with file-roller, moved image and changes > to my images folder, ran the image, ran the tests. Took a really long > time for anything to start, I thought it hung. Results: > > 3221 run, 3162 passes, 19 expected failures, 12 failures, 26 errors, 2 > unexpected passes > > Tried the "Run failures" button, that really did hand the process, had > to kill the window. > > How do I report in more detail what the errors were? > > For the record: FreeBSD 9.1 RC1 on a Dell Optiplex 745 > > xorg-7.5.2 > enlightenment-0.16.999.65643,2 > > $ squeak -version > 4.4.7-2375 #1 XShm Wed Mar 30 16:50:13 PDT 2011 gcc 4.2.1 > FreeBSD freebsd.piumarta.com 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri > Feb 18 02:24:46 UTC 2011 > [hidden email]:/usr/obj/usr/src/sys/GENERIC i386 > plugin path: /usr/local/lib/squeak/4.4.7-2375 [default: > /usr/local/lib/squeak/4.4.7-2375/] > > -- > Gary Dunn > Honolulu Still waiting for an answer, how do I report test results? And a new question: Does the image Frank asked us to use change daily? How often should I test it? -- Gary Dunn Honolulu |
On 7 September 2012 19:28, Gary Dunn <[hidden email]> wrote:
> On Wed, Sep 5, 2012 at 1:58 PM, Gary Dunn <[hidden email]> wrote: >> On Wed, Sep 5, 2012 at 12:38 AM, Frank Shearar <[hidden email]> wrote: >>> On 5 September 2012 05:29, Herbert König <[hidden email]> wrote: >>>> Hi Gary, >>>> >>>> Am 04.09.2012 23:59, schrieb Gary Dunn: >>>> >>>>> Happy to test on FreeBSD. Just set up a box with 9.1 RC1 and Enlightenment >>>>> WM without Gnome. Just got Squeak working a few minutes ago, in fact. Where >>>>> do I get a test image? And how do I execute the test suit? I know I did this >>>>> a few years back ... old age, you know, can't recall any details. >>>> >>>> >>>> First step: >>>> download the Squeak all in one from Squeak site. From the top menu bar >>>> choose "Apps" "Preference browser". In the search field write "update" and >>>> change the last part of the "Update Url" from "Squeak..." to trunk. >>>> >>>> World Menu, "Help", "Update code from Server", have a cup of tea. Remember >>>> to punch the necessary holes into the firewall so squeak can act as a >>>> server, can't help with this. >>> >>> Please rather test the image that the CI builds: >>> http://squeakci.org/job/UpdateFromLastRelease/lastSuccessfulBuild/artifact/*zip*/archive.zip >>> This is a clean, no-tests-yet-run, fully up-to-date image, so you (-) >>> don't have time for a cup of tea but (+) also test the precise image >>> that the build server tests. >>> >>> frank >> >> Downloaded the zip, unpacked with file-roller, moved image and changes >> to my images folder, ran the image, ran the tests. Took a really long >> time for anything to start, I thought it hung. Results: >> >> 3221 run, 3162 passes, 19 expected failures, 12 failures, 26 errors, 2 >> unexpected passes >> >> Tried the "Run failures" button, that really did hand the process, had >> to kill the window. >> >> How do I report in more detail what the errors were? >> >> For the record: FreeBSD 9.1 RC1 on a Dell Optiplex 745 >> >> xorg-7.5.2 >> enlightenment-0.16.999.65643,2 >> >> $ squeak -version >> 4.4.7-2375 #1 XShm Wed Mar 30 16:50:13 PDT 2011 gcc 4.2.1 >> FreeBSD freebsd.piumarta.com 8.2-RELEASE FreeBSD 8.2-RELEASE #0: Fri >> Feb 18 02:24:46 UTC 2011 >> [hidden email]:/usr/obj/usr/src/sys/GENERIC i386 >> plugin path: /usr/local/lib/squeak/4.4.7-2375 [default: >> /usr/local/lib/squeak/4.4.7-2375/] >> >> -- >> Gary Dunn >> Honolulu > > Still waiting for an answer, how do I report test results? I was hoping someone else would have a suggestion. If you run the tests via the scripts they'll spit out Jenkins/Hudson XML files. They're annoying to read in that form, but it's better than nothing at all. > And a new question: Does the image Frank asked us to use change daily? > How often should I test it? At present I have to trigger the build manually. I usually run them as soon as I see trunk commits. Maybe I should start replying to those as soon as I've run the build, and then you and the other volunteers know when to grab a new image? frank > -- > Gary Dunn > Honolulu > |
On Fri, Sep 7, 2012 at 9:02 AM, Frank Shearar <[hidden email]> wrote:
> On 7 September 2012 19:28, Gary Dunn <[hidden email]> wrote: [snip] >> Still waiting for an answer, how do I report test results? > > I was hoping someone else would have a suggestion. If you run the > tests via the scripts they'll spit out Jenkins/Hudson XML files. > They're annoying to read in that form, but it's better than nothing at > all. > >> And a new question: Does the image Frank asked us to use change daily? >> How often should I test it? > > At present I have to trigger the build manually. I usually run them as > soon as I see trunk commits. Maybe I should start replying to those as > soon as I've run the build, and then you and the other volunteers know > when to grab a new image? > > frank > >> -- >> Gary Dunn >> Honolulu Sorry to sound like a newbie but what scripts and where do I send the whatchmacallit files? -- Gary Dunn Honolulu |
On 7 September 2012 21:11, Gary Dunn <[hidden email]> wrote:
> On Fri, Sep 7, 2012 at 9:02 AM, Frank Shearar <[hidden email]> wrote: >> On 7 September 2012 19:28, Gary Dunn <[hidden email]> wrote: > > [snip] > >>> Still waiting for an answer, how do I report test results? >> >> I was hoping someone else would have a suggestion. If you run the >> tests via the scripts they'll spit out Jenkins/Hudson XML files. >> They're annoying to read in that form, but it's better than nothing at >> all. >> >>> And a new question: Does the image Frank asked us to use change daily? >>> How often should I test it? >> >> At present I have to trigger the build manually. I usually run them as >> soon as I see trunk commits. Maybe I should start replying to those as >> soon as I've run the build, and then you and the other volunteers know >> when to grab a new image? >> >> frank >> >>> -- >>> Gary Dunn >>> Honolulu > > Sorry to sound like a newbie but what scripts and where do I send the > whatchmacallit files? Sorry Gary, I think I confused your setup with someone else's. The scripts I referred to are from https://github.com/frankshearar/squeak-ci/ (which also includes several VMs, but NOT a FreeBSD one); they take a base image, update it, run some tests, and spit out some XML describing the test failures. I don't really mind how I get the test failures. If you don't mind extracting the juice out of the XML, dropping the list a mail would be worthwhile. Otherwise, you could always mail them directly to me, if you'd like to avoid spamming everyone on the list with numerous attachments. frank |
Free forum by Nabble | Edit this page |