bug#68034: Pull failure

2023-12-26 Thread Sergey Trofimov



this has been fixed in 3e41b252cfc81508bfcd0ac7103df212b35c3b91





bug#68031: Error running Guix pull: no code for module (gnu packages ed)

2023-12-26 Thread Sergey Trofimov

Richard Sent  writes:

This has been fixed in 3e41b252cfc81508bfcd0ac7103df212b35c3b91


Hi all,

Noticed this error when running Guix pull today. Not entirely 
sure of the
problem, but the console said to report it and I didn't notice 
any identical bug

reports recently.

Full log attached. Abridged version below.

ice-9/boot-9.scm:3330:6: In procedure resolve-interface:
no code for module (gnu packages ed)
Computing Guix derivation for 'x86_64-linux'...  guix pull: 
error: You found a

bug: the program
'/gnu/store/zd32rmipj4nqlq6rnc0mv638x3i7yvfs-compute-guix-derivation'
failed to compute the derivation for Guix (version:
"2a66a96634b33667a45f4493a37eef48033b7287"; system: 
"x86_64-linux";
host version: "49a7a95ba44e231e9e15a274f9a96de6fa012daf"; 
pull-version: 1).
Please report the COMPLETE output above by email to 
.






bug#57868: GStreamer gst_gstsystemclock test fails on CI for i686

2023-12-26 Thread Nicolas Graves via Bug reports for GNU Guix
On 2023-12-25 19:00, Nicolas Graves wrote:

> Hi Marius,
>
> I think a similar issue also happens on x86_64. For some reason, the
> binary is available through guix weather, but I'm unable to build the
> package locally (with --check). Can you confirm it's not just on my
> side?

Sorry it's not the gst_gstsystemclock but rather the
libs_gstnetclientclock that fails consistently. You can ignore the patch
sent. 

>  
> I'm going to send a patch which basically adds this phase for all
> platforms after this email, I'll be using this locally. 
>
> Cheers,
> Nicolas 
>
>
> On 2022-09-17 00:30, Marius Bakke wrote:
>
>> Hi,
>>
>> On i686-linux, the gstreamer gst_gstsystemclock test is failing:
>>
>> --8<---cut here---start->8---
>>  41/108 gst_gstsystemclockFAIL1.26s   exit status 2
> GST_PLUGIN_SYSTEM_PATH_1_0='' CK_DEFAULT_TIMEOUT=600 
> GST_STATE_IGNORE_ELEMENTS='' MALLOC_PERTURB_=230 
> GST_PLUGIN_SCANNER_1_0=/tmp/guix-build-gstreamer-1.20.3.drv-0/build/libs/gst/helpers/gst-plugin-scanner
>  GST_PLUGIN_LOADING_WHITELIST=gstreamer 
> GST_REGISTRY=/tmp/guix-build-gstreamer-1.20.3.drv-0/build/tests/check/gst_gstsystemclock.registry
>  GST_PLUGIN_PATH_1_0=/tmp/guix-build-gstreamer-1.20.3.drv-0/build 
> /tmp/guix-build-gstreamer-1.20.3.drv-0/build/tests/check/gst_gstsystemclock
>> ? ?  
>> ?
>> stdout:
>> Running suite(s): GstSystemClock
>> 75%: Checks: 8, Failures: 0, Errors: 2
>> ../gstreamer-1.20.3/tests/check/gst/gstsystemclock.c:263:E:waiting:test_stress_cleanup_unschedule:0:
>>  (after this point) Received signal 5 (Trace/breakpoint trap)
>> ../gstreamer-1.20.3/tests/check/gst/gstsystemclock.c:263:E:waiting:test_stress_reschedule:0:
>>  (after this point) Received signal 5 (Trace/breakpoint trap)
>> Check suite gst_systemclock ran in 1.236s (tests failed: 2)
>> stderr:
>>
>> (gst_gstsystemclock:5546): GLib-ERROR **: 22:57:16.217: creating thread 
>> 'wait': Error creating thread: Resource temporarily unavailable
>>
>> (gst_gstsystemclock:6027): GLib-ERROR **: 22:57:16.340: creating thread 
>> 'wait': Error creating thread: Resource temporarily unavailable
>> ??
>> --8<---cut here---end--->8---
>>
>> Full log output here:
>>
>>   https://ci.guix.gnu.org/build/1305526/log/raw
>>
>> I'm not able to reproduce this locally.  Any idea what might be going on
>> here?  Parallelism issue?
>>
>> Note: we have disabled these tests on i686 for a long time, but they
>> were recently enabled again on 'staging'.  I'll re-apply that hunk to
>> disable the test, but wanted to have an issue to link to.
>>
>>
>>

-- 
Best regards,
Nicolas Graves





bug#67956: bug

2023-12-26 Thread Josselin Poiret via Bug reports for GNU Guix
Hi Sebastian,

Sebastian Boccardi  writes:

> host version: "1.2.0"; pull-version: 1).

Where is your Guix daemon from?  It seems fairly ancient at this point
(a couple of years old) and should be upgraded.  It might not be the
cause of the problem but that might be a good thing to do first.

Best,
-- 
Josselin Poiret


signature.asc
Description: PGP signature


bug#68053: Docker 20.10.25 fails test on aarch64

2023-12-26 Thread Christian Miller via Bug reports for GNU Guix
Hi,

on aarch64, Docker fails the "daemon/logger TestRingLogge" test.

This is the case for guix revision
"ee7c9d254117fa470686210ad2ef5e7f1ba4fefc" (~100 days old) and
"5bd80ccd69047b149e24d4adf2c951b5d14b" (current latest as of
writing)

There is no substitute available for this package as well on aarch64.

--8<---cut here---start->8---
=== Failed
=== FAIL: daemon/logger TestRingLogger (0.01s)
ring_test.go:46: expected no more messages in the queue, got: "3"


DONE 2123 tests, 65 skipped, 1 failure in 1184.399s
error: in phase 'check': uncaught exception:
%exception #<&invoke-error program: "hack/test/unit" arguments: () exit-status: 
1 term-signal: #f stop-signal: #f> 
phase `check' failed after 1188.6 seconds
command "hack/test/unit" failed with status 1

Some deprecated features have been used.  Set the environment
variable GUILE_WARN_DEPRECATED to "detailed" and rerun the
program to get more information.  Set it to "no" to suppress
this message.
builder for `/gnu/store/wnk3w8z4wwh6lmwfaabacp3rpn051qcf-docker-20.10.25.drv' 
failed with exit code 1
build of /gnu/store/wnk3w8z4wwh6lmwfaabacp3rpn051qcf-docker-20.10.25.drv failed
View build log at 
'/var/log/guix/drvs/wn/k3w8z4wwh6lmwfaabacp3rpn051qcf-docker-20.10.25.drv.gz'.
guix build: error: build of 
`/gnu/store/wnk3w8z4wwh6lmwfaabacp3rpn051qcf-docker-20.10.25.drv' failed
--8<---cut here---end--->8---



k3w8z4wwh6lmwfaabacp3rpn051qcf-docker-20.10.25.drv.gz
Description: Binary data


-- 
Christian Miller


bug#68055: lightdm and lightdm-gtk-greeter do not show session menu in guix.

2023-12-26 Thread Feng Shu



See previous info:   https://issues.guix.gnu.org/57168


> It works fine, but there are a few gotchas:

> 1. The session selection menu doesn't show the items.  I don't know why.
> Perhaps a regresssion with newer GTK+.

I use below code to test:

1. lightdm-gtk-greeter code:
>>> 
>>> > >
> /* Session menu */
> >
> g_debug (": Call lightdm_get_sessions functions from main");  
> >
> items = lightdm_get_sessions ();  
> >
> g_debug (": Session menuitem create start."); 
> >
> if (gtk_widget_get_visible (session_menuitem))
> >
> { 
> >
> GSList *sessions = NULL;  
> >
>   
> >
> if (gtk_icon_theme_has_icon (icon_theme, 
> "document-properties-symbolic")) >
> session_badge = gtk_image_new_from_icon_name 
> ("document-properties-symbolic", GTK_ICON_SIZE_MENU);>
> else  
> >
> session_badge = gtk_image_new_from_icon_name 
> ("document-properties", GTK_ICON_SIZE_MENU); >
> gtk_widget_show (session_badge);  
> >
> gtk_container_add (GTK_CONTAINER (session_menuitem), session_badge);  
> >
>   
> >
> items = lightdm_get_sessions ();  
> >
> for (item = items; item; item = item->next)   
> >
> { 
> >
> LightDMSession *session = item->data; 
> >
> GtkWidget *radiomenuitem; 
> >
>   
> >
> g_debug (": Session items: %s", lightdm_session_get_key 
> (session));   >
>   
> >
> radiomenuitem = gtk_radio_menu_item_new_with_label (sessions, 
> lightdm_session_get_name (session));>
> g_object_set_data (G_OBJECT (radiomenuitem), SESSION_DATA_KEY, 
> (gpointer) lightdm_session_get_key (session)); >
> sessions = gtk_radio_menu_item_get_group (GTK_RADIO_MENU_ITEM 
> (radiomenuitem));   >
> g_signal_connect (G_OBJECT (radiomenuitem), "activate", 
> G_CALLBACK (session_selected_cb), NULL);  >
> gtk_menu_shell_append (GTK_MENU_SHELL (session_menu), 
> radiomenuitem); >
> gtk_widget_show (GTK_WIDGET (radiomenuitem)); 
> >
> } 
> >
>   
> >
> set_session (NULL);   
> >
> } 
> >
>   
>