On 2012-10-24 10:45 AM, Levente Uzonyi wrote:
> On Wed, 24 Oct 2012, Igor Stasenko wrote: > >> Err, no. >> A "workspace" is where slave doing its work. >> But artifacts made by job(s) are stored in separate place. > > Right, but as I said, the directory structure created by Jenkins > didn't match what the wiki says when we set up Jenkins. So, tt's still > worth checking the directory structure. > > > Levente > The directory structure seems to be as it should be: xxxxxxxxx:/xxxxxxxxx/jobs/SqueakTrunk/builds/20$ ls -la total 864 drwxr-xr-x 3 jenkins xxxxxx 4096 Oct 23 19:26 . drwxr-xr-x 21 jenkins xxxxxx 4096 Oct 23 19:21 .. drwxr-xr-x 3 jenkins xxxxxx 4096 Oct 23 19:26 archive -rw-r--r-- 1 jenkins xxxxxx 2906 Oct 23 19:26 build.xml -rw-r--r-- 1 jenkins xxxxxx 252 Oct 23 19:21 changelog.xml -rw-r--r-- 1 jenkins xxxxxx 857130 Oct 23 19:26 junitResult.xml -rw-r--r-- 1 jenkins xxxxxx 1312 Oct 23 19:26 log The deliverables are in the archive directory as expected. I think the build.xml is what is read to inform the web page. Looking at the site it seems a bit more stable than yesterday. Somewhat. Nothing has disappeared so far. Perhaps it's hardening a bit with use. Chris |
On 24 October 2012 18:06, Chris Cunnington
<[hidden email]> wrote: > On 2012-10-24 10:45 AM, Levente Uzonyi wrote: >> >> On Wed, 24 Oct 2012, Igor Stasenko wrote: >> >>> Err, no. >>> A "workspace" is where slave doing its work. >>> But artifacts made by job(s) are stored in separate place. >> >> >> Right, but as I said, the directory structure created by Jenkins didn't >> match what the wiki says when we set up Jenkins. So, tt's still worth >> checking the directory structure. >> >> >> Levente >> > > The directory structure seems to be as it should be: > > xxxxxxxxx:/xxxxxxxxx/jobs/SqueakTrunk/builds/20$ ls -la > total 864 > drwxr-xr-x 3 jenkins xxxxxx 4096 Oct 23 19:26 . > drwxr-xr-x 21 jenkins xxxxxx 4096 Oct 23 19:21 .. > drwxr-xr-x 3 jenkins xxxxxx 4096 Oct 23 19:26 archive > -rw-r--r-- 1 jenkins xxxxxx 2906 Oct 23 19:26 build.xml > -rw-r--r-- 1 jenkins xxxxxx 252 Oct 23 19:21 changelog.xml > -rw-r--r-- 1 jenkins xxxxxx 857130 Oct 23 19:26 junitResult.xml > -rw-r--r-- 1 jenkins xxxxxx 1312 Oct 23 19:26 log > > The deliverables are in the archive directory as expected. I think the > build.xml is what is read to inform the web page. > > Looking at the site it seems a bit more stable than yesterday. Somewhat. > Nothing has disappeared so far. Perhaps it's hardening a bit with use. The glue's setting? frank > Chris > |
On 2012-10-24 1:09 PM, Frank Shearar wrote:
> On 24 October 2012 18:06, Chris Cunnington > <[hidden email]> wrote: >> On 2012-10-24 10:45 AM, Levente Uzonyi wrote: >>> On Wed, 24 Oct 2012, Igor Stasenko wrote: >>> >>>> Err, no. >>>> A "workspace" is where slave doing its work. >>>> But artifacts made by job(s) are stored in separate place. >>> >>> Right, but as I said, the directory structure created by Jenkins didn't >>> match what the wiki says when we set up Jenkins. So, tt's still worth >>> checking the directory structure. >>> >>> >>> Levente >>> >> The directory structure seems to be as it should be: >> >> xxxxxxxxx:/xxxxxxxxx/jobs/SqueakTrunk/builds/20$ ls -la >> total 864 >> drwxr-xr-x 3 jenkins xxxxxx 4096 Oct 23 19:26 . >> drwxr-xr-x 21 jenkins xxxxxx 4096 Oct 23 19:21 .. >> drwxr-xr-x 3 jenkins xxxxxx 4096 Oct 23 19:26 archive >> -rw-r--r-- 1 jenkins xxxxxx 2906 Oct 23 19:26 build.xml >> -rw-r--r-- 1 jenkins xxxxxx 252 Oct 23 19:21 changelog.xml >> -rw-r--r-- 1 jenkins xxxxxx 857130 Oct 23 19:26 junitResult.xml >> -rw-r--r-- 1 jenkins xxxxxx 1312 Oct 23 19:26 log >> >> The deliverables are in the archive directory as expected. I think the >> build.xml is what is read to inform the web page. >> >> Looking at the site it seems a bit more stable than yesterday. Somewhat. >> Nothing has disappeared so far. Perhaps it's hardening a bit with use. > The glue's setting? > > frank Chris |
In reply to this post by Frank Shearar-3
On 22 October 2012 20:21, Frank Shearar <[hidden email]> wrote:
> We're down to 6 failing unit tests on the Linux platform, one of which > is an expected failure and another of which is a known network issue > for the Linux platform. > > Would my kind Windows and OSX build volunteers please run builds > against the latest trunk image? > (http://173.246.101.237:8080/job/SqueakTrunk/lastCompletedBuild/artifact/) > > Note the new URL: that's thanks to Chris Cunnington, who has kindly > moved Jenkins to its new home. That will no doubt shortly become the > new squeakci.org. > > Windows users note please that you'll need to grant permission for the > build executables etc to act as servers and to make connections: you > can do this through the Windows Firewall configuration screens. (I'd > give more detailed instructions, but my Windows machines are far away > right now.) > > (Dale, this shouldn't affect you much, in the sense that you won't > need any changes to builderCI or whatever once the DNS changes have > been made. So if they _do_ affect you, they shouldn't affect you for > very long.) > > It's about time I started with the more admin-y side of the release, > making a Changelog and such. I'll make a start on this soon, > docs/progress to be on http://wiki.squeak.org/squeak/6188 > > frank The latest builds have a few new failures: * Tests.Compiler.DecompilerTests.testDecompilerInClassesLAtoLM [1] * TraitsTests.Kernel.ClassTraitTest.testConflictsAliasesAndExclusions [2] which is kind've surprising. frank [1] Error Message subscript is out of bounds: 1 Stacktrace Array(Object)>>error: Array(Object)>>errorSubscriptBounds: Array(Object)>>at: Decompiler>>pushTemporaryVariable: Decompiler(InstructionStream)>>interpretNextInstructionFor: Decompiler>>interpretNextInstructionFor: Decompiler>>statementsTo: Decompiler>>blockTo: Decompiler>>doClosureCopyCopiedValues:numArgs:blockSize: Decompiler>>pushClosureCopyNumCopiedValues:numArgs:blockSize: Decompiler(InstructionStream)>>interpretExtension:in:for: Decompiler(InstructionStream)>>interpretNextInstructionFor: Decompiler>>interpretNextInstructionFor: Decompiler>>statementsTo: Decompiler>>blockTo: Decompiler>>decompile:in:method:using: Decompiler>>decompile:in:method: DecompilerTests>>checkDecompileMethod: [] in [] in [] in DecompilerTests>>decompileClassesSelect: MethodDictionary>>keysAndValuesDo: LargeNegativeIntegerTest class(Behavior)>>selectorsAndMethodsDo: [] in [] in DecompilerTests>>decompileClassesSelect: Array(SequenceableCollection)>>do: [] in DecompilerTests>>decompileClassesSelect: BlockClosure>>on:do: CurrentReadOnlySourceFiles class>>cacheDuring: DecompilerTests>>decompileClassesSelect: DecompilerTests>>testDecompilerInClassesLAtoLM DecompilerTests(TestCase)>>performTest [2] Stacktrace Parser>>notify:at: Parser>>expected: Parser>>pattern:inContext: Parser>>method:context: [] in Parser>>parse:class:category:noPattern:context:notifying:ifFail: BlockClosure>>on:do: Parser>>parse:class:category:noPattern:context:notifying:ifFail: Compiler>>translate:noPattern:ifFail: Compiler>>compile:in:classified:notifying:ifFail: Metaclass(ClassDescription)>>traitAddSelector:withMethod: [] in Metaclass(ClassDescription)>>installTraitMethodDict: [] in Dictionary>>keysAndValuesDo: Dictionary>>associationsDo: Dictionary>>keysAndValuesDo: Metaclass(ClassDescription)>>installTraitMethodDict: Metaclass(ClassDescription)>>installTraitsFrom: Metaclass(ClassDescription)>>updateTraits Metaclass(ClassDescription)>>classify:under:from:trait: [] in ClassTrait(TraitDescription)>>notifyOfRecategorizedSelector:from:to: Array(SequenceableCollection)>>do: ClassTrait(TraitDescription)>>notifyOfRecategorizedSelector:from:to: TraitOrganizer(ClassOrganizer)>>notifyOfChangedSelector:from:to: TraitOrganizer(ClassOrganizer)>>classify:under:suppressIfDefault:logged: TraitOrganizer(ClassOrganizer)>>classify:under:suppressIfDefault: TraitOrganizer(Categorizer)>>classify:under: [] in ClassTrait(ClassDescription)>>installTraitMethodDict: [] in Dictionary>>keysAndValuesDo: Dictionary>>associationsDo: Dictionary>>keysAndValuesDo: ClassTrait(ClassDescription)>>installTraitMethodDict: ClassTrait(ClassDescription)>>installTraitsFrom: ClassTrait(TraitDescription)>>installTraitsFrom: ClassTrait(ClassDescription)>>updateTraits [] in ClassTrait(TraitDescription)>>addSelectorSilently:withMethod: Array(SequenceableCollection)>>do: ClassTrait(TraitDescription)>>addSelectorSilently:withMethod: ClassTrait(ClassDescription)>>addAndClassifySelector:withMethod:inProtocol:notifying: ClassTrait(ClassDescription)>>compile:classified:withStamp:notifying:logSource: ClassTrait(ClassDescription)>>compile:classified:withStamp:notifying: ClassTrait(ClassDescription)>>compile:classified:notifying: ClassTrait(ClassDescription)>>compile:classified: ClassTraitTest>>testConflictsAliasesAndExclusions ClassTraitTest(TestCase)>>performTest |
I know that this is quite late, but better late than never. Running the latest from Frank's squeak-ci repo I get 8 errors:
KernelTests: 3 errors 0 failures. NetworkTests: 2 errors 0 failures. Tests: 2 errors 0 failures. ToolsTests: 1 errors 0 failures. DependencyBrowserTest>>#testClassList LargeNegativeIntegerTest>>#testMinimumNegativeArithmetic LocaleTest>>#testLocaleChanged ReleaseTest>>#testNoObsoleteClasses SocketTest>>#testSocketReuse SocketTest>>#testUDP TimeStampTest>>#testFromSeconds TimeStampTest>>#testReadFromA1 I'll run it on my linux vm momentarily and report the results. Thanks for all the great work Frank! Jeff On Wed, Oct 24, 2012 at 11:35 AM, Frank Shearar <[hidden email]> wrote:
|
So running it on my ubuntu 12.10 linux vm resulted in 10 failures.
The additional failures appeared to be Sockets. DependencyBrowserTest>>#testClassList LargeNegativeIntegerTest>>#testMinimumNegativeIntegerArithmetic LocaleTest>>#testLocaleChanged ReleaseTest>>#testNoObsoleteClasses SocketTest>>#testLocalAddress SocketTest>>#testPeerName SocketTest>>#testRemoteAddress SocketTest>>#testSendTimeout TimeStampTest>>#testFromSeconds TimeStampTest>>#testReadFromA1 I'll run these tests on each system sometime again tomorrow. Thanks, Jeff On Fri, Oct 26, 2012 at 6:21 PM, Jeff Gonis <[hidden email]> wrote: I know that this is quite late, but better late than never. Running the latest from Frank's squeak-ci repo I get 8 errors: |
In reply to this post by Jeff Gonis-2
On 27 October 2012 01:21, Jeff Gonis <[hidden email]> wrote:
> I know that this is quite late, but better late than never. Running the > latest from Frank's squeak-ci repo I get 8 errors: > > KernelTests: 3 errors 0 failures. > NetworkTests: 2 errors 0 failures. > Tests: 2 errors 0 failures. > ToolsTests: 1 errors 0 failures. > > DependencyBrowserTest>>#testClassList I also saw this guy and was a bit surprised. I mean, the test is fragile in that we examine the current methods of a few classes (String) - I wrote it that way for lack of mocks - but didn't have a chance to see why. It probably broke because of the recent String changes shuffled the method order. > LargeNegativeIntegerTest>>#testMinimumNegativeArithmetic General question not just for Jeff: Can we mark this as an expected failure? frank > LocaleTest>>#testLocaleChanged > ReleaseTest>>#testNoObsoleteClasses > SocketTest>>#testSocketReuse > SocketTest>>#testUDP > TimeStampTest>>#testFromSeconds > TimeStampTest>>#testReadFromA1 > > I'll run it on my linux vm momentarily and report the results. > > Thanks for all the great work Frank! > Jeff > > > > On Wed, Oct 24, 2012 at 11:35 AM, Frank Shearar <[hidden email]> > wrote: >> >> On 22 October 2012 20:21, Frank Shearar <[hidden email]> wrote: >> > We're down to 6 failing unit tests on the Linux platform, one of which >> > is an expected failure and another of which is a known network issue >> > for the Linux platform. >> > >> > Would my kind Windows and OSX build volunteers please run builds >> > against the latest trunk image? >> > >> > (http://173.246.101.237:8080/job/SqueakTrunk/lastCompletedBuild/artifact/) >> > >> > Note the new URL: that's thanks to Chris Cunnington, who has kindly >> > moved Jenkins to its new home. That will no doubt shortly become the >> > new squeakci.org. >> > >> > Windows users note please that you'll need to grant permission for the >> > build executables etc to act as servers and to make connections: you >> > can do this through the Windows Firewall configuration screens. (I'd >> > give more detailed instructions, but my Windows machines are far away >> > right now.) >> > >> > (Dale, this shouldn't affect you much, in the sense that you won't >> > need any changes to builderCI or whatever once the DNS changes have >> > been made. So if they _do_ affect you, they shouldn't affect you for >> > very long.) >> > >> > It's about time I started with the more admin-y side of the release, >> > making a Changelog and such. I'll make a start on this soon, >> > docs/progress to be on http://wiki.squeak.org/squeak/6188 >> > >> > frank >> >> The latest builds have a few new failures: >> >> * Tests.Compiler.DecompilerTests.testDecompilerInClassesLAtoLM [1] >> * TraitsTests.Kernel.ClassTraitTest.testConflictsAliasesAndExclusions [2] >> >> which is kind've surprising. >> >> frank >> >> [1] Error Message >> >> subscript is out of bounds: 1 >> Stacktrace >> >> Array(Object)>>error: >> Array(Object)>>errorSubscriptBounds: >> Array(Object)>>at: >> Decompiler>>pushTemporaryVariable: >> Decompiler(InstructionStream)>>interpretNextInstructionFor: >> Decompiler>>interpretNextInstructionFor: >> Decompiler>>statementsTo: >> Decompiler>>blockTo: >> Decompiler>>doClosureCopyCopiedValues:numArgs:blockSize: >> Decompiler>>pushClosureCopyNumCopiedValues:numArgs:blockSize: >> Decompiler(InstructionStream)>>interpretExtension:in:for: >> Decompiler(InstructionStream)>>interpretNextInstructionFor: >> Decompiler>>interpretNextInstructionFor: >> Decompiler>>statementsTo: >> Decompiler>>blockTo: >> Decompiler>>decompile:in:method:using: >> Decompiler>>decompile:in:method: >> DecompilerTests>>checkDecompileMethod: >> [] in [] in [] in DecompilerTests>>decompileClassesSelect: >> MethodDictionary>>keysAndValuesDo: >> LargeNegativeIntegerTest class(Behavior)>>selectorsAndMethodsDo: >> [] in [] in DecompilerTests>>decompileClassesSelect: >> Array(SequenceableCollection)>>do: >> [] in DecompilerTests>>decompileClassesSelect: >> BlockClosure>>on:do: >> CurrentReadOnlySourceFiles class>>cacheDuring: >> DecompilerTests>>decompileClassesSelect: >> DecompilerTests>>testDecompilerInClassesLAtoLM >> DecompilerTests(TestCase)>>performTest >> >> >> [2] Stacktrace >> >> Parser>>notify:at: >> Parser>>expected: >> Parser>>pattern:inContext: >> Parser>>method:context: >> [] in Parser>>parse:class:category:noPattern:context:notifying:ifFail: >> BlockClosure>>on:do: >> Parser>>parse:class:category:noPattern:context:notifying:ifFail: >> Compiler>>translate:noPattern:ifFail: >> Compiler>>compile:in:classified:notifying:ifFail: >> Metaclass(ClassDescription)>>traitAddSelector:withMethod: >> [] in Metaclass(ClassDescription)>>installTraitMethodDict: >> [] in Dictionary>>keysAndValuesDo: >> Dictionary>>associationsDo: >> Dictionary>>keysAndValuesDo: >> Metaclass(ClassDescription)>>installTraitMethodDict: >> Metaclass(ClassDescription)>>installTraitsFrom: >> Metaclass(ClassDescription)>>updateTraits >> Metaclass(ClassDescription)>>classify:under:from:trait: >> [] in ClassTrait(TraitDescription)>>notifyOfRecategorizedSelector:from:to: >> Array(SequenceableCollection)>>do: >> ClassTrait(TraitDescription)>>notifyOfRecategorizedSelector:from:to: >> TraitOrganizer(ClassOrganizer)>>notifyOfChangedSelector:from:to: >> TraitOrganizer(ClassOrganizer)>>classify:under:suppressIfDefault:logged: >> TraitOrganizer(ClassOrganizer)>>classify:under:suppressIfDefault: >> TraitOrganizer(Categorizer)>>classify:under: >> [] in ClassTrait(ClassDescription)>>installTraitMethodDict: >> [] in Dictionary>>keysAndValuesDo: >> Dictionary>>associationsDo: >> Dictionary>>keysAndValuesDo: >> ClassTrait(ClassDescription)>>installTraitMethodDict: >> ClassTrait(ClassDescription)>>installTraitsFrom: >> ClassTrait(TraitDescription)>>installTraitsFrom: >> ClassTrait(ClassDescription)>>updateTraits >> [] in ClassTrait(TraitDescription)>>addSelectorSilently:withMethod: >> Array(SequenceableCollection)>>do: >> ClassTrait(TraitDescription)>>addSelectorSilently:withMethod: >> >> ClassTrait(ClassDescription)>>addAndClassifySelector:withMethod:inProtocol:notifying: >> >> ClassTrait(ClassDescription)>>compile:classified:withStamp:notifying:logSource: >> ClassTrait(ClassDescription)>>compile:classified:withStamp:notifying: >> ClassTrait(ClassDescription)>>compile:classified:notifying: >> ClassTrait(ClassDescription)>>compile:classified: >> ClassTraitTest>>testConflictsAliasesAndExclusions >> ClassTraitTest(TestCase)>>performTest >> > > > > |
Free forum by Nabble | Edit this page |