OCCT GitHub Action Workflow Update #276
dpasukhi
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear OCCT community,
The GitHub Action workflow has been updated to provide building validation on:
A full compilation validation cycle is initiated only upon integration of the weekly integration branch (IR) into the master branch.
Each pull request (PR) undergoes DRAWEXE testing grid validation (on public data only) to help validate changes for all users. Note that the OCCT team utilizes an internal testing system that may differ from the GitHub Actions environment and includes commercial data files and tests on our commercial extensions.
GitHub Integration Workflow
Licensing: OCCT is available under the LGPL 2.1 license. To integrate any changes into our repositories, collaborators must sign the Contributor License Agreement (CLA). Details on signing and submitting the CLA are available on the [CONTRIBUTING.md](https://github.com/Open-Cascade-SAS/OCCT/blob/master/.github/CONTRIBUTING.md) page.
Forking: PRs to the OCCT repository are accepted only from external forks. Please create your own fork and work within your repository during development.
PR Submission: Once you have completed your code updates and prepared the final fix, please submit a PR to the OpenCascade OCCT repository using the following templates:
PR Name Template:
<Category(es)> - <Summary description>
PR Description: Should include the following details:
Testing: GitHub PRs have an automatic testing hook on each push to the PR branch. There are 4 stages of validation:
Build: Checks for warnings and successful compilation. If errors occur, the job will fail, and you can check the logs. If successful, you can download the compilation result (artifact
install-*.zip
).Testing: Performs DRAWEXE test grid with over 12k tests. This stage always succeeds; it validates that the tests run without errors. You can download the HTML report with all details (artifact
results-*.zip
).Test Validation: Performs tests for regressions. If errors occur, the job will be marked as failed. All regressions will be compiled into a small HTML report available as an artifact (
results-*-retest.zip
). You can retest this job to regenerate the results, which can help avoid some unstable test cases.Summarization: Always succeeds. This stage updates all
results-*.zip
artifacts with comparisons to the target branch, adding adiff.html
file with image, CPU, and memory differences. It also generates a single archive with each job's result in a single artifact (test-compare-results.zip
).Code review: The OCCT team will review your changes and integrate them into the IR branch and then into the latest master.
Test Suites
For master branch:
For any pull request:
Best regards,
OCCT3d development team.
Beta Was this translation helpful? Give feedback.
All reactions