You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Test failures for the code-metrics and web-log-report examples happen in MacOSX. The commands used in the examples start to timeout for no apparent reason. By increasing the alarm's time, the tests seem to succeed most of the times, but this shouldn't be the culprit. I would guess that a command aborted leading all others to timeout, but dgsh_negotiate's exit handler does not report an abnormal exit.
The text was updated successfully, but these errors were encountered:
Both are graphs that are much bigger than others. Can you look the progression of the negotiation message along the graph (ideally with timestamps)? This might tell you whether the delay is normal or not.
Test failures for the
code-metrics
andweb-log-report
examples happen in MacOSX. The commands used in the examples start to timeout for no apparent reason. By increasing the alarm's time, the tests seem to succeed most of the times, but this shouldn't be the culprit. I would guess that a command aborted leading all others to timeout, butdgsh_negotiate
's exit handler does not report an abnormal exit.The text was updated successfully, but these errors were encountered: