"Transcript addDependent: model." seems to break something...

[marceltaeumel]

Transcript outputs are redirected to be visible during the TravisCI build and test process. That's great! :)

Could it be possible that no other code is allowed to add new dependents to the Transcript stream? I have a test in my Signals project that produces an error only with your scripted platform.

[dalehenrich]

@marceltaeumel could you share some more details?

I think that I basically redefine the Transcript global to be a FileStream ... now one would think that FileStreams would be compatible with a TranscriptStream, but there are a couple of extra methods that TranscriptStream that FileStream does not ... so that could be the problem?

I hate to add these kind of extensions methods in my code, because they probably should be added at the platform level and I risk stomping on platform code if/when they actually implement the code ...

If you find that you need the extra protocol, then I will go ahead and add it ... when something is needed, it is needed:)

[marceltaeumel]

@dalehenrich This is what I basically do in the test:

Transcript addDependent: model.
Transcript cr; show: 'Hello World!'.
self assert: model lastValue = 'Hello World!'.
Transcript removeDependent: model.

The model stores that last value in the following way:

update: symbol
   symbol == #appendEntry ifTrue: [
      lastValue := Transcript contents].

Now, how does this work with a regular file stream? The transcript stream resets itself after each #show:. This is implemented in #endEntry. Maybe the call to #contents fails...

Best,
Marcel

[dalehenrich]

Ah, I will have to look but for non TranscriptStreams, I assume that contents will give you the contents of the entire Stream and not just the last entry ...

The #update: message behavior will also be different as well ... I will have to think about this ... presumably a Wrapper object can be used to forward messages to both the original Transcript and the fileStream object ... I would prefer that the platform folks add this kind of capability ... I simply want to route Transcript output to the fileStream ,,,

In GemStone I already use a wrapper/proxy object and all transcript traffic is automatically logged to a file ...

Dale
----- Original Message -----

| From: "Marcel Taeumel" notifications@github.com
| To: "dalehenrich/builderCI" builderCI@noreply.github.com
| Cc: "Dale Henrichs" dale.henrichs@gemtalksystems.com
| Sent: Monday, January 6, 2014 12:16:06 AM
| Subject: Re: [builderCI] "Transcript addDependent: model." seems to
| break something... (#56)

| This is what I basically do in the test:
| Transcript addDependent: model . Transcript cr ; show: 'Hello World!'
| . self assert: model lastValue = 'Hello World!' . Transcript
| removeDependent: model .
| The model stores that last value in the following way:
| update: symbol symbol == #appendEntry ifTrue: [ lastValue :=
| Transcript contents ] .
| Now, how does this work with a regular file stream? The transcript
| stream resets itself after each #show: . This is implemented in
| #endEntry . Maybe the call to #contents fails...
| Best,
| Marcel
| —
| Reply to this email directly or view it on GitHub .