1. Forum
  2. Usenet
  3. LINUX.DEBIAN.MAINT.BOOT

  • Gigantic build log for console-setup

    From Cyril Brulebois@21:1/5 to All on Thu Jun 20 01:10:02 2024
    Hi,

    While preparing a console-setup upload, I was a bit baffled by the heavy scrolling in my terminal, with *lots* of such lines:

    Hexadecimal number > 0xffffffff non-portable at /home/kibi/debian-installer/packages/console-setup/Fonts/bdf2psf line 478, <BDF> line 248533.

    Trying to check the previous build log, my browser would spin… and wget
    on the raw log yielded a 850+ MB file…

    Running a build locally under debuild, the .build file is 1.5 GB.

    The aforementioned pattern makes up for 10763352 lines out of 10809228.

    I have no idea about the severity of this warning, but we should
    definitely look into adressing it or silencing it in some way…

    Cc-ing the wb team for information about those huge logs. I don't have
    any metrics, but that's the kind of size that seems way higher than it
    should be.


    Cheers,
    --
    Cyril Brulebois (kibi@debian.org) <https://debamax.com/>
    D-I release manager -- Release team member -- Freelance Consultant

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmZzY8MACgkQ/5FK8MKz VSDB7g//aZZ7PkujRKC/eo3fPkomL9/trelpk2nGlEyLpdt7sVKTdXMp6ySIt3BO AW91/tdveSR327qrzELIHIE8aXMV/LnNqFXDceYXrWwRWGiYYXUCDGUoIAVACo1u 5d2dc03rFJ6T4Epx71a4r9hUPQvD/2667ouzj4ieA8vcYp61Kk03N/WfsBsf9H2H lFoXsUsXe+f4i04HyI9uH5Rz6rbfFeFrk8VcyLpc+pSjdnS6IN4DV6EalNZ0TPp0 SgQGITdRIuZ9p1OunlcyeSukYPfW3hQHS72vgFBBwgdFcb8CnerCH1xreFCNDKo4 xQIuEPYaIviXqRiobY/r8gIx7EqMGJ68ILw39Ti+bivesDC5c9j2nbroWAm16+lQ bkvl21U7Oh3AN3Q2PF9vVkIQt/xtB6pQQXSYbcuNbZ8MFiH4AgJJrLNqccYY1fAO kjsUa520p0Z3f64izeic+lORFUpMaZwDh8huGXwU3uRqqKDWbcD8pmj/TbNwPqXl aBU+LBssPYtID1RcWsBXFqWgq6SvXfKiWjwCcrYdz1bU2yENR/3EcpjYmOyzBKuu E5lTGXu3ue8glIfl4W78LnAqNBwok6JApFU13zIkME0m7LMmiounh6vR7rDjzK1U QQI8gYqq27bTqH5wk4qBDGtcIG8L0fqRIo0Qyo/0FQJ4z7j9K3g=
    =34rN
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    *
  • From Santiago Vila@21:1/5 to All on Thu Jun 20 01:30:01 2024
    El 20/6/24 a las 1:03, Cyril Brulebois escribió:
    Cc-ing the wb team for information about those huge logs. I don't have
    any metrics, but that's the kind of size that seems way higher than it
    should be.

    Hi. Some metrics for you, from my build log collection:

    -rw-r--r-- 1 master master 1339659 abr 9 03:51 console-setup_1.226_amd64-20240409T035134.494Z
    -rw-r--r-- 1 master master 1348798 may 10 06:59 console-setup_1.226_amd64-20240510T065958.220Z
    -rw-r--r-- 1 master master 1343335 may 16 17:54 console-setup_1.226_amd64-20240516T175447.452Z
    -rw-r--r-- 1 master master 1159202848 jun 6 05:55 console-setup_1.227_amd64-20240606T055523.152Z

    (I happen to keep the last four builds logs for trixie when I do QA stuff)

    Thanks.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Cyril Brulebois@21:1/5 to All on Thu Jun 20 09:10:01 2024
    Samuel Thibault <sthibault@debian.org> (2024-06-20):
    Yes, this is because of the 64-pixel-wide support for HiDPI displays
    (git 96733253b4b5). Perl complains that 64bit computation is not
    portable. I did check that on i386 the result is correct. In git
    a070f52e9adc I tried to use bigint but then it made the build *very*
    slow, so reverted it in git 0fa6a399c257. I hadn't realized that that
    warning was that numerous. Perhaps we can just filter it out?

    Maybe it would make sense to try and find out how/why/where it's not
    portable, but given the attempts and results you mentioned already,
    filtering it out wouldn't seem crazy to me, thanks.


    Cheers,
    --
    Cyril Brulebois (kibi@debian.org) <https://debamax.com/>
    D-I release manager -- Release team member -- Freelance Consultant

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEtg6/KYRFPHDXTPR4/5FK8MKzVSAFAmZz1UMACgkQ/5FK8MKz VSBXaQ/9F4Hi7C8IkU3ky4MfBCJjqp15+qsb5yrRHeab7eY3cS7M40RG5N8vfv8O EVTagnkJCSWnEVZcftm7amI88e1PyVu9wtx/updyc5HAa2Yvf4iyBdliPcJfo5+l r8a7s5xrg7ueasZiPnYo+HnIQGOGk6z590OMxVpoVukdp9C8NkHRqeeQ4hOlWLCt pXVVgy7We0MmDDKDYr27bSJsLYi41EbjxlGkWAaOmDXbxZnSQa7HF8Xj2tvZclnC jpm22fb5oCABBRdLpwC4Jq9ATPpp1ZT8tnDf1sW+1Hjju4aaPqDZRl+5iXu4+o6U fmDAjHnV29g6qdgYR/vV98aDQO7KnBe8iY7meOsTsAm3tKkFhY2rBcwy/FnHTZqk h34n1+yp9bYAQVw+6zUJA/beGv7TUuOOSME7lpHmRLkaT/DEQCWqNPHRj6JfBkxQ 62Cl+gDYa2LvXiIBSBm2LldsL1Zr+IdkLXdjN3TT0UWt0rzH+NxDvANBVKcV67xU oIT5t9ijkH2JmhPEpW5oCB46/8FPGJULp2/vm2Yh5p413pHRaHfeFxAucngvzLYW ZGvikiw6dP5hYtRt8I0xU1oX1lomiIr6DQyx64mMrPXsMARWKjEOAB2XfItuIeTP oOimOaCJ7fJ3SupUYbEpjtK1RSgXc0Jr2PyGYVl9nuy1Inp4XuQ=
    =QtpA
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    *
  • From Samuel Thibault@21:1/5 to All on Thu Jun 20 08:50:01 2024
    Hello,

    Santiago Vila, le jeu. 20 juin 2024 01:22:18 +0200, a ecrit:
    El 20/6/24 a las 1:03, Cyril Brulebois escribió:
    Cc-ing the wb team for information about those huge logs. I don't have
    any metrics, but that's the kind of size that seems way higher than it should be.

    Hi. Some metrics for you, from my build log collection:

    -rw-r--r-- 1 master master 1339659 abr 9 03:51 console-setup_1.226_amd64-20240409T035134.494Z
    -rw-r--r-- 1 master master 1348798 may 10 06:59 console-setup_1.226_amd64-20240510T065958.220Z
    -rw-r--r-- 1 master master 1343335 may 16 17:54 console-setup_1.226_amd64-20240516T175447.452Z
    -rw-r--r-- 1 master master 1159202848 jun 6 05:55 console-setup_1.227_amd64-20240606T055523.152Z

    Yes, this is because of the 64-pixel-wide support for HiDPI displays
    (git 96733253b4b5). Perl complains that 64bit computation is not
    portable. I did check that on i386 the result is correct. In git
    a070f52e9adc I tried to use bigint but then it made the build *very*
    slow, so reverted it in git 0fa6a399c257. I hadn't realized that that
    warning was that numerous. Perhaps we can just filter it out?

    Samuel

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Philipp Kern@21:1/5 to Cyril Brulebois on Thu Jun 20 10:00:02 2024
    On 2024-06-20 01:03, Cyril Brulebois wrote:
    While preparing a console-setup upload, I was a bit baffled by the
    heavy
    scrolling in my terminal, with *lots* of such lines:

    Hexadecimal number > 0xffffffff non-portable at /home/kibi/debian-installer/packages/console-setup/Fonts/bdf2psf line
    478, <BDF> line 248533.

    Trying to check the previous build log, my browser would spin… and wget
    on the raw log yielded a 850+ MB file…

    Running a build locally under debuild, the .build file is 1.5 GB.

    The aforementioned pattern makes up for 10763352 lines out of 10809228.

    I have no idea about the severity of this warning, but we should
    definitely look into adressing it or silencing it in some way…

    Cc-ing the wb team for information about those huge logs. I don't have
    any metrics, but that's the kind of size that seems way higher than it
    should be.

    I'd expect those to compress very well, though. Nominally the log size
    limit is determined by base64-encoding the gzip'ed files into emails and
    then the mail server's limit (which is higher for wuiet, as I remember
    it) is the line that you cannot cross. And indeed the file is only 22M
    on disk.

    But then I thought we'd also just serve the gzip'ed file over HTTP, but
    no, we HTML-encode it, unless raw=1 is passed. And even then we don't do
    that. Maybe that's a thing we should fix. Not that it would help any
    browsers that still want to render the whole file into a buffer.

    Kind regards
    Philipp Kern

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Samuel Thibault@21:1/5 to All on Sun Jun 23 16:20:01 2024
    Cyril Brulebois, le jeu. 20 juin 2024 09:07:50 +0200, a ecrit:
    Samuel Thibault <sthibault@debian.org> (2024-06-20):
    Yes, this is because of the 64-pixel-wide support for HiDPI displays
    (git 96733253b4b5). Perl complains that 64bit computation is not
    portable. I did check that on i386 the result is correct. In git a070f52e9adc I tried to use bigint but then it made the build *very*
    slow, so reverted it in git 0fa6a399c257. I hadn't realized that that warning was that numerous. Perhaps we can just filter it out?

    Maybe it would make sense to try and find out how/why/where it's not portable,

    The documentation for this warning is pointing at perlport(1) which
    talks about transferring integers in binary format which is not portable
    beyond 32b, so we don't care :)

    but given the attempts and results you mentioned already, filtering it
    out wouldn't seem crazy to me, thanks.

    I have now added a "no warnings" block so the warning does not even get produced.

    Samuel

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)