Verbose Logging (during CI)

3 views
Skip to first unread message

Sean DeNigris

unread,
Feb 25, 2018, 8:06:18 PM2/25/18
to Metacello
Is there a way to get more information on the console about what Metacello is doing during a load? I couldn't find anything obvious in the Settings or ML…

I have the following in the console, but I am not at all clear what it means, I'm assuming since "BaselineOfSimplePersistence" was "Loaded" that it failed at whatever came next, but I can't seem to tell what that next thing was from the output.
Fetched -> BaselineOfSimplePersistence-SeanDeNigris.1513620736 --- https://github.com/seandenigris/Simple-Persistence.git[master] --- /builds/SeanDeNigris/Quote-Me/smalltalkCI/_builds/2018_02_25_23_25_56/pharo-local/iceberg/seandenigris/Simple-Persistence/repository (Libgit)
Loaded -> BaselineOfSimplePersistence-SeanDeNigris.1513620736 --- https://github.com/seandenigris/Simple-Persistence.git[master] --- /builds/SeanDeNigris/Quote-Me/smalltalkCI/_builds/2018_02_25_23_25_56/pharo-local/iceberg/seandenigris/Simple-Persistence/repository (Libgit)LGit_GIT_EEOF: GitLab: The project you were looking for could not be found.


LGitReturnCodeEnum>>handleLGitReturnCode
LGitRepository(LGitExternalObject)>>withReturnHandlerDo:
LGitRepository>>clone:options:to:

Thanks!

- s 

Dale Henrichs

unread,
Feb 26, 2018, 1:27:24 PM2/26/18
to meta...@googlegroups.com



On 02/25/2018 05:06 PM, Sean DeNigris wrote:
Is there a way to get more information on the console about what Metacello is doing during a load? I couldn't find anything obvious in the Settings or ML…
Thinking about this ... with all the logging that goes on during a Metacello load I wanted to avoid have "About to load -> BaselineOf...." followed by "Loaded -> BaselineOf", however, it should be possible to wrap the stack at an appropriate level with an Error handler that dumps out a message about the operation (fetch or load) and the package/project involved that was in progress when the error occurred ...

If you think this would help, please submit a Metacello issue and we can talk about possible solutions in that thread ... If I could see the full stack for this error, I'd be willing to push a change in short order that provided better logging for this particular use case...

Dale

I have the following in the console, but I am not at all clear what it means, I'm assuming since "BaselineOfSimplePersistence" was "Loaded" that it failed at whatever came next, but I can't seem to tell what that next thing was from the output.
Fetched -> BaselineOfSimplePersistence-SeanDeNigris.1513620736 --- https://github.com/seandenigris/Simple-Persistence.git[master] --- /builds/SeanDeNigris/Quote-Me/smalltalkCI/_builds/2018_02_25_23_25_56/pharo-local/iceberg/seandenigris/Simple-Persistence/repository (Libgit) Loaded -> BaselineOfSimplePersistence-SeanDeNigris.1513620736 --- https://github.com/seandenigris/Simple-Persistence.git[master] --- /builds/SeanDeNigris/Quote-Me/smalltalkCI/_builds/2018_02_25_23_25_56/pharo-local/iceberg/seandenigris/Simple-Persistence/repository (Libgit)LGit_GIT_EEOF: GitLab: The project you were looking for could not be found. LGitReturnCodeEnum>>handleLGitReturnCode LGitRepository(LGitExternalObject)>>withReturnHandlerDo: LGitRepository>>clone:options:to:

Thanks!

- s 
--
You received this message because you are subscribed to the Google Groups "Metacello" group.
To unsubscribe from this group and stop receiving emails from it, send an email to metacello+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Sean DeNigris

unread,
Mar 1, 2018, 4:36:50 PM3/1/18
to Metacello
Thinking about this ... with all the logging that goes on during a Metacello load I wanted to avoid have "About to load -> BaselineOf...." followed by "Loaded -> BaselineOf"
Yes, that makes sense. The problem (IIUC) is that in a tricky (e.g. remote/CI) scenario, since there is no "about to…" log message, when the next step fails, it seems not at all clear what that next step even was!

please submit a Metacello issue and we can talk about possible solutions in that thread ... If I could see the full stack for this error, I'd be willing to push a change in short order that provided better logging for this particular use case...
Reply all
Reply to author
Forward
0 new messages