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

CI: Enhance error handling in Azure Pipelines #26335

Closed
wants to merge 2 commits into from
Closed

Conversation

morkev
Copy link

@morkev morkev commented Apr 23, 2024

Enhance error handling in Azure Pipelines by adding verbose logging, implementing continueOnError for non-critical steps, and improving condition checks and alerts for more robust CI/CD operations.

…:: continueOnError

Enhances error handling in Azure Pipelines by adding verbose logging, implementing continueOnError for non-critical steps, and improving condition checks and alerts for more robust CI/CD operations.
Copy link
Author

@morkev morkev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ensures that all 'git' submodules are fetched and initialized before the build and test steps commence, this update guarantees that all necessary code dependencies are present and up-to-date.

@morkev morkev changed the title Enhances error handling in Azure Pipelines by adding verbose logging … Enhances error handling in Azure Pipelines Apr 23, 2024
@charris charris changed the title Enhances error handling in Azure Pipelines CI: Enhance error handling in Azure Pipelines May 8, 2024
@morkev
Copy link
Author

morkev commented May 22, 2024

Hi @charris . Any chance this can get merged, or should we just close the PR? Thank you so much.

Copy link
Member

@mattip mattip left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes to azure-steps-windows.yml are not needed. This is a template, it is injected into the azure-pipelines.yml file so should not have a trigger and stages stanza.

Is there some deeper motivation for this PR: is there an issue or problem it comes to solve?

pr:
branches:
include:
- '*' # must quote since "*" is a YAML reserved character; we want a string

- '*' # All branches for PRs
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unindent?

@@ -50,8 +46,7 @@ stages:
- script: >-
python -m pip install -r requirements/linter_requirements.txt
displayName: 'Install tools'
# pip 21.1 emits a pile of garbage messages to annoy users :)
# failOnStderr: true
continueOnError: true
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand. How can the lint job succeed if the tools are not installed?

docker run -v $(pwd):/numpy -e CFLAGS="-msse2 -std=c99 -UNDEBUG" \
-e F77=gfortran-5 -e F90=gfortran-5 quay.io/pypa/manylinux2014_i686 \
/bin/bash -xc "source /numpy/tools/ci/run_32_bit_linux_docker.sh"
displayName: 'Run 32-bit manylinux2014 Docker Build / Tests'
continueOnError: true # Consider whether to allow continuation on error
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This seems wrong. If the tests fail, the job should fail

@mattip
Copy link
Member

mattip commented May 30, 2024

@morkev will you be continuing with this?

@morkev
Copy link
Author

morkev commented May 31, 2024

@mattip Hi, thanks for tagging me. As you mentioned earlier, this PR does not solve any particular issue, and I would like to contribute with something better. For the exception part, I agree - why catch an error if you can’t handle it. The indentation was probably a mistake from the IDE, would only change if it’s better based on PEP 8 style guide.

@morkev morkev closed this May 31, 2024
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.

None yet

2 participants