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

Trying to fix pylint errors #103

Merged
merged 3 commits into from
Aug 22, 2024
Merged

Trying to fix pylint errors #103

merged 3 commits into from
Aug 22, 2024

Conversation

Joao-L-S-Almeida
Copy link
Member

No description provided.

Signed-off-by: João Lucas de Sousa Almeida <joao.l.sa.9.3@gmail.com>
@Joao-L-S-Almeida
Copy link
Member Author

Hi @romeokienzler I followed the recommendation from here: actions/starter-workflows#2303
to circumvent the pylint issue. We could also could upload the lint outputs as an artifact.

@Joao-L-S-Almeida Joao-L-S-Almeida self-assigned this Aug 7, 2024
@Joao-L-S-Almeida
Copy link
Member Author

However, Dynamic code analysis have ran forever.

@Joao-L-S-Almeida Joao-L-S-Almeida marked this pull request as ready for review August 8, 2024 12:33
Signed-off-by: João Lucas de Sousa Almeida <joao.l.sa.9.3@gmail.com>
Signed-off-by: João Lucas de Sousa Almeida <joao.l.sa.9.3@gmail.com>
@Joao-L-S-Almeida
Copy link
Member Author

@romeokienzler I temporarily disabled the Dynamic code analysis and printed the pylint logs. I believe this is the ideal pipeline for the moment.

@Joao-L-S-Almeida
Copy link
Member Author

The pytest pipelines fail because the "mmcv._ext" issue from the man branch.

@romeokienzler romeokienzler merged commit ffc431a into main Aug 22, 2024
3 of 5 checks passed
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.

2 participants