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

Reboot the Windows bot #18071

Closed
timvandermeij opened this issue May 12, 2024 · 5 comments
Closed

Reboot the Windows bot #18071

timvandermeij opened this issue May 12, 2024 · 5 comments
Assignees
Labels
release-blocker Blocker for the upcoming release test

Comments

@timvandermeij
Copy link
Contributor

It looks like the Windows bot has crashed. We've seen timeouts of 60 minutes in e.g. #18052 and shortly after the bot didn't respond to commands anymore.

@calixteman Could you perhaps check what happened and reboot it, since not having the bot available is currently blocking some PRs?

@timvandermeij timvandermeij added the release-blocker Blocker for the upcoming release label May 12, 2024
@calixteman
Copy link
Contributor

I restarted the bot this morning (around 8:30 UTC+0).

@timvandermeij
Copy link
Contributor Author

Thanks!

@timvandermeij timvandermeij reopened this May 13, 2024
@timvandermeij
Copy link
Contributor Author

@calixteman Sadly it looks like the Windows bot is down again; see the final comments at #17923. It's strange because the first run failed pretty quickly with what looks like a Git clone timeout and after that a run took over an hour and the logs don't load anymore...

@calixteman
Copy link
Contributor

I just restart the bot.
The error was (the same as the one from this morning):

Error: EPERM: operation not permitted, unlink 'C:\pdfjs\botio-files-pdfjs\private\3ad9ebab6ed3957/node_modules/npm/node_modules/node-gyp/gyp/tools/pretty_sln.py'
    at Object.unlinkSync (node:fs:1808:3)
    at _unlinkSync (C:\Users\Administrator\AppData\Roaming\npm\node_modules\botio\node_modules\shelljs\shell.js:1398:10)
    at rmdirSyncRecursive (C:\Users\Administrator\AppData\Roaming\npm\node_modules\botio\node_modules\shelljs\shell.js:1145:9)
    at rmdirSyncRecursive (C:\Users\Administrator\AppData\Roaming\npm\node_modules\botio\node_modules\shelljs\shell.js:1135:7)
    at rmdirSyncRecursive (C:\Users\Administrator\AppData\Roaming\npm\node_modules\botio\node_modules\shelljs\shell.js:1135:7)
    at rmdirSyncRecursive (C:\Users\Administrator\AppData\Roaming\npm\node_modules\botio\node_modules\shelljs\shell.js:1135:7)
    at rmdirSyncRecursive (C:\Users\Administrator\AppData\Roaming\npm\node_modules\botio\node_modules\shelljs\shell.js:1135:7)
    at rmdirSyncRecursive (C:\Users\Administrator\AppData\Roaming\npm\node_modules\botio\node_modules\shelljs\shell.js:1135:7)
    at rmdirSyncRecursive (C:\Users\Administrator\AppData\Roaming\npm\node_modules\botio\node_modules\shelljs\shell.js:1135:7)
    at C:\Users\Administrator\AppData\Roaming\npm\node_modules\botio\node_modules\shelljs\shell.js:384:7

@timvandermeij
Copy link
Contributor Author

It looks like some process got interrupted and left files behind with invalid permissions. In any case, the cleanup seems to have worked now that the Windows bot is functional again. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release-blocker Blocker for the upcoming release test
Projects
None yet
Development

No branches or pull requests

2 participants