* [Buildroot] [autobuild.buildroot.net] Build results for 2018-11-25
@ 2018-11-26 7:00 Thomas Petazzoni
2018-11-26 17:50 ` Matthew Weber
0 siblings, 1 reply; 6+ messages in thread
From: Thomas Petazzoni @ 2018-11-26 7:00 UTC (permalink / raw)
To: buildroot
Hello,
Build statistics for 2018-11-25
===============================
branch | OK | NOK | TIM | TOT |
2018.02.x | 22 | 1 | 0 | 23 |
2018.08.x | 21 | 1 | 0 | 22 |
master | 213 | 5 | 0 | 218 |
next | 30 | 7 | 0 | 37 |
Results for branch '2018.02.x'
==============================
Classification of failures by reason
------------------------------------
audit-2.8.2 | 1
Detail of failures
------------------
i686 | audit-2.8.2 | NOK | http://autobuild.buildroot.net/results/8de651c8b390ba443cc3b0584c0095409d31e71f |
Results for branch '2018.08.x'
==============================
Classification of failures by reason
------------------------------------
libmpeg2-0.5.1 | 1
Detail of failures
------------------
powerpc | libmpeg2-0.5.1 | NOK | http://autobuild.buildroot.net/results/964e1356e17677de7eedf959fc005c1a594e1314 | ORPH
Results for branch 'master'
===========================
Classification of failures by reason
------------------------------------
dante-1.4.1 | 1
libmpeg2-0.5.1 | 1
msgpack-2.1.5 | 1
uboot-tools-2018.07 | 1
valgrind-3.14.0 | 1
Detail of failures
------------------
mips64el | dante-1.4.1 | NOK | http://autobuild.buildroot.net/results/e37e61bae1d81a7956e2843be70fea84b0bbb64b |
powerpc | libmpeg2-0.5.1 | NOK | http://autobuild.buildroot.net/results/8e4d25e2d91409833a92cafdc688b55d4c91b5c8 | ORPH
aarch64 | msgpack-2.1.5 | NOK | http://autobuild.buildroot.net/results/7d7aa9723f02f9bc78dbf6248674be4d402199bf |
arm | uboot-tools-2018.07 | NOK | http://autobuild.buildroot.net/results/0729a7739a7dc8dee46b63e81045b7d6bce34d09 |
mips64el | valgrind-3.14.0 | NOK | http://autobuild.buildroot.net/results/418443386731f12686cabc2e719ef667ad7b9338 | ORPH
Results for branch 'next'
=========================
Classification of failures by reason
------------------------------------
tpm2-abrmd-2.0.3 | 3
mender-1.4.0 | 2
qemu-2.12.1 | 1
setools-4.1.1 | 1
Detail of failures
------------------
x86_64 | mender-1.4.0 | NOK | http://autobuild.buildroot.net/results/c933f3398126f12091cc6be68ebcc7de47e8ee41 |
x86_64 | mender-1.4.0 | NOK | http://autobuild.buildroot.net/results/475b41fe938bec3e2515e9a0389a23aa89d952b4 |
mipsel | qemu-2.12.1 | NOK | http://autobuild.buildroot.net/results/c255e0e6a9054a3e11416e950d1459ccb8572413 |
powerpc64le | setools-4.1.1 | NOK | http://autobuild.buildroot.net/results/e214e1a539cdac07028fb58c3822f89886d86f1f |
sparc | tpm2-abrmd-2.0.3 | NOK | http://autobuild.buildroot.net/results/e6c0f41d9ec427391f783c287003cdfa455768d0 |
mips64el | tpm2-abrmd-2.0.3 | NOK | http://autobuild.buildroot.net/results/4cac7998ade80a7a9bfa3af2c0a9b71f5ff885e0 |
powerpc | tpm2-abrmd-2.0.3 | NOK | http://autobuild.buildroot.net/results/b7c4e1b81293f19fac518e2dbe771552a7275576 |
--
http://autobuild.buildroot.net
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Build results for 2018-11-25
2018-11-26 7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-11-25 Thomas Petazzoni
@ 2018-11-26 17:50 ` Matthew Weber
2018-11-28 22:52 ` Arnout Vandecappelle
0 siblings, 1 reply; 6+ messages in thread
From: Matthew Weber @ 2018-11-26 17:50 UTC (permalink / raw)
To: buildroot
All,
On Mon, Nov 26, 2018 at 1:01 AM Thomas Petazzoni
<thomas.petazzoni@bootlin.com> wrote:
>
> Hello,
>
> Build statistics for 2018-11-25
> ===============================
>
> branch | OK | NOK | TIM | TOT |
> 2018.02.x | 22 | 1 | 0 | 23 |
> 2018.08.x | 21 | 1 | 0 | 22 |
> master | 213 | 5 | 0 | 218 |
> next | 30 | 7 | 0 | 37 |
>
> Results for branch '2018.02.x'
> ==============================
>
> Classification of failures by reason
> ------------------------------------
>
> audit-2.8.2 | 1
>
>
> Detail of failures
> ------------------
>
> i686 | audit-2.8.2 | NOK | http://autobuild.buildroot.net/results/8de651c8b390ba443cc3b0584c0095409d31e71f |
>
> Results for branch '2018.08.x'
> ==============================
>
> Classification of failures by reason
> ------------------------------------
>
> libmpeg2-0.5.1 | 1
>
>
> Detail of failures
> ------------------
>
> powerpc | libmpeg2-0.5.1 | NOK | http://autobuild.buildroot.net/results/964e1356e17677de7eedf959fc005c1a594e1314 | ORPH
>
> Results for branch 'master'
> ===========================
>
> Classification of failures by reason
> ------------------------------------
>
> dante-1.4.1 | 1
> libmpeg2-0.5.1 | 1
> msgpack-2.1.5 | 1
> uboot-tools-2018.07 | 1
> valgrind-3.14.0 | 1
>
>
> Detail of failures
> ------------------
>
> mips64el | dante-1.4.1 | NOK | http://autobuild.buildroot.net/results/e37e61bae1d81a7956e2843be70fea84b0bbb64b |
> powerpc | libmpeg2-0.5.1 | NOK | http://autobuild.buildroot.net/results/8e4d25e2d91409833a92cafdc688b55d4c91b5c8 | ORPH
> aarch64 | msgpack-2.1.5 | NOK | http://autobuild.buildroot.net/results/7d7aa9723f02f9bc78dbf6248674be4d402199bf |
> arm | uboot-tools-2018.07 | NOK | http://autobuild.buildroot.net/results/0729a7739a7dc8dee46b63e81045b7d6bce34d09 |
> mips64el | valgrind-3.14.0 | NOK | http://autobuild.buildroot.net/results/418443386731f12686cabc2e719ef667ad7b9338 | ORPH
>
> Results for branch 'next'
> =========================
>
> Classification of failures by reason
> ------------------------------------
>
> tpm2-abrmd-2.0.3 | 3
> mender-1.4.0 | 2
> qemu-2.12.1 | 1
> setools-4.1.1 | 1
>
>
> Detail of failures
> ------------------
>
> x86_64 | mender-1.4.0 | NOK | http://autobuild.buildroot.net/results/c933f3398126f12091cc6be68ebcc7de47e8ee41 |
> x86_64 | mender-1.4.0 | NOK | http://autobuild.buildroot.net/results/475b41fe938bec3e2515e9a0389a23aa89d952b4 |
> mipsel | qemu-2.12.1 | NOK | http://autobuild.buildroot.net/results/c255e0e6a9054a3e11416e950d1459ccb8572413 |
> powerpc64le | setools-4.1.1 | NOK | http://autobuild.buildroot.net/results/e214e1a539cdac07028fb58c3822f89886d86f1f |
setools package is installing man pages and were caught using a bad
path by 'step_check_build_dir'. To stop the install of the man pages,
is the preference a 'sed' to remove a line in setup.py or a 'rm' as a
hook to cleanup the install of the files to staging/target?
Matt
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Build results for 2018-11-25
2018-11-26 17:50 ` Matthew Weber
@ 2018-11-28 22:52 ` Arnout Vandecappelle
2018-11-28 23:06 ` Angelo Compagnucci
0 siblings, 1 reply; 6+ messages in thread
From: Arnout Vandecappelle @ 2018-11-28 22:52 UTC (permalink / raw)
To: buildroot
On 26/11/2018 18:50, Matthew Weber wrote:
> All,
>
>
> On Mon, Nov 26, 2018 at 1:01 AM Thomas Petazzoni
> <thomas.petazzoni@bootlin.com> wrote:
[snip]
>> powerpc64le | setools-4.1.1 | NOK | http://autobuild.buildroot.net/results/e214e1a539cdac07028fb58c3822f89886d86f1f |
>
> setools package is installing man pages and were caught using a bad
> path by 'step_check_build_dir'. To stop the install of the man pages,
> is the preference a 'sed' to remove a line in setup.py or a 'rm' as a
> hook to cleanup the install of the files to staging/target?
Well, fix setup.py of course :-)
This is caused by e94280e5a537b "package/pkg-python: use proper --prefix and
--root values". It changed:
- --prefix=$(TARGET_DIR)/usr
+ --prefix=/usr \
+ --root=$(TARGET_DIR)
setools setup.py does:
data_files=[(join(sys.prefix, 'share/man/man1'), glob.glob("man/*.1"))],
To me, that actually looks like the right thing to do...
Angelo, maybe you have an idea?
Regards,
Arnout
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Build results for 2018-11-25
2018-11-28 22:52 ` Arnout Vandecappelle
@ 2018-11-28 23:06 ` Angelo Compagnucci
2018-11-29 0:29 ` Matthew Weber
0 siblings, 1 reply; 6+ messages in thread
From: Angelo Compagnucci @ 2018-11-28 23:06 UTC (permalink / raw)
To: buildroot
Hi Arnout,
Il giorno mer 28 nov 2018 alle ore 23:52 Arnout Vandecappelle
<arnout@mind.be> ha scritto:
>
>
>
> On 26/11/2018 18:50, Matthew Weber wrote:
> > All,
> >
> >
> > On Mon, Nov 26, 2018 at 1:01 AM Thomas Petazzoni
> > <thomas.petazzoni@bootlin.com> wrote:
> [snip]
> >> powerpc64le | setools-4.1.1 | NOK | http://autobuild.buildroot.net/results/e214e1a539cdac07028fb58c3822f89886d86f1f |
> >
> > setools package is installing man pages and were caught using a bad
> > path by 'step_check_build_dir'. To stop the install of the man pages,
> > is the preference a 'sed' to remove a line in setup.py or a 'rm' as a
> > hook to cleanup the install of the files to staging/target?
>
> Well, fix setup.py of course :-)
>
> This is caused by e94280e5a537b "package/pkg-python: use proper --prefix and
> --root values". It changed:
>
> - --prefix=$(TARGET_DIR)/usr
> + --prefix=/usr \
> + --root=$(TARGET_DIR)
>
> setools setup.py does:
>
> data_files=[(join(sys.prefix, 'share/man/man1'), glob.glob("man/*.1"))],
>
> To me, that actually looks like the right thing to do...
>
> Angelo, maybe you have an idea?
For me is wrong, [1] says:
" If directory is a relative path, it is interpreted relative to the
installation prefix (Python?s sys.prefix for pure-Python packages,
sys.exec_prefix for packages that contain extension modules)"
So the sys.prefix should not be joined because the correct one will be
added regardless. The reason why a relative path is going to work is
because the installation path is built internally joining python root
with python prefix, thus forming the correct path $(TARGET_DIR)/usr.
Joining the sys.prefix makes the path absolute: this was previously
working by accident.
So that should be
data_files=[('share/man/man1', glob.glob("man/*.1"),],
[1] https://docs.python.org/3/distutils/setupscript.html#installing-additional-files
>
> Regards,
> Arnout
Sincerely, Angelo
--
Profile: http://it.linkedin.com/in/compagnucciangelo
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Build results for 2018-11-25
2018-11-28 23:06 ` Angelo Compagnucci
@ 2018-11-29 0:29 ` Matthew Weber
2018-11-29 7:53 ` Thomas Petazzoni
0 siblings, 1 reply; 6+ messages in thread
From: Matthew Weber @ 2018-11-29 0:29 UTC (permalink / raw)
To: buildroot
All,
On Wed, Nov 28, 2018 at 5:07 PM Angelo Compagnucci
<angelo.compagnucci@gmail.com> wrote:
>
> Hi Arnout,
>
> Il giorno mer 28 nov 2018 alle ore 23:52 Arnout Vandecappelle
> <arnout@mind.be> ha scritto:
> >
> >
> >
> > On 26/11/2018 18:50, Matthew Weber wrote:
> > > All,
> > >
> > >
> > > On Mon, Nov 26, 2018 at 1:01 AM Thomas Petazzoni
> > > <thomas.petazzoni@bootlin.com> wrote:
> > [snip]
> > >> powerpc64le | setools-4.1.1 | NOK | http://autobuild.buildroot.net/results/e214e1a539cdac07028fb58c3822f89886d86f1f |
> > >
> > > setools package is installing man pages and were caught using a bad
> > > path by 'step_check_build_dir'. To stop the install of the man pages,
> > > is the preference a 'sed' to remove a line in setup.py or a 'rm' as a
> > > hook to cleanup the install of the files to staging/target?
> >
> > Well, fix setup.py of course :-)
> >
> > This is caused by e94280e5a537b "package/pkg-python: use proper --prefix and
> > --root values". It changed:
> >
> > - --prefix=$(TARGET_DIR)/usr
> > + --prefix=/usr \
> > + --root=$(TARGET_DIR)
> >
> > setools setup.py does:
> >
> > data_files=[(join(sys.prefix, 'share/man/man1'), glob.glob("man/*.1"))],
> >
> > To me, that actually looks like the right thing to do...
> >
> > Angelo, maybe you have an idea?
>
>
> For me is wrong, [1] says:
>
> " If directory is a relative path, it is interpreted relative to the
> installation prefix (Python?s sys.prefix for pure-Python packages,
> sys.exec_prefix for packages that contain extension modules)"
>
> So the sys.prefix should not be joined because the correct one will be
> added regardless. The reason why a relative path is going to work is
> because the installation path is built internally joining python root
> with python prefix, thus forming the correct path $(TARGET_DIR)/usr.
>
> Joining the sys.prefix makes the path absolute: this was previously
> working by accident.
>
> So that should be
>
> data_files=[('share/man/man1', glob.glob("man/*.1"),],
>
> [1] https://docs.python.org/3/distutils/setupscript.html#installing-additional-files
>
Thanks for the investigation. I'll get a patch sent upstream and to
the list for a fix.
I haven't looked but we search and remove all man pages as part of a
target finalized, right?
Matt
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Buildroot] [autobuild.buildroot.net] Build results for 2018-11-25
2018-11-29 0:29 ` Matthew Weber
@ 2018-11-29 7:53 ` Thomas Petazzoni
0 siblings, 0 replies; 6+ messages in thread
From: Thomas Petazzoni @ 2018-11-29 7:53 UTC (permalink / raw)
To: buildroot
Hello,
On Wed, 28 Nov 2018 18:29:26 -0600, Matthew Weber wrote:
> I haven't looked but we search and remove all man pages as part of a
> target finalized, right?
Yes:
target-finalize: $(PACKAGES) host-finalize
[...]
rm -rf $(TARGET_DIR)/usr/man $(TARGET_DIR)/usr/share/man
[...]
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2018-11-29 7:53 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-11-26 7:00 [Buildroot] [autobuild.buildroot.net] Build results for 2018-11-25 Thomas Petazzoni
2018-11-26 17:50 ` Matthew Weber
2018-11-28 22:52 ` Arnout Vandecappelle
2018-11-28 23:06 ` Angelo Compagnucci
2018-11-29 0:29 ` Matthew Weber
2018-11-29 7:53 ` Thomas Petazzoni
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox