nonspammy KDE builds?

classic Classic list List threaded Threaded
27 messages Options
12
Reply | Threaded
Open this post in threaded view
|

nonspammy KDE builds?

Mathias Homann-2
Hi,

I have a failing build in home:lemmy04/digikam. HOW can i make the build
process NOT throw up gigabytes of ascii progress all over the logfile so that
I can actually FIND the error?

I've already changed VERBOSE=1 to VERBOSE=0 in the spec file, which did ...
exactly... nothing.

Anyone got any ideas?

Thanks
Mathias

--
Mathias Homann
Senior Systems Engineer, IT Consultant. IT Trainer
[hidden email]
http://www.tuxonline.tech
gpg key fingerprint: 8029 2240 F4DD 7776 E7D2 C042 6B8E 029E 13F2 C102

signature.asc (650 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

Dave Plater lst


On 09/12/2017 16:39, Mathias Homann wrote:

> Hi,
>
> I have a failing build in home:lemmy04/digikam. HOW can i make the build
> process NOT throw up gigabytes of ascii progress all over the logfile so that
> I can actually FIND the error?
>
> I've already changed VERBOSE=1 to VERBOSE=0 in the spec file, which did ...
> exactly... nothing.
>
> Anyone got any ideas?
>
> Thanks
> Mathias
>
I usually search for "error:" or the "waiting" in "waiting for
unfinished jobs. If it's still mangled you may have to set make to a
single thread.
If you really want to remove verbose from a %cmake build reset
-DCMAKE_VERBOSE_MAKEFILE:BOOL=ON to off, it's part of the %cmake macro.
Regards
Dave P
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

John Paul Adrian Glaubitz
In reply to this post by Mathias Homann-2
On 12/09/2017 03:39 PM, Mathias Homann wrote:
> I have a failing build in home:lemmy04/digikam. HOW can i make the build
> process NOT throw up gigabytes of ascii progress all over the logfile so that
> I can actually FIND the error?

Comparing the build logs for digikam in OBS and Debian, it seems the key point to
readability is to turn off the automatic line wraps:

OBS: https://build.opensuse.org/build/home:lemmy04/openSUSE_Leap_42.3/x86_64/digikam/_log
Debian: https://buildd.debian.org/status/fetch.php?pkg=digikam&arch=amd64&ver=4%3A5.6.0-4%2Bb1&stamp=1512903221&raw=0

The long lines are the invocations of Qt5's moc C++ preprocessor and while they fill
long paragraphs in the OBS log, they are just very long single lines in Debian's
build logs which makes the logs more readable.

Is there maybe a way to tell OBS to turn off the automatic line wraps?

Adrian
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

Olaf Hering-2
On Sun, Dec 10, John Paul Adrian Glaubitz wrote:

> Is there maybe a way to tell OBS to turn off the automatic line wraps?

It does that by default via -fmessage-length=0 in RPM_OPT_FLAGS since many years.
Maybe the package in question ignores RPM_OPT_FLAGS.

Olaf

signature.asc (201 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

Andreas Schwab-2
In reply to this post by John Paul Adrian Glaubitz
On Dez 10 2017, John Paul Adrian Glaubitz <[hidden email]> wrote:

> Comparing the build logs for digikam in OBS and Debian, it seems the key point to
> readability is to turn off the automatic line wraps:
>
> OBS: https://build.opensuse.org/build/home:lemmy04/openSUSE_Leap_42.3/x86_64/digikam/_log

Which line wraps are you talking about?

Andreas.

--
Andreas Schwab, SUSE Labs, [hidden email]
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

John Paul Adrian Glaubitz

> On Dec 11, 2017, at 12:30 PM, Andreas Schwab <[hidden email]> wrote:
>
>> On Dez 10 2017, John Paul Adrian Glaubitz <[hidden email]> wrote:
>>
>> Comparing the build logs for digikam in OBS and Debian, it seems the key point to
>> readability is to turn off the automatic line wraps:
>>
>> OBS: https://build.opensuse.org/build/home:lemmy04/openSUSE_Leap_42.3/x86_64/digikam/_log
>
> Which line wraps are you talking about?

The moc invocations. Those lines are wrapped in OBS which is why there are these long paragraphs of text.

Adrian--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

Andreas Schwab-2
On Dez 11 2017, John Paul Adrian Glaubitz <[hidden email]> wrote:

> The moc invocations.

Any example?

Andreas.

--
Andreas Schwab, SUSE Labs, [hidden email]
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

Michael Matz
In reply to this post by John Paul Adrian Glaubitz
Hi,

On Sun, 10 Dec 2017, John Paul Adrian Glaubitz wrote:

> On 12/09/2017 03:39 PM, Mathias Homann wrote:
> > I have a failing build in home:lemmy04/digikam. HOW can i make the build
> > process NOT throw up gigabytes of ascii progress all over the logfile so
> > that
> > I can actually FIND the error?

Use a text viewer that can disable auto linewrap: less -S .

> Comparing the build logs for digikam in OBS and Debian, it seems the key
> point to readability is to turn off the automatic line wraps:
>
> OBS:
> https://build.opensuse.org/build/home:lemmy04/openSUSE_Leap_42.3/x86_64/digikam/_log
> Debian:
> https://buildd.debian.org/status/fetch.php?pkg=digikam&arch=amd64&ver=4%3A5.6.0-4%2Bb1&stamp=1512903221&raw=0
>
> The long lines are the invocations of Qt5's moc C++ preprocessor and
> while they fill long paragraphs in the OBS log, they are just very long
> single lines in Debian's build logs which makes the logs more readable.
>
> Is there maybe a way to tell OBS to turn off the automatic line wraps?

It's your browser doing the line wrapping.  Use curl with the above URL or
rather simply use osc to see that the file itself doesn't have line wraps.


Ciao,
Michael.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

John Paul Adrian Glaubitz


> On Dec 11, 2017, at 2:31 PM, Michael Matz <[hidden email]> wrote:
>
> It's your browser doing the line wrapping.  Use curl with the above URL or
> rather simply use osc to see that the file itself doesn't have line wraps.

The same browser doesn’t wrap the lines of the Debian build logs.

Adrian--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

Michael Matz
Hi,

On Mon, 11 Dec 2017, John Paul Adrian Glaubitz wrote:

>
>
> > On Dec 11, 2017, at 2:31 PM, Michael Matz <[hidden email]> wrote:
> >
> > It's your browser doing the line wrapping.  Use curl with the above URL or
> > rather simply use osc to see that the file itself doesn't have line wraps.
>
> The same browser doesn’t wrap the lines of the Debian build logs.

Sure, because you compare apples and oranges.  Debian delivers a HTML page
with the 'raw=0' you had in your URL.  OBS always delivers a raw text
file.  And that latter happens to be line wrapped in your browser (in mine
as well).  Use 'raw=1' if you want to see how it's also line wrapped with
the debian logs in a browser.


Ciao,
Michael.
Hint: use the source view of browser to see for yourself
Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

John Paul Adrian Glaubitz
On 12/11/2017 02:47 PM, Michael Matz wrote:
> Sure, because you compare apples and oranges.  Debian delivers a HTML page
> with the 'raw=0' you had in your URL.  OBS always delivers a raw text
> file.  And that latter happens to be line wrapped in your browser (in mine
> as well).  Use 'raw=1' if you want to see how it's also line wrapped with
> the debian logs in a browser.

Is this now about arguing who is right or this about solving the problem that
the original poster had?

I mean, yes, you are 100% right but that doesn't change the fact that the OBS
logs are harder to read from the browser than Debian's build logs and I think
that's the problem that the original poster has. And my browser is using the
default settings, Firefox 57 on openSUSE Tumbleweed.

Thanks,
Adrian

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

Michael Matz
Hi,

On Mon, 11 Dec 2017, John Paul Adrian Glaubitz wrote:

> On 12/11/2017 02:47 PM, Michael Matz wrote:
> > Sure, because you compare apples and oranges.  Debian delivers a HTML page
> > with the 'raw=0' you had in your URL.  OBS always delivers a raw text
> > file.  And that latter happens to be line wrapped in your browser (in mine
> > as well).  Use 'raw=1' if you want to see how it's also line wrapped with
> > the debian logs in a browser.
>
> Is this now about arguing who is right or this about solving the problem
> that the original poster had?

To find a solution one needs to understand the source of the problem.  
As your claim that OBS wraps lines isn't true and hence not the source of
it following that path of thought wouldn't have led to a solution.  Indeed
you haven't proposed any.

Stating the real source of the problem I came to the only solution I can
imagine working currently: using a non-wrapping text viewer, i.e. not a
browser.

> I mean, yes, you are 100% right but that doesn't change the fact that
> the OBS logs are harder to read from the browser than Debian's build
> logs and I think that's the problem that the original poster has.

And I didn't dispute any of this, did I?  I offered the
browser-line-wrapping things as explanation (for why the proposed solution
is the only one that works right now), and elaborated only when you asked
back (at least I assumed it was an implicit question); like I'm
elaborating now on meta topics :)

> And my browser is using the default settings, Firefox 57 on openSUSE
> Tumbleweed.

Well, what do you want me to say?  Yes, it looks suboptimal in the
browser.  It would be nice if it would look nicer.  Is anyone going to
implement non-line-wrapping in firefox?  I doubt it.  Is anyone going to
implement a non-raw mode for the build log URL like debian?  Perhaps, that
would be nice.  Is saying any of these things giving a solution to the
problem that works right now?  No.  So why mention them?


Ciao,
Michael.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

Simon Lees-3
In reply to this post by John Paul Adrian Glaubitz


On 12/12/17 06:16, John Paul Adrian Glaubitz wrote:

> On 12/11/2017 02:47 PM, Michael Matz wrote:
>> Sure, because you compare apples and oranges.  Debian delivers a HTML
>> page
>> with the 'raw=0' you had in your URL.  OBS always delivers a raw text
>> file.  And that latter happens to be line wrapped in your browser (in
>> mine
>> as well).  Use 'raw=1' if you want to see how it's also line wrapped with
>> the debian logs in a browser.
>
> Is this now about arguing who is right or this about solving the problem
> that
> the original poster had?
>
> I mean, yes, you are 100% right but that doesn't change the fact that
> the OBS
> logs are harder to read from the browser than Debian's build logs and I
> think
> that's the problem that the original poster has. And my browser is using
> the
> default settings, Firefox 57 on openSUSE Tumbleweed.
>
> Thanks,
> Adrian
>
But this is really a matter of preference though, personally I find
build logs that don't wrap and that you have to scroll left to right on
much harder to read. At this point openSUSE is providing a plain text
file viewed in a browser, whether the browser wraps plain text files or
not really should be a browser config option if its not already (or
atleast fixable via a plugin)

--

Simon Lees (Simotek)                            http://simotek.net

Emergency Update Team                           keybase.io/simotek
SUSE Linux                           Adelaide Australia, UTC+10:30
GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B


signature.asc (499 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

Andreas Schwab-2
In reply to this post by John Paul Adrian Glaubitz
On Dez 11 2017, John Paul Adrian Glaubitz <[hidden email]> wrote:

> I mean, yes, you are 100% right but that doesn't change the fact that the OBS
> logs are harder to read from the browser than Debian's build logs and I think
> that's the problem that the original poster has.

Non-plain logs are harder to handle since they are useless in an editor.

Andreas.

--
Andreas Schwab, SUSE Labs, [hidden email]
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

Arjen de Korte-2
In reply to this post by John Paul Adrian Glaubitz
Citeren John Paul Adrian Glaubitz <[hidden email]>:

> On 12/11/2017 02:47 PM, Michael Matz wrote:
>> Sure, because you compare apples and oranges.  Debian delivers a HTML page
>> with the 'raw=0' you had in your URL.  OBS always delivers a raw text
>> file.  And that latter happens to be line wrapped in your browser (in mine
>> as well).  Use 'raw=1' if you want to see how it's also line wrapped with
>> the debian logs in a browser.
>
> Is this now about arguing who is right or this about solving the problem that
> the original poster had?
>
> I mean, yes, you are 100% right but that doesn't change the fact that the OBS
> logs are harder to read from the browser than Debian's build logs and I think
> that's the problem that the original poster has. And my browser is using the
> default settings, Firefox 57 on openSUSE Tumbleweed.

Firefox by default wraps lines in plain_text. But this is easy to change:

about:config -> plain_text.wrap_long_lines -> false

--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

Mathias Homann-2


On 12.12.2017 10:31, Arjen de Korte wrote:

> Citeren John Paul Adrian Glaubitz <[hidden email]>:
>
>> On 12/11/2017 02:47 PM, Michael Matz wrote:
>>> Sure, because you compare apples and oranges.  Debian delivers a
>>> HTML page
>>> with the 'raw=0' you had in your URL.  OBS always delivers a raw text
>>> file.  And that latter happens to be line wrapped in your browser
>>> (in mine
>>> as well).  Use 'raw=1' if you want to see how it's also line wrapped
>>> with
>>> the debian logs in a browser.
>>
>> Is this now about arguing who is right or this about solving the
>> problem that
>> the original poster had?
>>
>> I mean, yes, you are 100% right but that doesn't change the fact that
>> the OBS
>> logs are harder to read from the browser than Debian's build logs and
>> I think
>> that's the problem that the original poster has. And my browser is
>> using the
>> default settings, Firefox 57 on openSUSE Tumbleweed.
>
> Firefox by default wraps lines in plain_text. But this is easy to change:
>
> about:config -> plain_text.wrap_long_lines -> false
>

Obviously this is all about arguing who is wrong and who is right.

That being said: my biggest problem with that failing build is that not
even grepping for "error" or something helped to make the log more
readable since the developers of digikam saw fit to have several folders
containing "error" in their name in the project, which absolutely HAD to
be added to the include path on each moc call, hence each call having
several -I statements with the word "error" in them.

Cheers
MH
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

Andreas Schwab-2
On Dez 12 2017, Mathias Homann <[hidden email]> wrote:

> That being said: my biggest problem with that failing build is that not
> even grepping for "error" or something helped to make the log more
> readable since the developers of digikam saw fit to have several folders
> containing "error" in their name in the project, which absolutely HAD to
> be added to the include path on each moc call, hence each call having
> several -I statements with the word "error" in them.

Grep for "error:" then.

Andreas.

--
Andreas Schwab, SUSE Labs, [hidden email]
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

John Paul Adrian Glaubitz
In reply to this post by Andreas Schwab-2
On 12/12/2017 10:20 AM, Andreas Schwab wrote:
> On Dez 11 2017, John Paul Adrian Glaubitz <[hidden email]> wrote:
>
>> I mean, yes, you are 100% right but that doesn't change the fact that the OBS
>> logs are harder to read from the browser than Debian's build logs and I think
>> that's the problem that the original poster has.
>
> Non-plain logs are harder to handle since they are useless in an editor.

I can get the raw builds logs by just clicking the "text" link in Debian
but the default are the HTML-encapsuled logs which is reasonable when
opening the log file with a web-browser for viewing.

But I guess this is turning into bike-shedding now. I prefer Debian's
solution because it allows me to choose between a web view and a plain
view and the web view is default in the browser.

Adrian
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

John Paul Adrian Glaubitz
In reply to this post by Michael Matz
On 12/11/2017 11:10 PM, Michael Matz wrote:
> To find a solution one needs to understand the source of the problem.  
> As your claim that OBS wraps lines isn't true and hence not the source of
> it following that path of thought wouldn't have led to a solution.  Indeed
> you haven't proposed any.

Well, the proposal would be to offer both HTML-encapsuled logs as well
as raw logs.

> Stating the real source of the problem I came to the only solution I can
> imagine working currently: using a non-wrapping text viewer, i.e. not a
> browser.

Which means users will have to download the log first, open a text editor,
then load the log file into it. Or they have to switch to the console
and use the OSC command to retrieve the log. In any case, they have to
switch away from the browser.

>> And my browser is using the default settings, Firefox 57 on openSUSE
>> Tumbleweed.
>
> Well, what do you want me to say?  Yes, it looks suboptimal in the
> browser.  It would be nice if it would look nicer.  Is anyone going to
> implement non-line-wrapping in firefox?  I doubt it.  Is anyone going to
> implement a non-raw mode for the build log URL like debian?  Perhaps, that
> would be nice.  Is saying any of these things giving a solution to the
> problem that works right now?  No.  So why mention them?

This isn't an issue in Firefox. This is an issue with OBS which doesn't
offer a web-browser compatible log file. The Debian solution works just
fine. Offer an HTML-encapsulated log file for the browser plus a link
to the raw log:

> https://buildd.debian.org/status/fetch.php?pkg=gcc-7&arch=i386&ver=7.2.0-17&stamp=1512511504&raw=0

As for patching Firefox, getting such patches upstreamed isn't trivial
as Mozilla is very nit-picky about accepting patches and it usually
takes a lot of discussion to get them to merge things.

Anyway, I think I'm out of the discussion. I think the original poster
has received enough suggestions now how to resolve his issue.

Adrian
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: nonspammy KDE builds?

Dave Plater lst
In reply to this post by Mathias Homann-2


On 12/12/2017 11:46, Mathias Homann wrote:
> That being said: my biggest problem with that failing build is that not
> even grepping for "error" or something helped to make the log more
> readable since the developers of digikam saw fit to have several folders
> containing "error" in their name in the project, which absolutely HAD to
> be added to the include path on each moc call, hence each call having
> several -I statements with the word "error" in them.
Build logs normally contain the word "error" multiple times that's why I
suggested grepping for "error:" note the colon at the end. This normally
occurs AFAIR 3 times.
Best regards
Dave P
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

12