Skip to content

Navigation Menu

Appearance settings

View all features
- BY COMPANY SIZE
  Enterprises
  Small and medium teams
  Startups
  Nonprofits
- BY USE CASE
  App Modernization
  DevSecOps
  DevOps
  CI/CD
  View all use cases
- BY INDUSTRY
  Healthcare
  Financial services
  Manufacturing
  Government
  View all industries
View all solutions
- EXPLORE BY TOPIC
  AI
  Software Development
  DevOps
  Security
  View all topics
- EXPLORE BY TYPE
  Customer stories
  Events & webinars
  Ebooks & reports
  Business insights
  GitHub Skills
- SUPPORT & SERVICES
  Documentation
  Customer support
  Community forum
  Trust center
  Partners
- COMMUNITY
  GitHub SponsorsFund open source developers
- PROGRAMS
  Security Lab
  Maintainer Community
  Accelerator
  Archive Program
- REPOSITORIES
  Topics
  Trending
  Collections
- ENTERPRISE SOLUTIONS
  Enterprise platformAI-powered developer platform
- AVAILABLE ADD-ONS
  GitHub Advanced SecurityEnterprise-grade security features
  Copilot for BusinessEnterprise-grade AI features
  Premium SupportEnterprise-grade 24/7 support
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

Appearance settings

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

NCAR / ccpp-framework Public

Notifications You must be signed in to change notification settings
Fork 65
Star 26

Code
Issues 57
Pull requests 3
Discussions
Actions
Projects 1
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Wiki
Security
Insights

Handle and test xmllint versions that return a zero exit code even if validation fails#708

Merged

mkavulich merged 4 commits intoNCAR:developNCAR/ccpp-framework:developfrom

climbfuji:feature/xmllint_wrapperclimbfuji/ccpp-framework:feature/xmllint_wrapperCopy head branch name to clipboard

Dec 18, 2025

Conversation Commits4 (4)Checks Files changed

Merged

Handle and test xmllint versions that return a zero exit code even if validation fails#708
mkavulich merged 4 commits intoNCAR:developfrom
climbfuji:feature/xmllint_wrapper

Commits

Commits on Dec 12, 2025

Create test/unit_tests/xmllint_wrapper/xmllint wrapper that emulates behavior of bad xmllint which returns a zero exit code even if the validation fails
climbfuji
committed
In scripts/parse_tools/xml_tools.py, handle xmllint versions that return a zero exit code even if the validation fails; simply logic and update test/unit_tests/test_sdf.py accordingly
climbfuji
committed
Run doctest together with pytest so that xmllint is available
climbfuji
committed

Commits on Dec 17, 2025

Merge branch 'develop' into feature/xmllint_wrapper
climbfuji
authored

Footer

© 2026 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Community
Docs
Contact

You can’t perform that action at this time.