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.

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

Run Reporting #6008

Closed
jonathanmorley opened this issue Jan 31, 2023 Discussed in #5954 · 0 comments · Fixed by #6098
Closed

Run Reporting #6008

jonathanmorley opened this issue Jan 31, 2023 Discussed in #5954 · 0 comments · Fixed by #6098
Milestone

Comments

@jonathanmorley
Copy link
Contributor

Discussed in #5954

Originally posted by jonathanmorley January 19, 2023
We run pnpm -r <script name> in our CI runner. While we can time the execution of this command running for in the CI runner, we do not get any visibility in the per-package time taken to run the script.

Another aspect is that if the execution fails during execution, we do not get visibility into 1) the package that failed, 2) the packages that succeeded, 3) the packages that were cancelled, or 4) the packages that were never started

I would like to propose an argument to pnpm run, something like --report=report.json, which would output a json file after execution (including failures) with syntax like:

{
  "package-1": {
    "status": "failure",
    "duration": 1234
  },
  "package-2": {
    "status": "cancelled",
    "duration": 2345
  },
  "package-3": {
    "status": "queued",
    "duration": undefined
  },
  "package-4": {
    "status": "success",
    "duration": "3456"
  }
}
```</div>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants