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

Make --py3 the default for 'wpt' #27081

Merged
merged 1 commit into from Jan 13, 2021
Merged

Conversation

stephenmcgruer
Copy link
Contributor

@stephenmcgruer stephenmcgruer commented Jan 7, 2021

As per
https://github.com/web-platform-tests/rfcs/blob/master/rfcs/py_3.md,
step #2 of the transition to Python 3-only is to make 'wpt ...' commands
run in Python 3 by default.

Passing --py2 will now be necessary to run under Python 2. (Until ~Feb
2021, when we will remove py2 support entirely).

This does affect some CI runs. Cases where they already specified py3
will remain py3. Cases which are designed to run under py2 had --py2
added. Cases that didn't currently specify and aren't version specific
are upgraded from py2 to py3 (one example is Azure Pipelines Mac
infrastructure tests.)

Some Azure Pipelines helper scripts are used for both py2 and py3 tasks.
As a simple way to keep them working, --py2 is used for them as it is
always available.

@stephenmcgruer
Copy link
Contributor Author

stephenmcgruer commented Jan 8, 2021

Started digging into what is necessary for this next step in the RFC. Some interesting discoveries:

  1. We're not running infrastructure/ tests on Py3 on Firefox today, only Chrome! (This PR does not change that, but we should separately address this issue). EDIT: See [Taskcluster] Run Py3 infrastructure/ tests on Firefox as well as Chrome #27104
  2. On Azure, every Py3 task has access to Py2, but not vice-versa. Therefore, for simplicity I've forced the shared scripts (tools/ci/azure/update_hosts.yml and tools/ci/azure/update_manifest.yml) to use py2 for now, rather than add a conditional variable.
  3. I've probably overlooked some tasks; I need to do a pass through tests.yaml and think carefully about whether each one ends up calling wpt [something].

@stephenmcgruer stephenmcgruer force-pushed the smcgruer/flip_py3_flag branch 2 times, most recently from 5da931a to fb628c5 Compare January 12, 2021 02:41
tools/ci/azure/update_hosts.yml Show resolved Hide resolved
tools/ci/azure/update_manifest.yml Show resolved Hide resolved
tools/ci/ci_wptrunner_infrastructure.sh Outdated Show resolved Hide resolved
As per
https://github.com/web-platform-tests/rfcs/blob/master/rfcs/py_3.md,
step #2 of the transition to Python 3-only is to make 'wpt ...' commands
run in Python 3 by default.

Passing --py2 will now be necessary to run under Python 2. (Until ~Feb
2021, when we will remove py2 support entirely).

This does affect some CI runs. Cases where they already specified py3
will remain py3. Cases which are designed to run under py2 had `--py2`
added. Cases that didn't currently specify and aren't version specific
are upgraded from py2 to py3 (one example is Azure Pipelines Mac
infrastructure tests.)

Some Azure Pipelines helper scripts are used for both py2 and py3 tasks.
As a simple way to keep them working, `--py2` is used for them as it is
always available.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants