From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [RFC] fateserver
Date: Mon, 26 Feb 2024 03:57:13 +0100
Message-ID: <20240226025713.GR6420@pb2> (raw)
In-Reply-To: <CA+28BfC_a_TCjPnQZB_w2ez-Agc=oRXp20S2_a0qZP_1B+t35Q@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 811 bytes --]
On Sun, Feb 25, 2024 at 06:21:14PM -0600, Marth64 wrote:
> Thank you Michael, for the opportunity. I have some initial questions
> while others add the remaining detail.
>
> 1) What is the flow of test result data like? e.g. do individual test
> servers send the data via API? Or does this tool query them directly.
fate clients send data via ssh to fate-recv.sh from fateserver
the way this is triggered is up to the person running teh individual fate client
it can be a simple for loop in a shell script
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Concerning the gods, I have no means of knowing whether they exist or not
or of what sort they may be, because of the obscurity of the subject, and
the brevity of human life -- Protagoras
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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".
next prev parent reply other threads:[~2024-02-26 2:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 17:49 Michael Niedermayer
2024-02-25 6:36 ` Marth64
2024-02-25 19:28 ` Michael Niedermayer
2024-02-26 0:21 ` Marth64
2024-02-26 2:57 ` Michael Niedermayer [this message]
2024-02-26 14:29 ` Michael Niedermayer
2024-03-08 1:08 ` Marth64
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=20240226025713.GR6420@pb2 \
--to=michael@niedermayer.cc \
--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