From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: "Thomas Huth" <thuth@redhat.com>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Cc: "Fam Zheng" <fam@euphon.net>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [PATCH] .travis.yml: Add description to each job
Date: Wed, 29 Jan 2020 09:20:53 +0100 [thread overview]
Message-ID: <93e3d049-4f02-92e6-9f7f-8f1a883a8ad0@redhat.com> (raw)
In-Reply-To: <a621498f-c9aa-5cd0-671f-f4e07c95aaa7@redhat.com>
On 1/29/20 8:34 AM, Thomas Huth wrote:
> On 29/01/2020 08.27, Philippe Mathieu-Daudé wrote:
>> On 1/29/20 8:20 AM, Thomas Huth wrote:
>>> On 28/01/2020 14.33, Wainer dos Santos Moschetta wrote:
>>>>
>>>> On 1/28/20 11:18 AM, Philippe Mathieu-Daudé wrote:
>>>>> On Tue, Jan 28, 2020 at 1:55 PM Alex Bennée <alex.bennee@linaro.org>
>>>>> wrote:
>>>>>> Thomas Huth <thuth@redhat.com> writes:
>>>>>>> On 25/01/2020 19.31, Philippe Mathieu-Daudé wrote:
>>>>>>>> The NAME variable can be used to describe nicely a job (see [*]).
>>>>>>>> As we currently have 32 jobs, use it. This helps for quickly
>>>>>>>> finding a particular job.
>>>>>>>>
>>>>>>>> before: https://travis-ci.org/qemu/qemu/builds/639887646
>>>>>>>> after: https://travis-ci.org/philmd/qemu/builds/641795043
>>>>>>> Very good idea, correlating a job in the GUI to an entry in the yml
>>>>>>> file
>>>>>>> was really a pain, so far.
>>>>>>>
>>>>>>>> [*]
>>>>>>>> https://docs.travis-ci.com/user/customizing-the-build/#naming-jobs-within-matrices
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
>>>>>>>> ---
>>>>>>>> .travis.yml | 101
>>>>>>>> ++++++++++++++++++++++++++++++++++------------------
>>>>>>>> 1 file changed, 67 insertions(+), 34 deletions(-)
>>>>>>>>
>>>>>>>> diff --git a/.travis.yml b/.travis.yml
>>>>>>>> index 6c1038a0f1..d68e35a2c5 100644
>>>>>>>> --- a/.travis.yml
>>>>>>>> +++ b/.travis.yml
>>>>>>>> @@ -94,24 +94,28 @@ after_script:
>>>>>>>>
>>>>>>>> matrix:
>>>>>>>> include:
>>>>>>>> - - env:
>>>>>>>> + - name: "[x86] GCC static (user)"
>>>>>>> Could you please drop the [x86] and other architectures from the
>>>>>>> names?
>>>>>>> Travis already lists the build architecture in the job status
>>>>>>> page, so
>>>>>>> this information is redundant.
>>>>>> Hmm for me the Travis page mis-renders the architecture (on
>>>>>> firefox) so
>>>>>> I do find the arch in the text fairly handy.
>>>>> This might be a font problem, I can't see the architecture on neither
>>>>> Firefox nor Chrome:
>>>>>
>>>>> https://pasteboard.co/IS3O358.png
>>>>
>>>>
>>>> It is the partially hidden column between the job number and the penguin
>>>> (or apple if MacOS).
>>>>
>>>> Funny, I can see the arch on Philippe's dashboard
>>>> (https://travis-ci.org/philmd/qemu) but it disappears on my own
>>>> (https://travis-ci.org/wainersm/qemu).
>>>
>>> I've never had problems here, for me the column shows up correctly
>>> everywhere. It looks like this:
>>>
>>> http://people.redhat.com/~thuth/travis.png
>>
>> OK now I understand better your comment :)
>>
>>>
>>>> Anyway, most of the jobs run on x86_64. So perhaps mark only the non-x86
>>>> ones?
>>>
>>> Sounds like a good compromise to me!
>>
>> I'd rather use one style, rather ARCH explicit on all, or not used at all.
>
> Then I'd vote to drop it (if I've got a vote here at all ;-)), hoping
> that Travis fixes their HTML for that column, soon...
Fine.
I opened issue https://github.com/travis-ci/travis-ci/issues/10503 which
got closed, then I got lost in their forum. I'll simply hope instead.
next prev parent reply other threads:[~2020-01-29 8:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 18:31 [PATCH] .travis.yml: Add description to each job Philippe Mathieu-Daudé
2020-01-26 7:54 ` Thomas Huth
2020-01-28 12:55 ` Alex Bennée
2020-01-28 13:18 ` Philippe Mathieu-Daudé
2020-01-28 13:33 ` Wainer dos Santos Moschetta
2020-01-29 7:20 ` Thomas Huth
2020-01-29 7:27 ` Philippe Mathieu-Daudé
2020-01-29 7:34 ` Thomas Huth
2020-01-29 8:20 ` Philippe Mathieu-Daudé [this message]
2020-01-29 7:38 ` Thomas Huth
2020-01-28 13:20 ` Wainer dos Santos Moschetta
2020-01-29 7:31 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=93e3d049-4f02-92e6-9f7f-8f1a883a8ad0@redhat.com \
--to=philmd@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=fam@euphon.net \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).