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

[No need to review, just a CI example] py2->py3: perfmon #5514

Conversation

stephenchengCloud
Copy link
Contributor

This is just an example to show what CI check will fail if we simply move a Python file.

liulinC and others added 25 commits February 2, 2024 10:34
…l in pyproject.toml and make sure it passes pytype checks

Signed-off-by: Fei Su <[email protected]>
…tephenche/CP-47935

py2->py3: hfx_filename
…aster

Resolve python3/Makefile merge conflict

Signed-off-by: Stephen Cheng <[email protected]>
There were no python3 unit tests now.
Set the unit test coverage to 80% for the py3 update.
In the future, if there are cases where the scripts are not UTable
or we can cover them by manual test or XenRT test,
we can handle it by excluding them from the check.

Signed-off-by: Stephen Cheng <[email protected]>
…tephenche/sync_feature_py3_with_master

Sync feature/py3 branch with master
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.

5 participants