fix: compatibility with fmt lib #223
Workflow file for this run
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
name: Pull Request | |
on: | |
pull_request: | |
jobs: | |
build: | |
uses: ./.github/workflows/build.yml | |
with: | |
buildtype: debug | |
clang-tidy: | |
needs: | |
- build | |
uses: ./.github/workflows/clang-tidy.yml | |
clang-format: | |
needs: | |
- build | |
uses: ./.github/workflows/clang-format.yml | |
comment: | |
name: Bot comment | |
needs: | |
- build | |
- clang-tidy | |
- clang-format | |
runs-on: ubuntu-latest | |
if: always() | |
steps: | |
- uses: thollander/actions-comment-pull-request@v2 | |
with: | |
comment_tag: bot_comment | |
mode: recreate | |
message: | | |
## :arrow_right: Commit ${{ github.event.pull_request.head.sha }} | |
## :clipboard: [Logs](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}) | |
## :hammer_and_wrench: Building result: ${{ needs.build.result == 'success' && ':white_check_mark:' || ':x:' }} | |
## :mag: clang-tidy results: ${{ (needs.clang-tidy.result == 'success' && ':white_check_mark:') || (needs.clang-tidy.result == 'skipped' && ':no_entry_sign:') || ':x:' }} | |
## :writing_hand: clang-format results: ${{ (needs.clang-format.result == 'success' && ':white_check_mark:') || (needs.clang-format.result == 'skipped' && ':no_entry_sign:') || ':x:' }} | |
## :package: Artifacts: | |
If the building step was successfull: | |
1. Download the tarball in the artifacts section [here](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}). | |
2. If new major version, [uninstall the previous version](docs/uninstallation.md) if you have one | |
3. Unzip: `unzip linux-enable-ir-emitter*.tar.gz.zip` | |
4. [Execute the install instructions](README.md#installation) | |
During the execution the tool raises an exception?\ | |
Please send us the gdb backtrace: `sudo gdb --ex run --args linux-enable-ir-emitter <your command args>`, once the crash arrives, type `bt` to show the error trace (`q` to exit). |