Weekly Meeting 2019-01-14 #minutes

Weekly Meeting 2019-01-14 #minutes

[Dan Rue]

- Attendees: Charles Oliveira, Daniel Díaz, Guenter Roeck, Guillaume
  Tucker, Dan Rue, Mark Brown, Matt Hart

- [matt]
  - Scrap HTML emails everywhere?
    - Ask HTML receivers
  - In kernel defconfig build lists
    - Kernel tree owner can update the defconfig list without us having
      to roll out updated configs
      - [mark] let’s see what 0day does and others; how do they solve
        this?
      - [drue] perhaps a separate repo that manages configs like this
        out of band from the kernel tree and out of band from kernelci’s
        release cycle. This could also be useful to manage and support
        fragments.
      - [gtucker] what’s the actual usecase of wanting to filter
        defconfigs?
        - [matt] speed
        - [mark] well kernelci’s point is coverage. If you just want one
          built, you don’t need kernelci.
      - [matt] we’ll wait until the yaml work is completed by gtucker
        before making any changes here
    - Very useful for testing
      - [gtucker] Other way to do this is in build-configs.yaml with all
        the other build configuration settings (see initial work in
        kernelci-core-staging PR #75)

- [gtucker]
  - Test regressions merged on staging, testing last changes to the test
    reports
  - Adding fix for MIPS (remove hacks and use gcc-7)
  - V4l2 & dynamic metadata: adding a template parameter to the
    test-configs.yaml test plans settings to specify the video driver to
    use in the test (discovering the driver name at runtime isn’t
    practical with current LAVA)

- [drue]
  - Next steps on ‘[Help] How to use kernelci to establish a local CI
    lab?’?
    - [chaws] I mentioned this repo:
      https://github.com/kernelci/kernelci-core, but still unsure what
      the next step is
    - Li’s asking for support using kernelci-docker locally, not adding
      a lab to kernelci. There are a lot of versions of this repo in the
      wild, so it’s not clear who should help him. Matt can show him how
      he does it.

Re: Weekly Meeting 2019-01-14 #minutes

[Kevin Hilman]

"Dan Rue" <dan.rue@linaro.org> writes:

> - Attendees: Charles Oliveira, Daniel Díaz, Guenter Roeck, Guillaume
>   Tucker, Dan Rue, Mark Brown, Matt Hart
>
> - [matt]
>   - Scrap HTML emails everywhere?
>     - Ask HTML receivers
>   - In kernel defconfig build lists
>     - Kernel tree owner can update the defconfig list without us having
>       to roll out updated configs
>       - [mark] let’s see what 0day does and others; how do they solve
>         this?
>       - [drue] perhaps a separate repo that manages configs like this
>         out of band from the kernel tree and out of band from kernelci’s
>         release cycle. This could also be useful to manage and support
>         fragments.
>       - [gtucker] what’s the actual usecase of wanting to filter
>         defconfigs?
>         - [matt] speed
>         - [mark] well kernelci’s point is coverage. If you just want one
>           built, you don’t need kernelci.
>       - [matt] we’ll wait until the yaml work is completed by gtucker
>         before making any changes here
>     - Very useful for testing
>       - [gtucker] Other way to do this is in build-configs.yaml with all
>         the other build configuration settings (see initial work in
>         kernelci-core-staging PR #75)

We need flexibility in which defconfigs are built per tree, but also per
arch and probably per toolchain, so having this in a simple file in tree
is not sufficient.

IMO, the build-configs.yaml stuff that Guillaume is working on is the
way to go forward.

> - [gtucker]
>   - Test regressions merged on staging, testing last changes to the test
>     reports
>   - Adding fix for MIPS (remove hacks and use gcc-7)

Thanks!

>   - V4l2 & dynamic metadata: adding a template parameter to the
>     test-configs.yaml test plans settings to specify the video driver to
>     use in the test (discovering the driver name at runtime isn’t
>     practical with current LAVA)
>
> - [drue]
>   - Next steps on ‘[Help] How to use kernelci to establish a local CI
>     lab?’?
>     - [chaws] I mentioned this repo:
>       https://github.com/kernelci/kernelci-core, but still unsure what
>       the next step is
>     - Li’s asking for support using kernelci-docker locally, not adding
>       a lab to kernelci. There are a lot of versions of this repo in the
>       wild, so it’s not clear who should help him. Matt can show him how
>       he does it.

I'm not sure about a lot of versions, but we (BayLibre) are working
primarily on this one, which is also deployed for AGL:
https://github.com/lucj/kernelci-docker

Kevin

Re: Weekly Meeting 2019-01-14 #minutes

[Mark Brown]

[-- Attachment #1: Type: text/plain, Size: 1947 bytes --]

On Mon, Jan 14, 2019 at 01:56:29PM -0800, Kevin Hilman wrote:
> "Dan Rue" <dan.rue@linaro.org> writes:

> >     - Very useful for testing
> >       - [gtucker] Other way to do this is in build-configs.yaml with all
> >         the other build configuration settings (see initial work in
> >         kernelci-core-staging PR #75)

> We need flexibility in which defconfigs are built per tree, but also per
> arch and probably per toolchain, so having this in a simple file in tree
> is not sufficient.

> IMO, the build-configs.yaml stuff that Guillaume is working on is the
> way to go forward.

The suggestion was to allow trees to drop in something with the
build-configs.yaml syntax so you could do anything you can do with that
with the in tree file.

> 
> > - [gtucker]
> >   - Test regressions merged on staging, testing last changes to the test
> >     reports
> >   - Adding fix for MIPS (remove hacks and use gcc-7)
> 
> Thanks!
> 
> >   - V4l2 & dynamic metadata: adding a template parameter to the
> >     test-configs.yaml test plans settings to specify the video driver to
> >     use in the test (discovering the driver name at runtime isn’t
> >     practical with current LAVA)
> >
> > - [drue]
> >   - Next steps on ‘[Help] How to use kernelci to establish a local CI
> >     lab?’?
> >     - [chaws] I mentioned this repo:
> >       https://github.com/kernelci/kernelci-core, but still unsure what
> >       the next step is
> >     - Li’s asking for support using kernelci-docker locally, not adding
> >       a lab to kernelci. There are a lot of versions of this repo in the
> >       wild, so it’s not clear who should help him. Matt can show him how
> >       he does it.
> 
> I'm not sure about a lot of versions, but we (BayLibre) are working
> primarily on this one, which is also deployed for AGL:
> https://github.com/lucj/kernelci-docker
> 
> Kevin
> 
> 
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]