public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Feedback on test of latest pakfire-builder build
Date: Mon, 05 Feb 2024 14:44:46 +0100	[thread overview]
Message-ID: <70a196f6-3408-437f-8a20-161ed3999a31@ipfire.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 5220 bytes --]

Hi Michael,

I saw that there were new commits to the pakfire repo so I thought I 
would test it out and see what happened.

The build worked for all stages except for the make check command.

This failed with the following result.

make check
make --no-print-directory check-recursive
Making check in .
make --no-print-directory tests/libpakfire/main tests/libpakfire/arch 
tests/libpakfire/archive tests/libpakfire/build tests/libpakfire/cgroup 
tests/libpakfire/compress tests/libpakfire/config tests/libpakfire/db 
tests/libpakfire/dependencies tests/libpakfire/digest 
tests/libpakfire/file tests/libpakfire/httpclient tests/libpakfire/jail 
tests/libpakfire/key tests/libpakfire/makefile tests/libpakfire/os 
tests/libpakfire/package tests/libpakfire/packager 
tests/libpakfire/parser tests/libpakfire/path tests/libpakfire/repo 
tests/libpakfire/snapshot tests/libpakfire/string tests/libpakfire/util 
tests/libpakfire/xfer tests/libtestsuite.la \
   tests/python/archive.py tests/python/ctx.py tests/python/keys.py 
tests/python/jail.py tests/python/package.py
   CC       tests/libpakfire/main-main.o
   CC       tests/libtestsuite_la-testsuite.lo
tests/testsuite.c: In function 'test_run':
tests/testsuite.c:89:35: warning: passing argument 1 of 'pakfire_bind' 
from incompatible pointer type [-Wincompatible-pointer-types]
    89 |                 r = pakfire_bind(t->pakfire, TEST_STUB_COMMAND, 
"/command", 0);
       |                                  ~^~~~~~~~~
       |                                   |
       |                                   struct pakfire *
In file included from tests/testsuite.c:28:
./src/libpakfire/include/pakfire/mount.h:42:38: note: expected 'struct 
pakfire_ctx *' but argument is of type 'struct pakfire *'
    42 | int pakfire_bind(struct pakfire_ctx* ctx, struct pakfire* pakfire,
       |                  ~~~~~~~~~~~~~~~~~~~~^~~
<command-line>: warning: passing argument 2 of 'pakfire_bind' from 
incompatible pointer type [-Wincompatible-pointer-types]
tests/testsuite.c:89:46: note: in expansion of macro 'TEST_STUB_COMMAND'
    89 |                 r = pakfire_bind(t->pakfire, TEST_STUB_COMMAND, 
"/command", 0);
       | ^~~~~~~~~~~~~~~~~
./src/libpakfire/include/pakfire/mount.h:42:59: note: expected 'struct 
pakfire *' but argument is of type 'char *'
    42 | int pakfire_bind(struct pakfire_ctx* ctx, struct pakfire* pakfire,
       | ~~~~~~~~~~~~~~~~^~~~~~~
tests/testsuite.c:89:21: error: too few arguments to function 'pakfire_bind'
    89 |                 r = pakfire_bind(t->pakfire, TEST_STUB_COMMAND, 
"/command", 0);
       |                     ^~~~~~~~~~~~
./src/libpakfire/include/pakfire/mount.h:42:5: note: declared here
    42 | int pakfire_bind(struct pakfire_ctx* ctx, struct pakfire* pakfire,
       |     ^~~~~~~~~~~~
make[3]: *** [Makefile:4574: tests/libtestsuite_la-testsuite.lo] Error 1
make[2]: *** [Makefile:5947: check-am] Error 2
make[1]: *** [Makefile:5285: check-recursive] Error 1
make: *** [Makefile:5951: check] Error 2


I then tried running the pakfire builder with beep and sqlite. In the 
past beep usually worked okay but sqlite had the file descriptor error.

Beep built without any problems but sqlite failed again. There is still 
a mention about file descriptor but I think it looks a bit different to 
what was shown in the past.



Feb 05 14:24:55 ipfire pakfire[13232]: Command Output: make[1]: Leaving 
directory '/build/source/sqlite-autoconf-3430100'
Feb 05 14:24:55 ipfire pakfire[13232]: Command Output: make: *** 
[Makefile:915: install-am] Error 2
Feb 05 14:24:55 ipfire pakfire[13232]: The child process exited with code 2
Feb 05 14:24:55 ipfire pakfire[13232]: Build stage 'install' failed with 
status 2
Feb 05 14:24:55 ipfire pakfire[13232]: Set environment variable: 
PS1=pakfire-jail \w>
Feb 05 14:24:55 ipfire pakfire[13232]: Set environment variable: 
TERM=xterm-256color
Feb 05 14:24:55 ipfire pakfire[13232]: Set environment variable: 
LANG=en_GB.UTF-8
Feb 05 14:24:55 ipfire pakfire[13232]: Executing jail...
Feb 05 14:24:55 ipfire pakfire[13232]: Parent has finished initialization
Feb 05 14:24:55 ipfire pakfire[13232]: Sending signal...
Feb 05 14:24:55 ipfire pakfire[13232]: Waiting for PID 15761 to finish 
its work
Feb 05 14:24:55 ipfire pakfire[13232]: Could not add file descriptor 0 
to epoll(): Invalid argument
Feb 05 14:24:55 ipfire pakfire[13232]: Failed setting up PTY forwarding: 
Invalid argument
Feb 05 14:24:55 ipfire pakfire[13232]: Could not destroy cgroup: Device 
or resource busy
Feb 05 14:24:55 ipfire pakfire[13232]: Freeing jail at 0x5b324d9e5dd0
Feb 05 14:24:55 ipfire pakfire[13232]: Could not destroy cgroup: Device 
or resource busy
Feb 05 14:24:55 ipfire pakfire[13232]: Removing 
sqlite-3.43.1-1.ipfire3.src at /var/tmp/sqlite-3.43.1-1.ipfire3.src.pfm


Regards,
Adolf.


-- 
Sent from my laptop


                 reply	other threads:[~2024-02-05 13:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=70a196f6-3408-437f-8a20-161ed3999a31@ipfire.org \
    --to=adolf.belka@ipfire.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox