ScaCap/action-surefire-report

Issues

• Only create annotations for forked pr

  #235 opened 2 months ago by gilesw
  0

• Possibility to exclude flaky tests from report

  #226 opened 3 months ago by rigazilla
  1

• When run on `workflow_dispatch`, no `Test Report` appears

  #199 opened a year ago by lobodpav
  7

• Update to Node.js 20

  #202 opened 10 months ago by JPowell-AA
  5

• Not always publish report

  #75 opened 3 years ago by blackdevil22
  6

• Maven failsafe plugin reports parsing fails: [Error: Cannot read properties of undefined (reading 'testsuite')]

  #184 opened a year ago by dejan-stojadinovic
  5

• Resource not accessible by integration when using from fork PRs

  #31 opened 4 years ago by rchiodo
  10

• Error: Validation Failed

  #161 opened a year ago by arcuri82
  4

• Error: Bad credentials by using v1.7.0 in private/enterprise github repo

  #156 opened 2 years ago by DietK
  1

• Documentation lacking on github token permissions

  #153 opened 2 years ago by Megagyger
  2

• Report check item appears under the wrong workflow name

  #39 opened 4 years ago by jamesdh
  8

• v1.6.1 broke running action on macOS and Windows

  #146 opened 2 years ago by joschi
  3

• Error: Sequence ']]>' not allowed in content

  #143 opened 2 years ago by ghaiszaher
  3

• Error: internal error: Huge input lookup

  #145 opened 2 years ago by thomas0306
  3

• New release v1.6.0 error loading shared library

  #140 opened 2 years ago by Ajris
  12

• Annotation shows wrong class path on multi-module project

  #84 opened 2 years ago by leonarta
  2

• Add support for Github Enterprise

  #125 opened 2 years ago by yeikel
  0

• "View more details on GitHub Actions" should point to the raw build logs instead of the check results

  #131 opened 2 years ago by yeikel
  0

• Execute `npm run package` automatically

  #130 opened 2 years ago by yeikel
  1

• Various security vulnerabilities

  #123 opened 2 years ago by yeikel
  4

• Error: request to https://api.github.com/repos/xxx/check-runs failed, reason: tunneling socket could not be established, statusCode=407

  #91 opened 2 years ago by liu-shaojun
  1

• Upgrade to Node.js 16

  #113 opened 2 years ago by tommens
  2

• Report shows failure of previous build

  #21 opened 4 years ago by jameskleeh
  6

• This repo appears to have been abandoned

  #98 opened 2 years ago by pdehlke
  1

• Update default runtime to Node 16

  #85 opened 2 years ago by kwin
  6

• Update to actions/core@v1.10.0

  #94 opened 2 years ago by mrmeyers99
  1

• TypeError: undefined is not iterable (cannot read property Symbol(Symbol.iterator)) on Mac OS runner

  #95 opened 2 years ago by kwin
  0

• JavaScript heap out of memory

  #17 opened 4 years ago by dwayneyuen
  7

• Document the necessary scopes of ${{ secrets.GITHUB_TOKEN }}

  #36 opened 4 years ago by nikwerhypoport
  4

• I got "Parameter token or opts.auth is required" at the end of run.

  #63 opened 4 years ago by xw185019-ncr
  3

• No tests found when gradle cache entry is used

  #80 opened 3 years ago by huehnerlady
  2

• Have the logs use the error annotation format

  #60 opened 4 years ago by jamie-wearsafe
  5

• Provide access to test <system-out>

  #73 opened 3 years ago by brenuart
  1

• Add option to skip publishing in case all tests were green

  #72 opened 3 years ago by kwin
  2

• How to publish separate reports for maven-surefire-plugin and maven-failsafe-plugin

  #71 opened 3 years ago by kwin
  1

• Proper usage with matrix builds

  #70 opened 4 years ago by kwin
  1

• Feature request - Ability to skip publishing report

  #57 opened 4 years ago by devinrsmith
  1

• The same workflow for `push` and `pull_request` doesn't produce "Test Report" when run on `pull_request`

  #50 opened 4 years ago by skarakhanov
  4

• Line number for check failure is wrong.

  #47 opened 4 years ago by mustaphazorgati
  8

• "No test results found!" after some time or after new run?

  #53 opened 4 years ago by famod
  4

• Support for event 'workflow_dispatch'

  #48 opened 4 years ago by pun-ky
  8

• Fails on `testcase`

  #19 opened 4 years ago by kobrikx
  3

• Cannot parse surefire-report XML

  #43 opened 4 years ago by mustaphazorgati
  2

• Instead of recommending `maven.test.failure.ignore`, use always() for publish test reports

  #41 opened 4 years ago by ivangreene
  1

• Bazel test reports can't be parsed

  #25 opened 4 years ago by iuliand-db
  3

• Make no-JUnit test file case as successful case with a warning

  #29 opened 4 years ago by HyukjinKwon
  3

• Failsafe

  #18 opened 4 years ago by paulius-p
  0

• [bug] Cannot parse report from jest junit

  #30 opened 4 years ago by kuritz
  1

• It should be possible to fail the build on test failures

  #22 opened 4 years ago by hennejg
  5

• Downstream workflow steps should be able to use the test outcome

  #23 opened 4 years ago by hennejg
  1