[Mesa-ci-intel] New CI branch for Mesa 18.3.x series
Juan A. Suarez Romero
jasuarez at igalia.com
Mon Nov 5 09:32:17 UTC 2018
On Fri, 2018-11-02 at 13:08 +0000, Emil Velikov wrote:
> [adding the Andres, Juan, Dylan]
>
> On Thu, 1 Nov 2018 at 22:00, Emil Velikov <emil.l.velikov at gmail.com> wrote:
> > On Thu, 1 Nov 2018 at 21:17, Clayton Craft <clayton.a.craft at intel.com> wrote:
> > > Quoting Emil Velikov (2018-11-01 12:09:03)
> > > > Hello gents,
> > > >
> > > > Can you please setup the following repo/branch for the 18.3.x series.
> > > Done.
> > > Can you push something to this branch so I can verify that it is triggering
> > > correctly?
> > >
> > Done. Just pushed a dummy `touch TEST` commit.
> >
> As per your IRC request - force-pushed ~3h ago, although I cannot see
> anything on website.
>
> > > > Repo: https://github.com/evelikov/Mesa/
> > > > Branch: wip/18.3
> > > >
> > > > Please let me know if the results will be available via the official
> > > > site or otherwise.
> > > The results will show up on the public CI results site (mesa-ci.01.org) once
> > > builds are complete.
> > Amazing thanks.
> >
I'd like to say that for 18.2, we were using Mesa repository, not our own
repository. I think this was agreed in a thread some time ago. And I think this
should be kept for 18.3, so everything happens in the mesa repository.
FWIW, we use two branches:
- staging/18.2, where we push/rebase everyday
- staging/18.2-ci, which runs a more complete testsuite (IIRC, this runs 64bit
and 32bit tests), and that we only push once, just before making the pre-
announcement, in order to detect any issue not detected when pushing to
staging/18.2
As I said, it would be great if we continue using a similar approach for 18.3
branches.
> > In the past someone from the Intel team had to run through the results
> > to ensure there's no regressions.
> > I take it that has been resolved now and there's some automated way to
> > check for regressions?
> >
> > Alternatively please share some light how I can ensure we don't
> > introduce issues.
> >
> Andres, Juan, Dylan - how did you guys handle regression tracking with
> the new setup?
> Is there something to setup on Intel side, my end, other?
>
Basically, we take a look at https://mesa-ci.01.org/, where the results for
staging/18.2 and staging/18.2-ci are pushed. In our side we do nothing, only
push commits to those branches.
If we see that no results were pushed, then we ask Clayton/Mark, as probably
something was broken in the CI and manually work is required.
J.A.
> Thanks
> Emil
> _______________________________________________
> Mesa-ci-intel mailing list
> Mesa-ci-intel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/mesa-ci-intel
More information about the Mesa-ci-intel
mailing list