Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

test: do not trigger node bug with fd mapping #94

Merged
merged 3 commits into from
Feb 19, 2015
Merged

test: do not trigger node bug with fd mapping #94

merged 3 commits into from
Feb 19, 2015

Commits on Feb 18, 2015

  1. test: do not trigger node bug with fd mapping 

    See nodejs/node#862
    @sam-github
    sam-github committed Feb 18, 2015
    Configuration menu
    Copy the full SHA
    ae8febd View commit details
    Browse the repository at this point in the history

  2. test: fix test-run-metrics after broken refactor 

    It was broken in f65aef4, which stopped passing the metrics arguments
(`runArgs`) to sl-run. With no `--metrics` arguments, no metrics are
reported, and the test started to fail.
    @sam-github
    sam-github committed Feb 18, 2015
    Configuration menu
    Copy the full SHA
    7d7acc4 View commit details
    Browse the repository at this point in the history

Commits on Feb 19, 2015

  1. run: allow profiling to be explicitly started 

    It used to be profiling was only started when StrongOps was started.

This caused problems for metrics and other users of the agent, because
when agent is no started first, it doesn't behave well. In particular,
it doesn't monkey patch anything, causing metrics to be lacking probe
metrics, and agent traces and express records not be available.
    @sam-github
    sam-github committed Feb 19, 2015
    Configuration menu
    Copy the full SHA
    4debc61 View commit details
    Browse the repository at this point in the history