Hi Damien,<br>
<br>
On Wed, Aug 8, 2018 at 9:29 AM, Damien Pollet <notifications@github.com><br>
wrote:<br>
<br>
> Could the VM provide an option for separating its own output from the<br>
> image's output?<br>
><br>
<br>
Yes, I guess it could. But (to state the obvious) this wouldn't help e.g.<br>
errors coming from C library code, only explicit error messages from the VM<br>
code itself.<br>
<br>
> Concretely, the VM complains about pthread_setschedparam in my Travis<br>
> builds, which prevents writing command-line scripts with clean output both<br>
> on stdout and stderr. See hpi-swa/smalltalkCI#388<br>
> <https://github.com/hpi-swa/smalltalkCI/issues/388><br>
><br>
The thing is, this is worrying.  If pthread_setschedparam complains then it<br>
likely means you don't have reliable time or delays in the running system.<br>
You may be better off using an timer heartbeat VM if your build machine<br>
won't support multiple thread priorities.  Alternatively it could simply be<br>
a issue of the age of the kernel.<br>
<br>
Can you post the exact error message and the build machine's kernel version?<br>
<br>
> Maybe it's possible to play with the file descriptors at image startup,<br>
> but it would make sense if the VM itself had something like a --silent or<br>
> a --vm-stderr FILE flag (the JVM has -Xlog) to redirect its diagnostic<br>
> messages so that anything that goes to stdout or stderr exclusively comes<br>
> from the image.<br>
><br>
<br>
Yes, but this would require some intelligence to ensure the VM does answer<br>
actual stderr through the primitives that provide access to them<br>
(stdioHandles uses the primitiveFileStdioHandles primitive in<br>
FilePlugin). So it's not trivial.<br>
<br>
> —<br>
> You are receiving this because you are subscribed to this thread.<br>
> Reply to this email directly, view it on GitHub<br>
> <https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/275>, or mute<br>
> the thread<br>
> <https://github.com/notifications/unsubscribe-auth/APHa0KEfhqUkkNSkZ6TO2e2dPJeoZyI6ks5uOxHTgaJpZM4V0Q3j><br>
> .<br>
><br>
_,,,^..^,,,_<br>
best, Eliot<br>


<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/275#issuecomment-411523476">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AhLyW-GToHtZXhjwISCB8lMn_g75T1ndks5uOztvgaJpZM4V0Q3j">mute the thread</a>.<img src="https://github.com/notifications/beacon/AhLyWzbOnii1KR591rHHbCF-6Kz9GovJks5uOztvgaJpZM4V0Q3j.gif" height="1" width="1" alt="" /></p>
<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/OpenSmalltalk/opensmalltalk-vm","title":"OpenSmalltalk/opensmalltalk-vm","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/OpenSmalltalk/opensmalltalk-vm"}},"updates":{"snippets":[{"icon":"PERSON","message":"@eliotmiranda in #275: Hi Damien,\n\nOn Wed, Aug 8, 2018 at 9:29 AM, Damien Pollet \u003cnotifications@github.com\u003e\nwrote:\n\n\u003e Could the VM provide an option for separating its own output from the\n\u003e image's output?\n\u003e\n\nYes, I guess it could. But (to state the obvious) this wouldn't help e.g.\nerrors coming from C library code, only explicit error messages from the VM\ncode itself.\n\n\u003e Concretely, the VM complains about pthread_setschedparam in my Travis\n\u003e builds, which prevents writing command-line scripts with clean output both\n\u003e on stdout and stderr. See hpi-swa/smalltalkCI#388\n\u003e \u003chttps://github.com/hpi-swa/smalltalkCI/issues/388\u003e\n\u003e\nThe thing is, this is worrying.  If pthread_setschedparam complains then it\nlikely means you don't have reliable time or delays in the running system.\nYou may be better off using an timer heartbeat VM if your build machine\nwon't support multiple thread priorities.  Alternatively it could simply be\na issue of the age of the kernel.\n\nCan you post the exact error message and the build machine's kernel version?\n\n\u003e Maybe it's possible to play with the file descriptors at image startup,\n\u003e but it would make sense if the VM itself had something like a --silent or\n\u003e a --vm-stderr FILE flag (the JVM has -Xlog) to redirect its diagnostic\n\u003e messages so that anything that goes to stdout or stderr exclusively comes\n\u003e from the image.\n\u003e\n\nYes, but this would require some intelligence to ensure the VM does answer\nactual stderr through the primitives that provide access to them\n(stdioHandles uses the primitiveFileStdioHandles primitive in\nFilePlugin). So it's not trivial.\n\n\u003e —\n\u003e You are receiving this because you are subscribed to this thread.\n\u003e Reply to this email directly, view it on GitHub\n\u003e \u003chttps://github.com/OpenSmalltalk/opensmalltalk-vm/issues/275\u003e, or mute\n\u003e the thread\n\u003e \u003chttps://github.com/notifications/unsubscribe-auth/APHa0KEfhqUkkNSkZ6TO2e2dPJeoZyI6ks5uOxHTgaJpZM4V0Q3j\u003e\n\u003e .\n\u003e\n_,,,^..^,,,_\nbest, Eliot\n"}],"action":{"name":"View Issue","url":"https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/275#issuecomment-411523476"}}}</script>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/275#issuecomment-411523476",
"url": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/275#issuecomment-411523476",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
},
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "AF6C5A86-E920-430C-9C59-A73278B5EFEB",
"title": "Re: [OpenSmalltalk/opensmalltalk-vm] Provide control over VM messages (#275)",
"sections": [
{
"text": "",
"activityTitle": "**Eliot Miranda**",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@eliotmiranda",
"facts": [

]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueComment\",\n\"repositoryFullName\": \"OpenSmalltalk/opensmalltalk-vm\",\n\"issueId\": 275,\n\"IssueComment\": \"{{IssueComment.value}}\"\n}"
}
]
},
{
"name": "Close issue",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"IssueClose\",\n\"repositoryFullName\": \"OpenSmalltalk/opensmalltalk-vm\",\n\"issueId\": 275\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/OpenSmalltalk/opensmalltalk-vm/issues/275#issuecomment-411523476"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n\"commandName\": \"MuteNotification\",\n\"threadId\": 366022115\n}"
}
],
"themeColor": "26292E"
}
]</script>