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
java.io.FileNotFoundException: /var/lib/jenkins/jobs/post-build-status-update/builds/2261443/log (No such file or directory) at java.base/java.io.RandomAccessFile.open0(Native Method)...
I'll see if I can find it on the Jenkins server (I think they get compressed there).
-- Logs begin at Tue 2024-05-14 10:38:04 UTC, end at Tue 2024-05-14 13:02:12 UTC. --
May 14 10:38:04 infra-rackspace-debian8-x64-1 systemd[1]: Stopping github-bot...
May 14 10:38:04 infra-rackspace-debian8-x64-1 systemd[1]: Starting github-bot...
May 14 10:38:04 infra-rackspace-debian8-x64-1 systemd[1]: Started github-bot.
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: internal/modules/cjs/loader.js:883
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: throw err;
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: ^
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: Error: Cannot find module 'node:path'
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: Require stack:
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: - /home/iojs/github-bot/node_modules/path-scurry/dist/commonjs/index.js
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: - /home/iojs/github-bot/node_modules/glob/dist/commonjs/glob.js
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: - /home/iojs/github-bot/node_modules/glob/dist/commonjs/index.js
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: - /home/iojs/github-bot/server.js
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: at Function.Module._load (internal/modules/cjs/loader.js:725:27)
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: at Module.require (internal/modules/cjs/loader.js:952:19)
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: at require (internal/modules/cjs/helpers.js:88:18)
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: at Object.<anonymous> (/home/iojs/github-bot/node_modules/path-scurry/dist/commonjs/index.js:28:21)
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: at Module._compile (internal/modules/cjs/loader.js:1063:30)
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: at Module.load (internal/modules/cjs/loader.js:928:32)
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: at Function.Module._load (internal/modules/cjs/loader.js:769:14)
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: at Module.require (internal/modules/cjs/loader.js:952:19) {
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: code: 'MODULE_NOT_FOUND',
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: requireStack: [
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: '/home/iojs/github-bot/node_modules/path-scurry/dist/commonjs/index.js',
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: '/home/iojs/github-bot/node_modules/glob/dist/commonjs/glob.js',
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: '/home/iojs/github-bot/node_modules/glob/dist/commonjs/index.js',
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: '/home/iojs/github-bot/server.js'
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: ]
May 14 10:38:05 infra-rackspace-debian8-x64-1 node[14484]: }
May 14 10:38:05 infra-rackspace-debian8-x64-1 systemd[1]: github-bot.service: main process exited, code=exited, status=1/FAILURE
May 14 10:38:05 infra-rackspace-debian8-x64-1 systemd[1]: Unit github-bot.service entered failed state.
which is #3214 and the inability to update Node.js there until we update the OS all over again.
If upgrading to Node.js 14.18 or later is trouble, and even if it's not, a quick fix would be to revert the glob update.
Oops, probably not because the bot will still install the latest glob and this was introduced in a patch release. I'll open a PR to pin glob instead, which isn't great, but will fix things if the Node.js upgrade isn't something that can happen quickly.
Hmm, pinning glob doesn't seem to have fixed it. I'm not sure how to look at the log file to confirm that glob is still the problem, but I'll reopen this.
Is the machine still in sync with its playbook? If it's not, I suggest we remove the Node.js installed via apt and instead just download it from nodejs.org and extract it to /usr/local
Is the machine still in sync with its playbook? If it's not, I suggest we remove the Node.js installed via apt and instead just download it from nodejs.org and extract it to /usr/local
I've downloaded Node.js 14.21.3 onto the machine and extracted it to /usr/local. Had to edit /lib/systemd/system/github-bot.service so that it used /usr/local/bin/node instead of /usr/bin/node. It looks like the bot has now been able to start:
root@infra-rackspace-debian8-x64-1:/home/iojs# systemctl status github-bot● github-bot.service - github-bot Loaded: loaded (/lib/systemd/system/github-bot.service; enabled) Active: active (running) since Wed 2024-05-15 17:52:29 UTC; 1s ago Main PID: 19176 (node) CGroup: /system.slice/github-bot.service └─19176 /usr/local/bin/node server.jsMay 15 17:52:29 infra-rackspace-debian8-x64-1 systemd[1]: Started github-bot.May 15 17:52:29 infra-rackspace-debian8-x64-1 node[19176]: {"name":"bot","hostname":"infra-rackspace-debian8-x64-1","pid":19176,"level":30,"msg":"Loading: ./scripts/ping.js","time":"2024-05-15T1...591Z","v":0}May 15 17:52:29 infra-rackspace-debian8-x64-1 node[19176]: {"name":"bot","hostname":"infra-rackspace-debian8-x64-1","pid":19176,"level":30,"msg":"Loading: ./scripts/node-ping-owners.js","time":"...595Z","v":0}May 15 17:52:29 infra-rackspace-debian8-x64-1 node[19176]: {"name":"bot","hostname":"infra-rackspace-debian8-x64-1","pid":19176,"level":30,"msg":"Loading: ./scripts/jenkins-status.js","time":"20...687Z","v":0}May 15 17:52:29 infra-rackspace-debian8-x64-1 node[19176]: {"name":"bot","hostname":"infra-rackspace-debian8-x64-1","pid":19176,"level":30,"msg":"Loading: ./scripts/event-relay.js","time":"2024-...688Z","v":0}May 15 17:52:29 infra-rackspace-debian8-x64-1 node[19176]: {"name":"bot","hostname":"infra-rackspace-debian8-x64-1","pid":19176,"level":30,"msg":"Listening on port 3333","time":"2024-05-15T17:52...693Z","v":0}Hint: Some lines were ellipsized, use -l to show in full.root@infra-rackspace-debian8-x64-1:/home/iojs#
Activity
richardlau commentedon May 14, 2024
post-build-status-update at first glance looks green, but clicking on the jobs and looking at the "Pipeline steps", e.g. https://ci.nodejs.org/job/post-build-status-update/2261443/flowGraphTable/, shows that the "httpRequest" step failed.

The console output can't find the build log, e.g.
I'll see if I can find it on the Jenkins server (I think they get compressed there).
richardlau commentedon May 14, 2024
On
ci:From the uncompressed log:
richardlau commentedon May 14, 2024
The bot isn't running -- on
gh-bot:richardlau commentedon May 14, 2024
From
journalctlwhich is #3214 and the inability to update Node.js there until we update the OS all over again.
targos commentedon May 14, 2024
nodejs/github-bot@c5ba723
Landed 18 hours ago.
targos commentedon May 14, 2024
Can't we update Node.js to 14.21.3 (the last 14.x version), or at least 14.18? isaacs/node-glob@57f5551
Trott commentedon May 14, 2024
Oof, sorry I did this with that
globupdate. That sure seemed safe.... 🥴Trott commentedon May 14, 2024
If upgrading to Node.js 14.18 or later is trouble, and even if it's not, a quick fix would be to revert the
globupdate.Revert "build(deps): bump glob from 10.3.12 to 10.3.15 (#509)"
Trott commentedon May 14, 2024
Oops, probably not because the bot will still install the latest
globand this was introduced in a patch release. I'll open a PR to pinglobinstead, which isn't great, but will fix things if the Node.js upgrade isn't something that can happen quickly.fix: pin glob to 10.3.4
Trott commentedon May 14, 2024
nodejs/github-bot#511 for a temporary workaround
richardlau commentedon May 14, 2024
FWIW
apt updateoffers no update or newer verson of Node.js 14.fix: pin glob to 10.3.4 (#511)
Trott commentedon May 15, 2024
Hmm, pinning
globdoesn't seem to have fixed it. I'm not sure how to look at the log file to confirm thatglobis still the problem, but I'll reopen this.targos commentedon May 15, 2024
Is the machine still in sync with its playbook? If it's not, I suggest we remove the Node.js installed via
aptand instead just download it fromnodejs.organd extract it to/usr/localfix: pin glob to 10.3.12
fix: pin glob to 10.3.12
fix: pin glob to 10.3.12 (#512)
richardlau commentedon May 15, 2024
hmm. bot is still failing to start.
It seems like the deployment still has path-scurry 1.11.1 installed.
Maybe trying to get a manual Node.js 14 installed as a temporary solution would be worth pursuing.
richardlau commentedon May 15, 2024
I've downloaded Node.js 14.21.3 onto the machine and extracted it to
/usr/local. Had to edit/lib/systemd/system/github-bot.serviceso that it used/usr/local/bin/nodeinstead of/usr/bin/node. It looks like the bot has now been able to start:richardlau commentedon May 15, 2024
httpRequest step in the pipeline (see #3720 (comment)) is passing now and I can see status checks being posted back to PRs.
Trott commentedon May 20, 2024
@richardlau Should we land nodejs/github-bot#514 and keep an eye on things?