On Tue, Jun 21, 2022 at 6:21 PM Ivan Zhakov <i...@visualsvn.com> wrote:
>
> On Tue, 21 Jun 2022 at 19:16, Yann Ylavic <ylavic....@gmail.com> wrote:
>>
>> On Tue, Jun 21, 2022 at 5:58 PM Ivan Zhakov <i...@visualsvn.com> wrote:
>> >
>> > On Tue, 21 Jun 2022 at 18:33, Yann Ylavic <ylavic....@gmail.com> wrote:
>> >>
>> >> Hi Ivan,
>> >>
>> >> I'm responding randomly to one of your ci commits, first to say
>> >> thanks, really nice and valuable work!
>> >>
>> >> I have a question too :) Sorry if it's premature, but I'm also
>> >> wondering why we don't see the outputs of the jobs in the github UI,
>> >> for instance in [1] for both succeeding and failing jobs the details
>> >> of the steps shows "Error:" only without more output (i.e. something
>> >> that could help us fix errors).
>> >> Do you know if there is a way to show the stdout/stderr of the
>> >> commands/scripts instead?
>> >>
>> > I see error output in testlog:
>>
>> Ah yes, I actually expected the outputs to be viewable by developing
>> the failing step (with the arrow), but the logs are actually available
>> via "View raw logs" in the configuration like icon..
>>
> I see outputs when click on the failing step. See screenshot in attachement.

Argh, sorry for the noise and your time, the blame is on a javascript
filter on my firefox :/

Well, I'm hesitating for my second remark now, but I'm going for it anyway :p
It seems that setting both branches like you did in this commit (r1902143):

-    branches: [ "trunk" ]
+    branches: [ "trunk", "1.8.x" ]

is causing two runs to be launched by gh actions whenever either
apr-trunk or apr-1.8.x is modified.
Don't we want "trunk" only in "trunk/.github/workflows/linux.yml" and
"1.8.x" only in "1.8.x/.github/workflows/linux.yml" instead?
I'm double checking but https://github.com/apache/apr/actions really
seem to show this behaviour, and somehow one of the build is failing..

Regards;
Yann.

Reply via email to