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

update 2023-03-16 #355

Closed
wants to merge 0 commits into from
Closed

update 2023-03-16 #355

wants to merge 0 commits into from

Conversation

kba
Copy link
Member

@kba kba commented Mar 16, 2023

No description provided.

@stweil
Copy link
Collaborator

stweil commented Mar 16, 2023

I noticed yesterday that make all fails with Ubuntu 18.04 and any Python version, see CI protocol for a job based on this PR. The CI jobs hang and always print the same message until they get canceled:

parallel: Warning: Semaphore stuck for 30 seconds. Consider using --semaphoretimeout.

Newer Ubuntu versions don't show this issue. Is Ubuntu 18.04 still relevant, or should we remove it from CI now?

@kba kba closed this Mar 16, 2023
@kba kba force-pushed the update-2023-03-16 branch from 0c67092 to 209b533 Compare March 16, 2023 16:50
@bertsky
Copy link
Collaborator

bertsky commented Mar 16, 2023

There seems to be a problem with that dinglehopper commit.

Also, CI failure on master looks like we have to hold numpy for ocrd_keraslm. Just pushed fix there 🤞

@kba
Copy link
Member Author

kba commented Mar 16, 2023

Wow, GH closes a PR if you force-push the only commit and does not allow reopening. Not sure whether this is new behavior but it certainly is annoying.

Is Ubuntu 18.04 still relevant, or should we remove it from CI now?

No, it is not and yes we should.

@kba kba deleted the update-2023-03-16 branch March 16, 2023 16:54
@kba
Copy link
Member Author

kba commented Mar 16, 2023

Argh, my bad, I accidentally amended a commit that was in master m-(. Force-push and new PR incoming, sry about that.

@bertsky
Copy link
Collaborator

bertsky commented Mar 16, 2023

Also, CI failure on master looks like we have to hold numpy for ocrd_keraslm. Just pushed fix there

ah, of course we are screwed there:

Operating System: Ubuntu 20.04.5 LTS
 OSType: linux
 Architecture: x86_64

Starting container ocrd/core
...
ERROR: Could not find a version that satisfies the requirement tensorflow-gpu==1.15.* (from versions: 2.2.0, 2.2.1, 2.2.2, 2.2.3, 2.3.0, 2.3.1, 2.3.2, 2.3.3, 2.3.4, 2.4.0, 2.4.1, 2.4.2, 2.4.3, 2.4.4, 2.5.0, 2.5.1, 2.5.2, 2.5.3, 2.6.0, 2.6.1, 2.6.2, 2.6.3, 2.6.4, 2.6.5, 2.7.0rc0, 2.7.0rc1, 2.7.0, 2.7.1, 2.7.2, 2.7.3, 2.7.4, 2.8.0rc0, 2.8.0rc1, 2.8.0, 2.8.1, 2.8.2, 2.8.3, 2.8.4, 2.9.0rc0, 2.9.0rc1, 2.9.0rc2, 2.9.0, 2.9.1, 2.9.2, 2.9.3, 2.10.0rc0, 2.10.0rc1, 2.10.0rc2, 2.10.0rc3, 2.10.0, 2.10.1, 2.11.0rc0, 2.11.0rc1, 2.11.0rc2, 2.11.0, 2.12.0)

@stweil
Copy link
Collaborator

stweil commented Mar 16, 2023

No, it is not and yes we should.

18.04 is still used in CircleCI. Does that need a change, too? I can prepare a PR for the rest.

And should Python 3.6 also be removed?

@bertsky
Copy link
Collaborator

bertsky commented Mar 16, 2023

ah, of course we are screwed there:

although py38 should still be covered by our nvidia-tensorflow workaround. Investigating...

@kba kba mentioned this pull request Mar 16, 2023
@kba
Copy link
Member Author

kba commented Mar 16, 2023

There seems to be a problem with that dinglehopper commit.

Yeah, I was in the wrong branch, is now fixed.

18.04 is still used in CircleCI. Does that need a change, too? I can prepare a PR for the rest.

Yes, but unless that is a breaking issue now, let's do it after this update.

And should Python 3.6 also be removed?

I'd say not right now, but in the next release?

@stweil
Copy link
Collaborator

stweil commented Mar 16, 2023

So the pull requests #357 and #358 can included.

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

Successfully merging this pull request may close these issues.

3 participants