http://www.squeakci.org/job/SqueakTrunk/19/testReport/?
That's a fully up-to-date trunk passing most of its tests.
The update-from-4.3 test also passes most of its tests:
http://www.squeakci.org/job/UpdateFromLastRelease/3/testReport/
Next is to show well-known packages (and mine, just because I'm in control of them) loading into a tested image and running their suites.
frank
On 8/3/12, Frank Shearar frank.shearar@gmail.com wrote:
http://www.squeakci.org/job/SqueakTrunk/19/testReport/?
That's a fully up-to-date trunk passing most of its tests.
The update-from-4.3 test also passes most of its tests:
http://www.squeakci.org/job/UpdateFromLastRelease/3/testReport/
Next is to show well-known packages (and mine, just because I'm in control of them) loading into a tested image and running their suites.
Will this list include http://www.squeaksource.com/Xtreams/ ?
--Hannes
frank
On 11 August 2012 11:39, H. Hirzel hannes.hirzel@gmail.com wrote:
On 8/3/12, Frank Shearar frank.shearar@gmail.com wrote:
http://www.squeakci.org/job/SqueakTrunk/19/testReport/?
That's a fully up-to-date trunk passing most of its tests.
The update-from-4.3 test also passes most of its tests:
http://www.squeakci.org/job/UpdateFromLastRelease/3/testReport/
Next is to show well-known packages (and mine, just because I'm in control of them) loading into a tested image and running their suites.
Will this list include http://www.squeaksource.com/Xtreams/ ?
Absolutely!
frank
--Hannes
frank
On 11 August 2012 12:14, Frank Shearar frank.shearar@gmail.com wrote:
On 11 August 2012 11:39, H. Hirzel hannes.hirzel@gmail.com wrote:
On 8/3/12, Frank Shearar frank.shearar@gmail.com wrote:
http://www.squeakci.org/job/SqueakTrunk/19/testReport/?
That's a fully up-to-date trunk passing most of its tests.
The update-from-4.3 test also passes most of its tests:
http://www.squeakci.org/job/UpdateFromLastRelease/3/testReport/
Next is to show well-known packages (and mine, just because I'm in control of them) loading into a tested image and running their suites.
Will this list include http://www.squeaksource.com/Xtreams/ ?
Absolutely!
I should add: my CI todo list is here - http://wiki.squeak.org/squeak/6188 - and please feel free to extend the todo list as appropriate.
frank
frank
--Hannes
frank
Frank Shearar-3 wrote
I should add: my CI todo list is here -
1. "After updating the image, print out the version number..." One thing I've found very useful on Pharo's Jenkins is that the latest update is put in the build description, so you can see exactly which version you're getting (pic attached to Nabble post): http://forum.world.st/file/n4643842/Screen_Shot_2012-08-11_at_9.29.09_AM.png
This is provided by a plugin (https://wiki.jenkins-ci.org/display/JENKINS/Description+Setter+Plugin). You output a line from the build script (e.g. "[version] #11860) and then the plugin picks it up with a regex like "[version] (.*)": http://forum.world.st/file/n4643842/Screen_Shot_2012-08-11_at_9.23.12_AM.png
2. "progress printing to stdout". One thing to note - Jenkins only shows full lines in the console log. I was trying to output "..............." incrementally to signify download progress, but none of the $. showed up until the newline was issued (https://issues.jenkins-ci.org/browse/JENKINS-14435)
-- View this message in context: http://forum.world.st/CI-ftw-tp4642910p4643842.html Sent from the Squeak - Dev mailing list archive at Nabble.com.
On Sat, Aug 11, 2012 at 06:33:41AM -0700, Sean P. DeNigris wrote:
Frank Shearar-3 wrote
I should add: my CI todo list is here -
- "After updating the image, print out the version number..."
One thing I've found very useful on Pharo's Jenkins is that the latest update is put in the build description, so you can see exactly which version you're getting (pic attached to Nabble post): http://forum.world.st/file/n4643842/Screen_Shot_2012-08-11_at_9.29.09_AM.png
This is provided by a plugin (https://wiki.jenkins-ci.org/display/JENKINS/Description+Setter+Plugin). You output a line from the build script (e.g. "[version] #11860) and then the plugin picks it up with a regex like "[version] (.*)": http://forum.world.st/file/n4643842/Screen_Shot_2012-08-11_at_9.23.12_AM.png
- "progress printing to stdout". One thing to note - Jenkins only shows
full lines in the console log. I was trying to output "..............." incrementally to signify download progress, but none of the $. showed up until the newline was issued (https://issues.jenkins-ci.org/browse/JENKINS-14435)
You need to flush the output after writing each character in order to get progress printing like this "..............."
Like this:
20 timesRepeat: [ FileStream stdout nextPut: $. ; flush. (Delay forMilliseconds: 400) wait]
Dave
David T. Lewis wrote
You need to flush the output after writing each character in order to get progress printing like this "..............."
IIRC it still didn't show up in the log. The output was in the log file, just not picked up by Jenkins.
-- View this message in context: http://forum.world.st/CI-ftw-tp4642910p4643848.html Sent from the Squeak - Dev mailing list archive at Nabble.com.
Frank,
May I ask you to add PetitParser in addition please?
It loads fine into Squeak 4.3 all-in one with your http://www.squeaksource.com/PharoCompatibility added
and after manual loading of Metacello.
I tested ConfigurationOfPetitParser loadMinimal
No GUI. It would be nice to have the GUI as well but I do not know if it has been ported to Squeak.
For Cuis it has been done https://github.com/pmon/Cuis-PetitParser
--Hannes
On 8/11/12, Sean P. DeNigris sean@clipperadams.com wrote:
David T. Lewis wrote
You need to flush the output after writing each character in order to get progress printing like this "..............."
IIRC it still didn't show up in the log. The output was in the log file, just not picked up by Jenkins.
-- View this message in context: http://forum.world.st/CI-ftw-tp4642910p4643848.html Sent from the Squeak - Dev mailing list archive at Nabble.com.
On 25 August 2012 15:22, H. Hirzel hannes.hirzel@gmail.com wrote:
Frank,
May I ask you to add PetitParser in addition please?
Absolutely!
Dale Henrichs and I are busy fighting with some other CI stuff at the moment, at https://github.com/dalehenrichs/builderCI. In particular, we're battling with single-source packages (packages whose ConfigurationOf specs only contain a single source repository). I'm trying to figure out an easy way to pull resource location out of Metacello, such that one can say "these are the places where you should look for any missing packages".
It loads fine into Squeak 4.3 all-in one with your http://www.squeaksource.com/PharoCompatibility added
and after manual loading of Metacello.
I tested ConfigurationOfPetitParser loadMinimal
OK, that's great. (And I'm happy to see other people finding my hacks useful!)
I'm aiming to, at some point in the very near future, implement some kind of minimal CI infrastructure that could take a ConfigurationOf and run its tests. I was hoping builderCI could do it, but it's quite a complicated beast.
No GUI. It would be nice to have the GUI as well but I do not know if it has been ported to Squeak.
There's a GUI for PetitParser? I guess it must be OmniBrowser hook-ins or something?
For Cuis it has been done https://github.com/pmon/Cuis-PetitParser
Hm, interesting. Those *.pck files look like chunk format, or very near to. Either way, I'm glad to see other folk jumping on the git bandwagon. (Tim Felgentreff's Gitocello provides a very nice/minimal git wrapper using FFI.)
frank
--Hannes
On 8/11/12, Sean P. DeNigris sean@clipperadams.com wrote:
David T. Lewis wrote
You need to flush the output after writing each character in order to get progress printing like this "..............."
IIRC it still didn't show up in the log. The output was in the log file, just not picked up by Jenkins.
-- View this message in context: http://forum.world.st/CI-ftw-tp4642910p4643848.html Sent from the Squeak - Dev mailing list archive at Nabble.com.
----- Original Message ----- | From: "Frank Shearar" frank.shearar@gmail.com | | I'm aiming to, at some point in the very near future, implement some | kind of minimal CI infrastructure that could take a ConfigurationOf | and run its tests. I was hoping builderCI could do it, but it's quite | a complicated beast.
Frank,
I think the interesting bit in builderCI that you're looking for to construct the test suite is probably this chunk of code that leverages the Metacello scripting api:
| suite configurationClassNameList | configurationClassNameList := #( "list of configuration classes" ). suite := TestCase suiteClass named: configurationClassNameList printString, ' Test Suite'. configurationClassNameList do: [ :className | ((MetacelloProjectRegistration registrationForClassNamed: className ifAbsent: [ self error: className printString , ' not registered (loaded)' ]) currentlyLoadedClassesInProject select: [ :cl | cl inheritsFrom: TestCase ]) do: [ :cl | cl isAbstract ifFalse: [ suite addTest: cl buildSuiteFromSelectors ] ] ].
Dale
As a reminder (for myself or somebody else..) by reactivating this thread:
PetitParser needs to be retested if it loads fine in Squeak 4.4...
--Hannes
On 8/31/12, Dale Henrichs dhenrich@vmware.com wrote:
----- Original Message ----- | From: "Frank Shearar" frank.shearar@gmail.com | | I'm aiming to, at some point in the very near future, implement some | kind of minimal CI infrastructure that could take a ConfigurationOf | and run its tests. I was hoping builderCI could do it, but it's quite | a complicated beast.
Frank,
I think the interesting bit in builderCI that you're looking for to construct the test suite is probably this chunk of code that leverages the Metacello scripting api:
| suite configurationClassNameList | configurationClassNameList := #( "list of configuration classes" ). suite := TestCase suiteClass named: configurationClassNameList printString, ' Test Suite'. configurationClassNameList do: [ :className | ((MetacelloProjectRegistration registrationForClassNamed: className ifAbsent: [ self error: className printString , ' not registered (loaded)' ]) currentlyLoadedClassesInProject select: [ :cl | cl inheritsFrom: TestCase ]) do: [ :cl | cl isAbstract ifFalse: [ suite addTest: cl buildSuiteFromSelectors ] ] ].
Dale
On 21 November 2012 21:20, H. Hirzel hannes.hirzel@gmail.com wrote:
As a reminder (for myself or somebody else..) by reactivating this thread:
PetitParser needs to be retested if it loads fine in Squeak 4.4...
Agreed. One possible solution is to dump PetitParser into a filetree repository on github and use Dale Henrich's builderCI. You (not Hannes necessarily, but whoever does this) could use https://github.com/frankshearar/Control as a guide on how to set things up. That also has the side benefit of letting Travis-CI do the work, at the cost of needing to keep the filetree repository in sync with the canonical PetitParser repository. Given the rate of change in that repo, that shouldn't be too hard; PP is now quite well beaten upon.
frank
--Hannes
On 8/31/12, Dale Henrichs dhenrich@vmware.com wrote:
----- Original Message ----- | From: "Frank Shearar" frank.shearar@gmail.com | | I'm aiming to, at some point in the very near future, implement some | kind of minimal CI infrastructure that could take a ConfigurationOf | and run its tests. I was hoping builderCI could do it, but it's quite | a complicated beast.
Frank,
I think the interesting bit in builderCI that you're looking for to construct the test suite is probably this chunk of code that leverages the Metacello scripting api:
| suite configurationClassNameList | configurationClassNameList := #( "list of configuration classes" ). suite := TestCase suiteClass named: configurationClassNameList printString, ' Test Suite'. configurationClassNameList do: [ :className | ((MetacelloProjectRegistration registrationForClassNamed: className ifAbsent: [ self error: className printString , ' not registered (loaded)' ]) currentlyLoadedClassesInProject select: [ :cl | cl inheritsFrom: TestCase ]) do: [ :cl | cl isAbstract ifFalse: [ suite addTest: cl buildSuiteFromSelectors ] ] ].
Dale
On 23 November 2012 10:41, Frank Shearar frank.shearar@gmail.com wrote:
On 21 November 2012 21:20, H. Hirzel hannes.hirzel@gmail.com wrote:
As a reminder (for myself or somebody else..) by reactivating this thread:
PetitParser needs to be retested if it loads fine in Squeak 4.4...
Agreed. One possible solution is to dump PetitParser into a filetree repository on github and use Dale Henrich's builderCI. You (not Hannes necessarily, but whoever does this) could use https://github.com/frankshearar/Control as a guide on how to set things up. That also has the side benefit of letting Travis-CI do the work, at the cost of needing to keep the filetree repository in sync with the canonical PetitParser repository. Given the rate of change in that repo, that shouldn't be too hard; PP is now quite well beaten upon.
I should add: PP's Smalltalk parser WILL break on 4.4 because PP uses the host system to parse numbers. In Pharo, NumberParser parses only Smalltalk numbers; in Squeak ExtendedNumberParser accepts things like "1." as a number.
Nicolas and I have done some work towards fixing this, and I can't recall off the top of my head where that stands.
frank
frank
--Hannes
On 8/31/12, Dale Henrichs dhenrich@vmware.com wrote:
----- Original Message ----- | From: "Frank Shearar" frank.shearar@gmail.com | | I'm aiming to, at some point in the very near future, implement some | kind of minimal CI infrastructure that could take a ConfigurationOf | and run its tests. I was hoping builderCI could do it, but it's quite | a complicated beast.
Frank,
I think the interesting bit in builderCI that you're looking for to construct the test suite is probably this chunk of code that leverages the Metacello scripting api:
| suite configurationClassNameList | configurationClassNameList := #( "list of configuration classes" ). suite := TestCase suiteClass named: configurationClassNameList printString, ' Test Suite'. configurationClassNameList do: [ :className | ((MetacelloProjectRegistration registrationForClassNamed: className ifAbsent: [ self error: className printString , ' not registered (loaded)' ]) currentlyLoadedClassesInProject select: [ :cl | cl inheritsFrom: TestCase ]) do: [ :cl | cl isAbstract ifFalse: [ suite addTest: cl buildSuiteFromSelectors ] ] ].
Dale
Maybe try to search these on your disk or on the net
"Number class>>#readSmalltalkSyntaxFrom:" "Number readSmalltalkSyntaxFrom:"
Nicolas
2012/12/3 Frank Shearar frank.shearar@gmail.com:
On 23 November 2012 10:41, Frank Shearar frank.shearar@gmail.com wrote:
On 21 November 2012 21:20, H. Hirzel hannes.hirzel@gmail.com wrote:
As a reminder (for myself or somebody else..) by reactivating this thread:
PetitParser needs to be retested if it loads fine in Squeak 4.4...
Agreed. One possible solution is to dump PetitParser into a filetree repository on github and use Dale Henrich's builderCI. You (not Hannes necessarily, but whoever does this) could use https://github.com/frankshearar/Control as a guide on how to set things up. That also has the side benefit of letting Travis-CI do the work, at the cost of needing to keep the filetree repository in sync with the canonical PetitParser repository. Given the rate of change in that repo, that shouldn't be too hard; PP is now quite well beaten upon.
I should add: PP's Smalltalk parser WILL break on 4.4 because PP uses the host system to parse numbers. In Pharo, NumberParser parses only Smalltalk numbers; in Squeak ExtendedNumberParser accepts things like "1." as a number.
Nicolas and I have done some work towards fixing this, and I can't recall off the top of my head where that stands.
frank
frank
--Hannes
On 8/31/12, Dale Henrichs dhenrich@vmware.com wrote:
----- Original Message ----- | From: "Frank Shearar" frank.shearar@gmail.com | | I'm aiming to, at some point in the very near future, implement some | kind of minimal CI infrastructure that could take a ConfigurationOf | and run its tests. I was hoping builderCI could do it, but it's quite | a complicated beast.
Frank,
I think the interesting bit in builderCI that you're looking for to construct the test suite is probably this chunk of code that leverages the Metacello scripting api:
| suite configurationClassNameList | configurationClassNameList := #( "list of configuration classes" ). suite := TestCase suiteClass named: configurationClassNameList printString, ' Test Suite'. configurationClassNameList do: [ :className | ((MetacelloProjectRegistration registrationForClassNamed: className ifAbsent: [ self error: className printString , ' not registered (loaded)' ]) currentlyLoadedClassesInProject select: [ :cl | cl inheritsFrom: TestCase ]) do: [ :cl | cl isAbstract ifFalse: [ suite addTest: cl buildSuiteFromSelectors ] ] ].
Dale
Right. That's the hint I needed. The status is this:
Nicolas got the Pharo side of things integrated (http://code.google.com/p/pharo/issues/detail?id=2063)
Now it's up to me to * get String>>asSmalltalkNumber and Number class>>#readSmalltalkSyntaxFrom: into Trunk, * update the PP Smalltalk parser to use the above, * resubmit, pinging Lukas
Right!
frank
On 3 December 2012 23:01, Nicolas Cellier nicolas.cellier.aka.nice@gmail.com wrote:
Maybe try to search these on your disk or on the net
"Number class>>#readSmalltalkSyntaxFrom:" "Number readSmalltalkSyntaxFrom:"
Nicolas
2012/12/3 Frank Shearar frank.shearar@gmail.com:
On 23 November 2012 10:41, Frank Shearar frank.shearar@gmail.com wrote:
On 21 November 2012 21:20, H. Hirzel hannes.hirzel@gmail.com wrote:
As a reminder (for myself or somebody else..) by reactivating this thread:
PetitParser needs to be retested if it loads fine in Squeak 4.4...
Agreed. One possible solution is to dump PetitParser into a filetree repository on github and use Dale Henrich's builderCI. You (not Hannes necessarily, but whoever does this) could use https://github.com/frankshearar/Control as a guide on how to set things up. That also has the side benefit of letting Travis-CI do the work, at the cost of needing to keep the filetree repository in sync with the canonical PetitParser repository. Given the rate of change in that repo, that shouldn't be too hard; PP is now quite well beaten upon.
I should add: PP's Smalltalk parser WILL break on 4.4 because PP uses the host system to parse numbers. In Pharo, NumberParser parses only Smalltalk numbers; in Squeak ExtendedNumberParser accepts things like "1." as a number.
Nicolas and I have done some work towards fixing this, and I can't recall off the top of my head where that stands.
frank
frank
--Hannes
On 8/31/12, Dale Henrichs dhenrich@vmware.com wrote:
----- Original Message ----- | From: "Frank Shearar" frank.shearar@gmail.com | | I'm aiming to, at some point in the very near future, implement some | kind of minimal CI infrastructure that could take a ConfigurationOf | and run its tests. I was hoping builderCI could do it, but it's quite | a complicated beast.
Frank,
I think the interesting bit in builderCI that you're looking for to construct the test suite is probably this chunk of code that leverages the Metacello scripting api:
| suite configurationClassNameList | configurationClassNameList := #( "list of configuration classes" ). suite := TestCase suiteClass named: configurationClassNameList printString, ' Test Suite'. configurationClassNameList do: [ :className | ((MetacelloProjectRegistration registrationForClassNamed: className ifAbsent: [ self error: className printString , ' not registered (loaded)' ]) currentlyLoadedClassesInProject select: [ :cl | cl inheritsFrom: TestCase ]) do: [ :cl | cl isAbstract ifFalse: [ suite addTest: cl buildSuiteFromSelectors ] ] ].
Dale
If you need some argumentation to convince Lukas, note that #readSmalltalkSyntaxFrom: now exists in Squeak, Pharo, Dolphin, Smalltalk X, Visualworks, so it's quite portable (I didn't check Visual age nor gnu Smalltalk)
Nicolas
2012/12/4 Frank Shearar frank.shearar@gmail.com:
Right. That's the hint I needed. The status is this:
Nicolas got the Pharo side of things integrated (http://code.google.com/p/pharo/issues/detail?id=2063)
Now it's up to me to
- get String>>asSmalltalkNumber and Number
class>>#readSmalltalkSyntaxFrom: into Trunk,
- update the PP Smalltalk parser to use the above,
- resubmit, pinging Lukas
Right!
frank
On 3 December 2012 23:01, Nicolas Cellier nicolas.cellier.aka.nice@gmail.com wrote:
Maybe try to search these on your disk or on the net
"Number class>>#readSmalltalkSyntaxFrom:" "Number readSmalltalkSyntaxFrom:"
Nicolas
2012/12/3 Frank Shearar frank.shearar@gmail.com:
On 23 November 2012 10:41, Frank Shearar frank.shearar@gmail.com wrote:
On 21 November 2012 21:20, H. Hirzel hannes.hirzel@gmail.com wrote:
As a reminder (for myself or somebody else..) by reactivating this thread:
PetitParser needs to be retested if it loads fine in Squeak 4.4...
Agreed. One possible solution is to dump PetitParser into a filetree repository on github and use Dale Henrich's builderCI. You (not Hannes necessarily, but whoever does this) could use https://github.com/frankshearar/Control as a guide on how to set things up. That also has the side benefit of letting Travis-CI do the work, at the cost of needing to keep the filetree repository in sync with the canonical PetitParser repository. Given the rate of change in that repo, that shouldn't be too hard; PP is now quite well beaten upon.
I should add: PP's Smalltalk parser WILL break on 4.4 because PP uses the host system to parse numbers. In Pharo, NumberParser parses only Smalltalk numbers; in Squeak ExtendedNumberParser accepts things like "1." as a number.
Nicolas and I have done some work towards fixing this, and I can't recall off the top of my head where that stands.
frank
frank
--Hannes
On 8/31/12, Dale Henrichs dhenrich@vmware.com wrote:
----- Original Message ----- | From: "Frank Shearar" frank.shearar@gmail.com | | I'm aiming to, at some point in the very near future, implement some | kind of minimal CI infrastructure that could take a ConfigurationOf | and run its tests. I was hoping builderCI could do it, but it's quite | a complicated beast.
Frank,
I think the interesting bit in builderCI that you're looking for to construct the test suite is probably this chunk of code that leverages the Metacello scripting api:
| suite configurationClassNameList | configurationClassNameList := #( "list of configuration classes" ). suite := TestCase suiteClass named: configurationClassNameList printString, ' Test Suite'. configurationClassNameList do: [ :className | ((MetacelloProjectRegistration registrationForClassNamed: className ifAbsent: [ self error: className printString , ' not registered (loaded)' ]) currentlyLoadedClassesInProject select: [ :cl | cl inheritsFrom: TestCase ]) do: [ :cl | cl isAbstract ifFalse: [ suite addTest: cl buildSuiteFromSelectors ] ] ].
Dale
squeak-dev@lists.squeakfoundation.org
-
Dale Henrichs -
David T. Lewis -
Frank Shearar -
H. Hirzel -
Nicolas Cellier -
Sean P. DeNigris