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

Change default Python interpreter to pypy #914

Merged
merged 1 commit into from
Dec 2, 2020

Conversation

pingiun
Copy link
Contributor

@pingiun pingiun commented Nov 10, 2020

We discussed in the slack that the default Python interpreter should be switched to pypy. I believe previously this wasn't done because pypy3 packages weren't readily available. They are now, and it seems many contests are using pypy3 already.

This PR adds pypy3 to the chroot (and leaves python3 in place for contests that want to supply their own runscript for it), and changes the python interpreter in the run script.

@nickygerritsen
Copy link
Member

Hmmm, I think pypy3 does not exist in Debian stable yet? At least CI is complaining and that uses Debian currently.

@pingiun
Copy link
Contributor Author

pingiun commented Nov 10, 2020

@thijskh
Copy link
Member

thijskh commented Nov 10, 2020

The CI uses bionic, not buster, so that must then be bumped to focal (not a bad thing per se)

@nickygerritsen
Copy link
Member

The CI uses bionic, not buster, so that must then be bumped to focal (not a bad thing per se)

Yes Michael and me are trying to fix this

@vmcj
Copy link
Member

vmcj commented Nov 11, 2020

@pingiun in the gitlab.ci file you have to replace the gitlabci:1.0 for gitlab:2.0 also for the Docker in Docker jobs,

But maybe you'll be in luck and my PR is fixed before so you can rebase against it.

@vmcj
Copy link
Member

vmcj commented Nov 19, 2020

@pingiun Master/Main now has the gitlabci:2.0 for all tests, so it should be easier to get this one in a working state. Could you rebase and see if it works?

@pingiun
Copy link
Contributor Author

pingiun commented Nov 21, 2020

Rebased

@thijskh
Copy link
Member

thijskh commented Nov 21, 2020

This test is supposed to fail but now judged as “correct”: https://github.com/DOMjudge/domjudge/blob/master/tests/test-extra-file.py3.zip

@pingiun
Copy link
Contributor Author

pingiun commented Nov 26, 2020

I have no clue why that might be, it seems to have no relation to my change

@thijskh
Copy link
Member

thijskh commented Nov 26, 2020

Yes and no. Your changes expose a bug in the testsuite. So they are triggering the failure, but are not the cause. I propose you rebase on current master to see if your PR then passes.

@thijskh
Copy link
Member

thijskh commented Dec 2, 2020

Merging, thanks for your contribution!

@thijskh thijskh merged commit 75b2dde into DOMjudge:master Dec 2, 2020
vmcj added a commit to vmcj/domjudge that referenced this pull request May 13, 2022
This was kept in DOMjudge#914 but pypy3
has now proven itself so its not needed in the chroot anymore. Keeping
it there might keep people on a 'slower' standard and make their
competition harder than needed.
eldering pushed a commit that referenced this pull request May 17, 2022
This was kept in #914 but pypy3
has now proven itself so its not needed in the chroot anymore. Keeping
it there might keep people on a 'slower' standard and make their
competition harder than needed.
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.

4 participants