-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
Gym's swan song #9
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe:
|
d211e79
to
2e2470e
Compare
OK, I'm going to patch this out for the moment. We can re-add this once we switch to gymnasium (as @thewchan prepared https://github.com/conda-forge/gymnasium-notices-feedstock already 👍) |
OK, so the segmentation fault I saw in conda-forge/gym-feedstock#29 is still there... 😑 We can try to whittle things down to the various outputs (and then their dependencies), but for now I didn't see a trivial way to just run the test suite for a given extra-package (e.g. Help/input appreciated @pseudo-rnd-thoughts @jkterry1 As mentioned, I can make the artefacts produced in this PR installable locally if that helps with debugging. |
I literally linked that feedstock in my comment... The point was that gym 0.26.1 still expects to find GYM-notices (for PS. In case it's not clear from the name & the content of the PR, this is building gym one last time (the release that's supposedly identical with gymnasium), for continuity with the previous history, and then doing the switch to gymnasium. |
I know I got confused therefore I deleted the comment sorry |
Yes, could you send me the artefacts, I suspect the issue is with rendering as we have a number of rendering-based tests that probably need xvfc |
Hey @pseudo-rnd-thoughts, thanks for your help! The artefacts will be downloadable from azure in the CI of this PR (in the previous run you can also see that the segfaults are only on linux; on osx & win there are some failures that look mostly benign - e.g. there's simply no forking on windows, so those tests will need to be skipped). To install, download the appropriate artefact (for a given platform plus python version), and then do:
Then you can activate the environment and use/test the package as usual.
Is this a test-only dependency, or one of gym/gymnasium itself? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed that you have a windows build however both gym and gymnasium don't officially support it. So we can include it but there might be unknown issues
Also how have you passed all of the tests now?
"cloudpickle >= 1.2.0", | ||
"importlib_metadata >= 4.8.0; python_version < '3.10'", | ||
- "gym_notices >= 0.0.4", | ||
+ # "gym_notices >= 0.0.4", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Update to gymnasium-notices
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please see this comment.
@h-vetinari do you think I should try to get |
I don't think it's worth the effort, but if you feel like doing so, go ahead. :) |
Btw, as the last run shows, we could publish builds if we don't run the test suite. I'm just not very thrilled about having packages that potentially segfault. But it's the state of the packaging we had before, so... In any case, if you could have a glance at the artefacts from this PR (@pseudo-rnd-thoughts @jkterry1) that'd be awesome :) |
@h-vetinari it is now available: https://github.com/conda-forge/gym-notices-feedstock |
@h-vetinari Sorry, yes I can do that. Two things, it looks like 3.7 versions doesn't exist and secondly, I feel very stupid but how do I download the artefact and use it for testing? |
Yes, conda-forge does not build python 3.7 anymore. My last comment contains a direct link to the download page. Choose your platform and a python version, then, on mouse-over, there's a menu that appears at the right-hand side. Download the artefact somewhere, and unpack it. Then do:
|
Hey @h-vetinari, I've been delegated by @pseudo-rnd-thoughts to have a stab at this. I've never used conda before, so I'm pretty unfamiliar with its workflow. Following your steps above, I initially get this:
So instead, I did:
which seemed to work, except it threw this error:
Was this the segfault error that you guys were experiencing? Doesn't seem like it. Do you have any idea what the above errors are referring to or what I need to do to get to the point of seg fault? |
Hey @jjshoots, thanks for your help! It seems you must have forgotten a |
Thanks for the help with the install process. I've actually managed to run all tests on gym with no seg faults save for some minor errors regarding np.bool. |
Hey @jjshoots thanks for testing that's pretty good news - I guess we can go ahead with publishing these builds even without running the tests, but I'd still like to find out why those are segfaulting on our infra, and how to make them pass (or at least skip an appropriate subset, e.g. stuff that cannot pass without an actual screen device). |
@h-vetinari Is there anything preventing us from merging this Also @h-vetinari and @thewchan could you join the gymnasium discord - https://discord.gg/bnJ6kubTg6 then message me PseudoRnd and I can add you as dev to use the conda-dev channel to more discussions |
Well, mainly I've been waiting for people to continue the discussion here (e.g. why the segfaults in the test suite, and whether we want to just ignore them), but with the holiday period I decided to be patient before repinging. Please reread the comments above and respond if you can. Thanks for the invite to the discord; I'll consider it (I'm already drowning in notifications, so I need to be somewhat judicious about whether adding new ones and the signal to noise ratio relative to just packaging gymnasium) |
Hiya @h-vetinari @pseudo-rnd-thoughts - my two cents: I'd vote for merging here. This PR certainly does not make the situation worse than what it currently is, and @jjshoots was able to run the tests locally without issues, so the builds seem fine. We can then look into issues with our build pipeline when packaging the latest version of |
I find the lack of responses... confusing, but whatever, let's do it. |
…nda-forge-pinning 2023.01.07.12.45.19
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( I do have some suggestions for making it better though... For recipe:
|
This needs to wait for conda-forge/feedstock-outputs#41 to be merged. |
Should be fixed by conda-forge/admin-requests#562 |
After picking up the history from https://github.com/conda-forge/gym-feedstock, do one last gym build (picking up changes from conda-forge/gym-feedstock#29), before we switch over to the glorious new world of gymnasium.