No more CI Reliability report since 4 days ago

[F3n67u]

The last CI Reliability report is 06-29, 4 days ago. 06-30, 07-01, 07-02 is absent.

@richardlau could you help to take a look?

[targos]

End of the logs from https://github.com/nodejs/reliability/runs/7165313876?check_suite_focus=true:

2022-07-03T00:18:30.2074274Z --------------------------------- Other builds ---------------------------------
2022-07-03T00:18:30.2074823Z Unstable   https://ci.nodejs.org/job/node-test-commit-osx/45875/
2022-07-03T00:18:30.2075370Z --------------------------------------------------------------------------------
2022-07-03T00:18:30.2075912Z [87/89] Running https://ci.nodejs.org/job/node-test-pull-request/44957/
2022-07-03T00:18:30.2076461Z --------------------------------------------------------------------------------
2022-07-03T00:18:30.2076950Z - Querying data for job/node-test-pull-request/44957/
2022-07-03T00:18:30.4374583Z ✔  Build data downloaded
2022-07-03T00:18:30.4375090Z - Querying failures of job/node-test-commit/54550/
2022-07-03T00:18:31.1725844Z TypeError: Cannot read properties of null (reading '1')
2022-07-03T00:18:31.1726616Z     at new JSTestFailure (file:///opt/hostedtoolcache/node/16.15.1/x64/lib/node_modules/node-core-utils/lib/ci/ci_failure_parser.js:78:62)
2022-07-03T00:18:31.1727317Z     at file:///opt/hostedtoolcache/node/16.15.1/x64/lib/node_modules/node-core-utils/lib/ci/ci_failure_parser.js:168:16
2022-07-03T00:18:31.1727703Z     at Array.map (<anonymous>)
2022-07-03T00:18:31.1728280Z     at filter (file:///opt/hostedtoolcache/node/16.15.1/x64/lib/node_modules/node-core-utils/lib/ci/ci_failure_parser.js:167:29)
2022-07-03T00:18:31.1729023Z     at CIFailureParser.parse (file:///opt/hostedtoolcache/node/16.15.1/x64/lib/node_modules/node-core-utils/lib/ci/ci_failure_parser.js:296:22)
2022-07-03T00:18:31.1729775Z     at TestRun.parseConsoleText (file:///opt/hostedtoolcache/node/16.15.1/x64/lib/node_modules/node-core-utils/lib/ci/build-types/job.js:93:26)
2022-07-03T00:18:31.1730507Z     at runMicrotasks (<anonymous>)
2022-07-03T00:18:31.1730971Z     at processTicksAndRejections (node:internal/process/task_queues:96:5)
2022-07-03T00:18:31.1731319Z     at async Promise.all (index 13)
2022-07-03T00:18:31.1732021Z     at async CommitBuild.getResults (file:///opt/hostedtoolcache/node/16.15.1/x64/lib/node_modules/node-core-utils/lib/ci/build-types/commit_build.js:106:25)
2022-07-03T00:18:31.1841036Z ##[error]Process completed with exit code 1.

[F3n67u]

It is recovered now. don't know why.😅

[richardlau]

The workflow runs ncu-ci pr walk pr, which looks at the 100 most recent node-test-pull-request CI runs

reliability/.github/workflows/reliability_report.yml

Lines 21 to 25 in 506849d

	- run: npm i -g node-core-utils
	- run: ncu-config --global set jenkins_token ${{ secrets.JENKINS_TOKEN }}
	- run: ncu-config --global set token ${{ secrets.USER_TOKEN }}
	- run: ncu-config --global set username ${{ secrets.USER_NAME }}
	- run: ncu-ci walk pr --stats=true --markdown $PWD/results.md

(See https://github.com/nodejs/node-core-utils#setting-up-jenkins-credentials if you want to try running ncu-ci yourself.)

From the quoted log it would appear that node-core-utils was unable to parse one of the sub-jobs of job/node-test-commit/54550/ -- presumably the workflow starting working again once enough new CI runs happened to push that job outside the most recent 100.

[F3n67u]

The workflow runs ncu-ci pr walk pr, which looks at the 100 most recent node-test-pull-request CI runs

reliability/.github/workflows/reliability_report.yml

Lines 21 to 25 in 506849d

	- run: npm i -g node-core-utils
	- run: ncu-config --global set jenkins_token ${{ secrets.JENKINS_TOKEN }}
	- run: ncu-config --global set token ${{ secrets.USER_TOKEN }}
	- run: ncu-config --global set username ${{ secrets.USER_NAME }}
	- run: ncu-ci walk pr --stats=true --markdown $PWD/results.md

(See https://github.com/nodejs/node-core-utils#setting-up-jenkins-credentials if you want to try running ncu-ci yourself.)
From the quoted log it would appear that node-core-utils was unable to parse one of the sub-jobs of job/node-test-commit/54550/ -- presumably the workflow starting working again once enough new CI runs happened to push that job outside the most recent 100.

I don't know that before. Thanks for your info. I thought only collaborators could have Jenkins credentials. I am wrong.

[F3n67u]

I could reproduce this problem now. I create a issue at nodejs/node-core-utils. so I close this issue in favor of nodejs/node-core-utils#639.