Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CIP: resolve / filter remaining issues of 4.4 branch #1053

Closed
jan-kiszka opened this issue Feb 24, 2022 · 8 comments
Closed

CIP: resolve / filter remaining issues of 4.4 branch #1053

jan-kiszka opened this issue Feb 24, 2022 · 8 comments
Labels
cip cip related issues
Projects
KernelCI project board

Comments

@jan-kiszka
Copy link

See https://linux.kernelci.org/build/stable-rc/branch/linux-4.4.y/kernel/v4.4.302/ or also maintainer staging branches like https://linux.kernelci.org/build/cip-gitlab/branch/ci%2Fpavel%2Flinux-test/kernel/v4.4.302-1101-gc2ab5f3d8331/

@aliceinwire @patersonc
@gctucker gctucker added this to Backlog in KernelCI project board via automation Feb 24, 2022
@patersonc patersonc added the cip cip related issues label Feb 25, 2022
@patersonc
Copy link
Contributor

Hi @jan-kiszka

Could you add some more detail on what the issue/request actually is?

Thanks, Chris

@jan-kiszka
Copy link
Author

As we discussed yesterday: either resolve the cited errors or drop those configs.

@gctucker
Copy link
Contributor

Others have mentioned before the fact that some builds are failing on old stable branches and it wasn't worth keeping them. If you think they can be fixed then great, otherwise we can add a blocklist filter in the build configs YAML. I think the same issues are on the stable queues, stable-rc and stable trees for 4.4 and probably 4.9 too.

A long-term solution for that is to determine new regressions from one stable release to the next, as that would be the basis for sending automated email reports for stable review threads. These are the ones that really have to get fixed in order to keep the same quality level in the code. Then new regressions could be highlighted on the web UI rather than all regressions. This would apply to tests too, or any result in KernelCI. The advantage would be to not require any manual maintenance about things to report or not report.

@fbezdeka
Copy link
Contributor

Maybe it's time to refresh this one here. In the meantime we

As already summarized in #1362, we now have the following issues for the 4.4-cip tree:

Who is able to help here? Would be nice to get the 4.4-cip tree "green".

@aliceinwire

@aliceinwire
Copy link
Member

aliceinwire commented Oct 20, 2022 •
edited

looks like that logs got deleted by someone
anyway:

  • baseline/x86_64_defconfig+x86-chromebook
    https://linux.kernelci.org/build/id/63370cf6f978caa398ec4eed/logs/
    prompt is now detected but have some warnings
  • baseline-cip-nfs/beaglebone-black multi_v7_defconfig
    couldn't find this anymore
  • hp-x360-14-G1-sona x86_64_defconfig+x86-chromebook
    couldn't find this
  • ltp-fcntl-locktests/asus-C523NA-A20057-coral x86_64_defconfig+x86-chromebook
    couldn't find this

@fbezdeka
Copy link
Contributor

According to https://lists.cip-project.org/g/cip-dev/message/9797 the filtering works now. We have one SMC related issue remaining but that looks not limited to 4.4-cip at first glance. Should we close this issue now?

@aliceinwire
Copy link
Member

@fbezdeka let's check at the next CIP meeting.

@aliceinwire
Copy link
Member

closing as per decision at CIP meeting 2022/12/01

KernelCI project board automation moved this from Backlog to Done Dec 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cip cip related issues
Projects
CIP
Status: Done
KernelCI project board
  
Done
Milestone
No milestone
Development

No branches or pull requests
5 participants
@aliceinwire @fbezdeka @jan-kiszka @gctucker @patersonc