MNU in MCMcmUpdater >> #updateFromRepositories

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

MNU in MCMcmUpdater >> #updateFromRepositories

Frank Shearar-3
http://build.squeak.org/job/SqueakTrunk/787/console shows this failure:

2014-01-26T20:14:48.748+01:00: Conflict; choosing remote:
2014-01-26T20:14:48.766+01:00: Utilities class>>updateFromServer
2014-01-26T20:14:48.782+01:00: Resolved? true

MultiByteFileStream(Object)>>error:
MultiByteFileStream(Object)>>primitiveFailed:
MultiByteFileStream(Object)>>primitiveFailed
MultiByteFileStream(StandardFileStream)>>primSize:
MultiByteFileStream(StandardFileStream)>>size
MultiByteFileStream(StandardFileStream)>>setToEnd
MessageNotUnderstood(Error)>>printVerboseOn:
[] in UndefinedObject>>DoIt
BlockClosure>>cull:
[] in MethodContext(ContextPart)>>handleSignal:
BlockClosure>>ensure:
MethodContext(ContextPart)>>handleSignal:
MethodContext(ContextPart)>>handleSignal:
MethodContext(ContextPart)>>handleSignal:
MethodContext(ContextPart)>>handleSignal:
MethodContext(ContextPart)>>handleSignal:
MethodContext(ContextPart)>>handleSignal:
MessageNotUnderstood(Exception)>>signal
UndefinedObject(Object)>>doesNotUnderstand: #dependencies
[] in [] in [] in [] in MCMcmUpdater class>>updateFromRepositories

I've seen it a couple times before, and never quite figured out why.
This method has two senders of #dependencies. This is the one by the
"Skip packages that are not in the image" comment.

frank

Reply | Threaded
Open this post in threaded view
|

Re: MNU in MCMcmUpdater >> #updateFromRepositories

Karl Ramberg
Hi,
I'm looking at a error with MultiByteFileStream>>testLineEndingChunk wich fails at all line endings but nil.

This is on windows 8.1

There are some issues with MultiByteFileStream that should be fixed before release.

Cheers,
Karl



On Sun, Jan 26, 2014 at 8:25 PM, Frank Shearar <[hidden email]> wrote:
http://build.squeak.org/job/SqueakTrunk/787/console shows this failure:

2014-01-26T20:14:48.748+01:00: Conflict; choosing remote:
2014-01-26T20:14:48.766+01:00: Utilities class>>updateFromServer
2014-01-26T20:14:48.782+01:00: Resolved? true

MultiByteFileStream(Object)>>error:
MultiByteFileStream(Object)>>primitiveFailed:
MultiByteFileStream(Object)>>primitiveFailed
MultiByteFileStream(StandardFileStream)>>primSize:
MultiByteFileStream(StandardFileStream)>>size
MultiByteFileStream(StandardFileStream)>>setToEnd
MessageNotUnderstood(Error)>>printVerboseOn:
[] in UndefinedObject>>DoIt
BlockClosure>>cull:
[] in MethodContext(ContextPart)>>handleSignal:
BlockClosure>>ensure:
MethodContext(ContextPart)>>handleSignal:
MethodContext(ContextPart)>>handleSignal:
MethodContext(ContextPart)>>handleSignal:
MethodContext(ContextPart)>>handleSignal:
MethodContext(ContextPart)>>handleSignal:
MethodContext(ContextPart)>>handleSignal:
MessageNotUnderstood(Exception)>>signal
UndefinedObject(Object)>>doesNotUnderstand: #dependencies
[] in [] in [] in [] in MCMcmUpdater class>>updateFromRepositories

I've seen it a couple times before, and never quite figured out why.
This method has two senders of #dependencies. This is the one by the
"Skip packages that are not in the image" comment.

frank




Reply | Threaded
Open this post in threaded view
|

Re: MNU in MCMcmUpdater >> #updateFromRepositories

Karl Ramberg
Duh, MultiByteFileStream>>testLineEndingChunk is expected failure, as far as I can tell

Cheers,
Karl


On Sun, Jan 26, 2014 at 9:45 PM, karl ramberg <[hidden email]> wrote:
Hi,
I'm looking at a error with MultiByteFileStream>>testLineEndingChunk wich fails at all line endings but nil.

This is on windows 8.1

There are some issues with MultiByteFileStream that should be fixed before release.

Cheers,
Karl



On Sun, Jan 26, 2014 at 8:25 PM, Frank Shearar <[hidden email]> wrote:
http://build.squeak.org/job/SqueakTrunk/787/console shows this failure:

2014-01-26T20:14:48.748+01:00: Conflict; choosing remote:
2014-01-26T20:14:48.766+01:00: Utilities class>>updateFromServer
2014-01-26T20:14:48.782+01:00: Resolved? true

MultiByteFileStream(Object)>>error:
MultiByteFileStream(Object)>>primitiveFailed:
MultiByteFileStream(Object)>>primitiveFailed
MultiByteFileStream(StandardFileStream)>>primSize:
MultiByteFileStream(StandardFileStream)>>size
MultiByteFileStream(StandardFileStream)>>setToEnd
MessageNotUnderstood(Error)>>printVerboseOn:
[] in UndefinedObject>>DoIt
BlockClosure>>cull:
[] in MethodContext(ContextPart)>>handleSignal:
BlockClosure>>ensure:
MethodContext(ContextPart)>>handleSignal:
MethodContext(ContextPart)>>handleSignal:
MethodContext(ContextPart)>>handleSignal:
MethodContext(ContextPart)>>handleSignal:
MethodContext(ContextPart)>>handleSignal:
MethodContext(ContextPart)>>handleSignal:
MessageNotUnderstood(Exception)>>signal
UndefinedObject(Object)>>doesNotUnderstand: #dependencies
[] in [] in [] in [] in MCMcmUpdater class>>updateFromRepositories

I've seen it a couple times before, and never quite figured out why.
This method has two senders of #dependencies. This is the one by the
"Skip packages that are not in the image" comment.

frank





Reply | Threaded
Open this post in threaded view
|

Re: MNU in MCMcmUpdater >> #updateFromRepositories

Bert Freudenberg
In reply to this post by Frank Shearar-3
On 26.01.2014, at 20:25, Frank Shearar <[hidden email]> wrote:

> UndefinedObject(Object)>>doesNotUnderstand: #dependencies
> [] in [] in [] in [] in MCMcmUpdater class>>updateFromRepositories
>
> I've seen it a couple times before, and never quite figured out why.
> This method has two senders of #dependencies. This is the one by the
> "Skip packages that are not in the image" comment.

That must mean that config is nil. Which means that versionNamed: failed to load the version. Which probably means that the config listed a file that does not exist.

For debugging it might help to log the error suppressed in MCFileBasedRepository>>versionNamed: on FileDoesNotExistException.

- Bert -





smime.p7s (5K) Download Attachment