Hi Gábor,

On Thu, 6 Feb 2020, SZEDER Gábor wrote:

> On Thu, Feb 06, 2020 at 09:57:51AM +0100, Johannes Schindelin wrote:
> >
> > On Thu, 6 Feb 2020, SZEDER Gábor wrote:
> >
> > > On Wed, Feb 05, 2020 at 01:01:50PM -0800, Junio C Hamano wrote:
> > > >
> > > > If linux-gcc and linux-clang labels are not visible, linux-clang-py2
> > > > and osx-py3 would not be, either, so...
> > >
> > > The 'linux-gcc' and 'linux-clang' labels are not visible on Travis CI,
> > > because those jobs as part of the build matrix, and, consequently, we
> > > can't set the a 'jobname' environment variable for them in
> > > '.travis.yml'.  If we were to include additional jobs for the Python
> > > scripts, then for those we can (and should!) set
> > > 'jobname=linux-python' or something, and that would be visible on the
> > > Travis CI web interface, just like e.g. 'jobname=StaticAnalysis'.
> >
> > I think we can see that jobname very well, though. If you direct your web
> > browser to
> > https://travis-ci.org/git/git/builds/646646192?utm_source=github_status&utm_medium=notification
> > you will see something like this:
> >
> >     Build jobs		View config
> >
> > ! 5281.1 AMD64		Compiler: clang Xcode: xcode10.1 C	no environment variables set	8 min 20 sec
> > ! 5281.2 AMD64		Compiler: gcc Xcode: xcode10.1 C	no environment variables set	8 min 23 sec
> > X 5281.3 AMD64		Compiler: clang Xcode: xcode10.1 C	no environment variables set	1 min 57 sec
> > X 5281.4 AMD64		Compiler: gcc Xcode: xcode10.1 C	no environment variables set	2 min 41 sec
> > ! 5281.5 AMD64		Xcode: xcode10.1 C			jobname=GIT_TEST_GETTEXT_POISON	5 min 14 sec
> > X 5281.6 AMD64		Xcode: xcode10.1 C			jobname=linux-gcc-4.8		1 min 13 sec
> > ! 5281.7 AMD64		Xcode: xcode10.1 C			jobname=Linux32			6 min 50 sec
> > ✓ 5281.8 AMD64		Xcode: xcode10.1 C			jobname=StaticAnalysis		10 min 56 sec
> > ✓ 5281.9 AMD64		Xcode: xcode10.1 C			jobname=Documentation		6 min 15 sec
>
> I don't see any 'linux-gcc' and 'linux-clang' jobnames.

Ah, that's what you meant. Indeed, those are not displayed because we set
them at the wrong layer, they would need to be defined in `.travis.yml`.
You probably _can_ use variables in the `jobname`.

Ciao,
Dscho