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

Add windows to test_python and fix compilation/importing #471

Merged
merged 4 commits into from
Jun 1, 2024

Conversation

ShadowJonathan
Copy link
Contributor

Closes #470

@ShadowJonathan
Copy link
Contributor Author

Github CI is being incredibly annoying, please double-check if all checks were indeed ran, and if it reaches the "Test wheel on all python versions" stage.

@garfieldnate
Copy link
Collaborator

"Test wheel on all python versions" is getting skipped. My guess is that it's because the build-*nix (ubuntu 24.04) step is being skipped. Why that is, I don't know, though!

@ShadowJonathan
Copy link
Contributor Author

Yeah it's because GitHub CI is/was not properly working for a couple of hours. You can hit the re-run button if you want to try it again.

I've gotten it to run properly on my own fork, and I'm now encountering the import error that was encountered in the workshop, and it's a really annoying one to debug and be certain of what's happening.

@ShadowJonathan
Copy link
Contributor Author

We seem to be running into this: actions/runner-images#9959

@ShadowJonathan
Copy link
Contributor Author

I found the problem; #470 (comment)

Apparently, the windows builds are pointing to python39.dll, which shouldn't be the case.

(Also CI will crash on the test file, since apparently you cant print an emoji...)

@ShadowJonathan ShadowJonathan marked this pull request as draft May 30, 2024 09:39
@ShadowJonathan
Copy link
Contributor Author

I'll mark this as draft until I've figured this out.

@ShadowJonathan ShadowJonathan changed the title Add windows to test_python Add windows to test_python and fix compilation/importing May 30, 2024
@ShadowJonathan ShadowJonathan marked this pull request as ready for review May 30, 2024 12:15
@ShadowJonathan
Copy link
Contributor Author

Figured it out; you can check https://github.com/ShadowJonathan/Soar/actions/runs/9302102798/job/25602114115 for a run where it runs without requiring the ubuntu runners.

Unfortunately actions/runner-images#9959 persists, and github hasnt responded to it yet, nor is it visible in https://www.githubstatus.com

I'd recommend keeping an eye on that issue, and re-run the CI once it has been resolved, to see a completely green checkmark list.

@garfieldnate
Copy link
Collaborator

Nice job! How did you fix the cp1252 issue? I've subscribed to updates on the runner issue, and I'll re-run as soon as that's resolved. Thanks for all your work!

@ShadowJonathan
Copy link
Contributor Author

ShadowJonathan commented May 31, 2024

How did you fix the cp1252 issue?

For Python versions 3.7 and up, there's the environment variable PYTHONUTF8 to allow it to output and map unicode characters. For 3.6 and below I had to use PYTHONIOENCODING=utf-8.

Do you want me to add that in comments above the env-variable setting?

@garfieldnate
Copy link
Collaborator

Ah, right! I had thought that setting was there already. Makes sense. I guess a comment is a good idea.

The runner issue has been resolved, as well, so I'm re-running the jobs for this PR.

@ShadowJonathan
Copy link
Contributor Author

Added the comment :)

@ShadowJonathan
Copy link
Contributor Author

Grrr there's a flake on testSpreadingActivation, apparantly

@garfieldnate
Copy link
Collaborator

That does sound familiar. I thought I had seen a flakey test recently and recorded it but I can't find a note. I'll add something to #385.

@garfieldnate garfieldnate merged commit bdf5f02 into SoarGroup:development Jun 1, 2024
40 checks passed
@garfieldnate
Copy link
Collaborator

Merged! Thanks, Jonathan!

@ShadowJonathan
Copy link
Contributor Author

ShadowJonathan commented Jun 1, 2024

Thanks!

I've deleted the windows wheel on the only available release on pypi just now, and will send an email monday to all the workshop participants who reached out with their email to explain to them the issue is (most likely) fixed, and to install it via test.pypi.org, once the automatic monday build has rolled around and uploaded it :)

This prevents anyone from downloading a broken wheel, but also makes soar-sml uninstallable for windows users (for now), with .3 being the next version which has that wheel.

Currently I don't think the situation is that speedy to require uploading more dev artifacts to pypi to fill pre-release needs, since .3 is around the corner(ish), so i think we can bear with that for now.

If .3 will take a few more months, however, then that might change.

@garfieldnate
Copy link
Collaborator

I don't believe that it will take months, but I need to coordinate a bit to determine the timing. I'll let you know when I find out.

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.

[Python] Windows version testing is not included in test_python
2 participants