Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] forgejo/workflows: add initial rudimentary CI
Date: Mon, 21 Jul 2025 21:24:23 +0200
Message-ID: <8518c19a-4b96-4e7a-8399-efeeee295901@rothenpieler.org> (raw)
In-Reply-To: <b3fe49b0-e3c9-4fc5-ab64-787344aa51c8@rothenpieler.org>


On 7/21/2025 7:44 PM, Timo Rothenpieler wrote:
> On 7/21/2025 7:02 PM, Leo Izen wrote:
>> On 7/21/25 12:37, Timo Rothenpieler wrote:
>>> It runs basic fate with no special dependencies enabled on x86_64 and
>>> aarch64.
>>> ---
>>>   .forgejo/workflows/test.yml | 39 +++++++++++++++++++++++++++++++++++++
>>>   .gitignore                  |  1 +
>>>   2 files changed, 40 insertions(+)
>>>   create mode 100644 .forgejo/workflows/test.yml
>>>
>>> diff --git a/.forgejo/workflows/test.yml b/.forgejo/workflows/test.yml
>>> new file mode 100644
>>> index 0000000000..f9e032b78c
>>> --- /dev/null
>>> +++ b/.forgejo/workflows/test.yml
>>> @@ -0,0 +1,39 @@
>>> +on:
>>> +  push:
>>> +    branches:
>>> +      - master
>>> +  pull_request:
>>> +
>>> +jobs:
>>> +  run_fate:
>>> +    strategy:
>>> +      fail-fast: false
>>> +      matrix:
>>> +        runner: [linux-amd64,linux-aarch64]
>>> +    runs-on: ${{ matrix.runner }}
>>> +    steps:
>>> +      - name: Checkout
>>> +        uses: actions/checkout@v4
>>> +      - name: Configure
>>> +        run: ./configure
>>> +      - name: Build
>>> +        run: make -j$(nproc)
>>> +      - name: Restore Cached Fate-Suite
>>> +        uses: actions/cache/restore@v4
>>> +        with:
>>> +          path: fate-suite
>>> +          key: fate-suite
>>> +          restore-keys: |
>>> +            fate-suite-
>>> +      - name: Sync Fate-Suite
>>> +        id: fate
>>> +        run: |
>>> +          make fate-rsync SAMPLES=$PWD/fate-suite
>>> +          echo "hash=$(find fate-suite -type f | sha256sum | cut -d' 
>>> ' -f1)" >> $GITHUB_OUTPUT
>>
>> $GITHUB_OUTPUT is probably a copypaste issue.
> 
> Negative, Forgejo Runners are fully compatible with GHA, so this is how 
> you do it.

By now, both FORGEJO_OUTPUT and GITHUB_OUTPUT work, so I think renaming 
this makes it look a bit nicer. Will amend locally.

>>> +      - name: Cache Fate-Suite
>>> +        uses: actions/cache/save@v4
>>> +        with:
>>> +          path: fate-suite
>>> +          key: fate-suite-${{ steps.fate.outputs.hash }}
>>> +      - name: Run Fate
>>> +        run: make fate SAMPLES=$PWD/fate-suite -j$(nproc)
>>> diff --git a/.gitignore b/.gitignore
>>> index 59c89da5e0..4aa49c52c7 100644
>>> --- a/.gitignore
>>> +++ b/.gitignore
>>> @@ -45,3 +45,4 @@
>>>   /libavcodec/vulkan/*.c
>>>   /libavfilter/vulkan/*.c
>>>   /.*/
>>> +!/.forgejo/
>>
>> _______________________________________________
>> ffmpeg-devel mailing list
>> ffmpeg-devel@ffmpeg.org
>> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
>>
>> To unsubscribe, visit link above, or email
>> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
> 
> _______________________________________________
> ffmpeg-devel mailing list
> ffmpeg-devel@ffmpeg.org
> https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
> 
> To unsubscribe, visit link above, or email
> ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2025-07-21 19:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-21 16:37 Timo Rothenpieler
2025-07-21 17:02 ` Leo Izen
2025-07-21 17:44   ` Timo Rothenpieler
2025-07-21 19:24     ` Timo Rothenpieler [this message]
2025-07-21 22:17 ` Michael Niedermayer
2025-07-21 22:40   ` Scott Theisen
2025-07-21 23:27     ` Kacper Michajlow
2025-07-21 23:00   ` Timo Rothenpieler

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8518c19a-4b96-4e7a-8399-efeeee295901@rothenpieler.org \
    --to=timo@rothenpieler.org \
    --cc=ffmpeg-devel@ffmpeg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git