v4l2-decoder: Remove media tree monitoring, add stable-rc_6.6 #897
Conversation
There was a problem hiding this comment.
AFAIK there is no such tree as stable-rc_6.6.
I added documentation for rules parameter: #899 if it will help.
stable-rc_6.6 is name of one of build configurations, it cannot be used in rules.
|
@denisyuji from my understanding, the codec tests are going to target the 6.6 LTS (and the 6.12 LTS later). As far as I can see we're not tracking the 6.6 LTS tree/branch at the moment (that's different from stable-rc). In that case, I think we should start tracking the |
nuclearcat
added
the
staging-skip
|
Yes, here is example: #807 |
denisyuji
changed the title
denisyuji
force-pushed
the
v4l2-decoder-update-trees
branch
from
754f6e0
to
6f68acd
Compare
denisyuji
changed the title
|
@laura-nao, @nuclearcat , thank you for your inputs. Please, see the changes now and let me know if it looks good now. |
denisyuji
force-pushed
the
v4l2-decoder-update-trees
branch
4 times, most recently
from
fb3c9d5
to
4ba3c09
Compare
As per internal discussion, we will not monitor `media` branch for fluster/tast v4l2 decoder tests neither for ChromeOS or Debian rootfs. We will keep monitoring `next` branch for fluster tests for now and evaluate its value later. Signed-off-by: Denis Yuji Shimizu <[email protected]>
denisyuji
force-pushed
the
v4l2-decoder-update-trees
branch
from
4ba3c09
to
1025349
Compare
|
@nuclearcat did you see the changes I suggested above? With this patch as-is, all Tast tests will run on mainline, stable and collabora-chromeos-kernel, not just the codec tests..which is not what we wanted. |
|
@denisyuji can you fix that please? |
|
Thank you @laura-nao . That makes sense. I fixed it in a new PR: #939 |
As per internal discussion, we will separate the handling of Tast tests in 2 grpous: decoder related Tast tests and other Tast tests. The Tast decoder related tests will be monitored on the following branches: - mainline - collabora-chromeos-kernel - stable All other Tast tests will target: - mainline - stable-rc With that, we revert the changes on the tree monitoring for non-decoder tests made on [kernelci#897](https://github.com/kernelci/kernelci-pipeline/pull/897/files). Signed-off-by: Denis Yuji Shimizu <[email protected]>
|
@nuclearcat @laura-nao After this PR, there are no build/tests enabled on it. Should we remove media tree stubs from kernelci? |
As per internal discussion (ref: https://issuetracker.google.com/issues/371638530 ), we will not monitor
mediabranch for fluster/tast v4l2 decoder tests neither for ChromeOS or Debian rootfs. We will keep monitoringnextbranch for fluster tests for now and evaluate its value later. In addition, ChromeOS will stay instable-rc_6.6and eventuallystable-rc_6.12, so we will keep monitoring this branch.