public inbox for kernelci@lists.linux.dev
 help / color / mirror / Atom feed
From: Gustavo Padovan <gus@collabora.com>
To: linuxtv-ci@linuxtv.org
Cc: "kernelci@lists.linux.dev" <kernelci@lists.linux.dev>,
	Denys Fedoryshchenko <denys.f@collabora.com>
Subject: linux-media checkout failing for KernelCI
Date: Fri, 17 May 2024 09:41:04 -0400	[thread overview]
Message-ID: <2b1ca3bb-c49a-ce2d-2d86-821dfa6854a4@collabora.com> (raw)


Hi Media maintainers,

We are struggling to use the media tree, in the same way we usually 
virtually all other trees in KernelCI. The following commands gives 
KernelCI a fatal error.

git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
cd linux
git remote add media https://git.linuxtv.org/media_tree.git
git remote update media
git fetch --tags https://git.linuxtv.org/media_tree.git
fatal: Couldn't find remote ref HEAD

We are in the process of enabling a lot of testing for media using 
fluster/gst and the ChromeOS Tast PlatformDecoder tests. I am not a git 
behavior expert, so we want to start this thread to discuss possible 
solutions as the media tree is for some reason deviating from some tacit 
standard.

Thoughts?

Best,

- Gus

-- 
Gustavo Padovan
Kernel Lead

Collabora Ltd.
Platinum Building, St John's Innovation Park
Cambridge CB4 0DS, UK
Registered in England & Wales, no. 5513718


             reply	other threads:[~2024-05-17 13:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-17 13:41 Gustavo Padovan [this message]
2024-05-17 13:45 ` linux-media checkout failing for KernelCI Gustavo Padovan
2024-05-17 18:56   ` Mauro Carvalho Chehab
2024-05-17 19:46     ` Mauro Carvalho Chehab
2024-05-17 15:29 ` Guenter Roeck
2024-05-17 16:57   ` Gustavo Padovan
2024-05-17 21:40     ` Denys Fedoryshchenko

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=2b1ca3bb-c49a-ce2d-2d86-821dfa6854a4@collabora.com \
    --to=gus@collabora.com \
    --cc=denys.f@collabora.com \
    --cc=kernelci@lists.linux.dev \
    --cc=linuxtv-ci@linuxtv.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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox