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

tutorial test failing #232

Closed
McHaillet opened this issue Oct 16, 2024 · 5 comments
Closed

tutorial test failing #232

McHaillet opened this issue Oct 16, 2024 · 5 comments

Comments

@McHaillet
Copy link
Collaborator

Tutorial test is failing on the main branch:

https://github.com/SBC-Utrecht/pytom-match-pick/actions/runs/11368748316/job/31625082457

It fails on pytom_create_template but I am fairly certain that I did not touch that code in my latest PR, so its unclear to me what is going on.

@sroet
Copy link
Collaborator

sroet commented Oct 16, 2024

Yeah, it already failed last weekend as well on the scheduled test, and did not come up with a restart. I am looking if I can reproduce the issue outside of docker.

@McHaillet
Copy link
Collaborator Author

Ah, I missed that one! Thanks for having a look

@sroet
Copy link
Collaborator

sroet commented Oct 22, 2024

Alright:

  1. it does not fail outside of the container on the same machine
  2. in [DO NOT MERGE] Update tutorial-tests.yml #234 I forced all packages to be identical between the last successful tutorial run and the next and it still fails. Which means it doesn't seem to be any python package.

However I did notice the following in our runner logs:

2024-10-06 00:44:40Z: Running job: test-tutorial
2024-10-06 02:26:07Z: Job test-tutorial completed with result: Succeeded
2024-10-06 02:26:09Z: Running job: test_suite
2024-10-06 02:29:23Z: Job test_suite completed with result: Succeeded
2024-10-07 16:06:11Z: Runner connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
2024-10-07 16:07:20Z: Runner reconnected.
Runner update in progress, do not shutdown runner.
Downloading 2.320.0 runner
Waiting for current job finish running.
Generate and execute update script.
Runner will exit shortly for update, should be back online within 10 seconds.
Runner update process finished.
Runner listener exit because of updating, re-launch runner after successful update
Update finished successfully.
Restarting runner...

√ Connected to GitHub

Current runner version: '2.320.0'
2024-10-07 20:45:48Z: Listening for Jobs
2024-10-07 21:51:31Z: Runner connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
2024-10-07 21:52:48Z: Runner reconnected.
2024-10-08 07:12:04Z: Runner connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
2024-10-08 07:13:23Z: Runner reconnected.
2024-10-08 15:46:21Z: Runner connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
2024-10-08 15:47:32Z: Runner reconnected.
2024-10-09 13:25:44Z: Runner connect error: The HTTP request timed out after 00:01:00.. Retrying until reconnected.
2024-10-09 13:26:52Z: Runner reconnected.
2024-10-11 21:07:23Z: Runner connect error: The HTTP request timed out after 00:01:40.. Retrying until reconnected.
2024-10-13 00:44:26Z: Running job: test-tutorial
2024-10-13 00:47:24Z: Job test-tutorial completed with result: Failed

With no commits coming from us between october 2nd (2f5bb47) and october 16 (b8a80a3) it seems to come from the runner update. I will make an issue on their tracker for it

@McHaillet
Copy link
Collaborator Author

Nice work on finding that possible runner update. Seems quite a nasty bug.

@sroet
Copy link
Collaborator

sroet commented Oct 31, 2024

As of last weekend, the tutorial test on main runs again, no clue what changed in the end...

@sroet sroet closed this as completed Oct 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants