mirror of
https://github.com/Xahau/xahaud.git
synced 2025-11-04 10:45:50 +00:00
b2bf2b6e6b
* Add instructions to the workflow at the point where the failure would occur, which is where someone experiencing a failure is most likely to look. To keep things simple, the instructions are always printed. The assumption is that if the job succeeds, nobody is likely to look anyway. * Provides the diff of the failure as an artifact, so the user can apply it directly to their repo. * Also update the levelization/README.md to clarify the levels a little bit.
50 lines
1.6 KiB
YAML
50 lines
1.6 KiB
YAML
name: levelization
|
|
|
|
on: [push, pull_request]
|
|
|
|
jobs:
|
|
check:
|
|
runs-on: ubuntu-18.04
|
|
env:
|
|
CLANG_VERSION: 10
|
|
steps:
|
|
- uses: actions/checkout@v2
|
|
- name: Check levelization
|
|
run: Builds/levelization/levelization.sh
|
|
- name: Check for differences
|
|
id: assert
|
|
run: |
|
|
set -o pipefail
|
|
git diff --exit-code | tee "levelization.patch"
|
|
- name: Upload patch
|
|
if: failure() && steps.assert.outcome == 'failure'
|
|
uses: actions/upload-artifact@v2
|
|
continue-on-error: true
|
|
with:
|
|
name: levelization.patch
|
|
if-no-files-found: ignore
|
|
path: levelization.patch
|
|
- name: What happened?
|
|
if: failure() && steps.assert.outcome == 'failure'
|
|
env:
|
|
MESSAGE: |
|
|
If you are reading this, you are looking at a failed Github
|
|
Actions job. That means you changed the dependency relationships
|
|
between the modules in rippled. That may be an improvement or a
|
|
regression. This check doesn't judge.
|
|
|
|
A rule of thumb, though, is that if your changes caused
|
|
something to be removed from loops.txt, that's probably an
|
|
improvement. If something was added, it's probably a regression.
|
|
|
|
To fix it, you can do one of two things:
|
|
1. Download and apply the patch generated as an artifact of this
|
|
job to your repo, commit, and push.
|
|
2. Run './Builds/levelization/levelization.sh' in your repo,
|
|
commit, and push.
|
|
|
|
See Builds/levelization/README.md for more info.
|
|
run: |
|
|
echo "${MESSAGE}"
|
|
exit 1
|