Builder libpsl-solaris10-amd64 Build #339

Results:

Failed shell_2 shell_3

SourceStamp:

BuildSlave:

Reason:

The AnyBranchScheduler scheduler named 'schedule-libpsl-pr' triggered this build

Steps and Logfiles:

1. git update ( 2 secs )
   1. stdio
2. shell 'bash autogen.sh' ( 34 secs )
   1. stdio
3. shell_1 './configure --with-psl-file=/opt/csw/share/public_suffix_list.dat' ( 10 secs )
   1. stdio
   2. config.log
4. shell_2 'gmake' failed ( 5 secs )
   1. stdio
5. shell_3 'gmake check' failed ( 0 secs )
   1. stdio
   2. test-suite.log

Build Properties:

Forced Build Properties:

Responsible Users:

1. Eli Schwartz

   eschwartz93ohnoyoudont@gmail.com

Timing:

All Changes:

:

1. Change #192567

   Category	None
   Changed by	Eli Schwartz <eschwartz93ohnoyoudont@gmail.com>
   Changed at	Thu 07 Mar 2024 21:39:07
   Repository	https://github.com/rockdaboot/libpsl
   Project	rockdaboot/libpsl
   Branch	es/python-find_program
   Revision	b201380ede40b4d83b44eb9c5df9b56f3e43b2d4

   Comments

   meson: simplify python3 detection
   
   Don't look up the python module's find_installation() method. This is
   intended for detecting lots of information needed for compiling and
   installing python modules including the C-API interface to libpython, as
   well as site-packages layout information.
   
   It's totally uninvolved with what we are doing, which is executing a
   script. For this, we just need any python program. Meson is written in
   python3, so we know in meson.build that we have that available -- which
   is also why meson guarantees that `find_program('python3')` always
   returns a valid python. Even if no python is installed on the system,
   meson will return the `meson.exe runpython` shim which runs the script
   using the copy of python bundled inside the redistributable meson
   Windows executable.

   Changed files

   • meson.build