You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm updating from 1.0.0 to 1.1.0 in Debian unstable, and during my build/test procedure I found that an automated test was intermittently getting stuck. As a smoke-test for new versions, I run this script https://salsa.debian.org/python-team/packages/rgain3/-/blob/debian/master/debian/tests/replaygain in a virtual machine. The expected result is that it performs replay gain analysis on the four test audio clips found in the same directory as the script itself, as though they were an album (they're actually short clips taken from sound-theme-freedesktop), then terminates successfully.
However, the result I'm actually getting in the test VM is that it hangs, like this:
Checking for Replay Gain information ...
message-new-instant.oga:none
phone-incoming-call.oga:none
phone-outgoing-busy.oga:none
phone-outgoing-calling.oga:none
Calculating Replay Gain information ...
message-new-instant.oga:7.70 dB
phone-incoming-call.oga:-8.91 dB
phone-outgoing-busy.oga:
(replaygain:1723): GStreamer-WARNING **: 11:55:36.510: ../gst/gstpad.c:4621:gst_pad_push_data:<multiqueue2:src_0> Got data flow before segment event
(replaygain:1723): GStreamer-WARNING **: 11:55:36.510: ../gst/gstpad.c:4368:gst_pad_chain_data_unchecked:<vorbisdec2:sink> Got data flow before segment event
(replaygain:1723): GStreamer-WARNING **: 11:55:36.510: ../gst/gstpad.c:4621:gst_pad_push_data:<vorbisdec2:src> Got data flow before segment event
(replaygain:1723): GStreamer-WARNING **: 11:55:36.510: ../gst/gstpad.c:4368:gst_pad_chain_data_unchecked:<src_2:proxypad6> Got data flow before segment event
(replaygain:1723): GStreamer-WARNING **: 11:55:36.510: ../gst/gstpad.c:4621:gst_pad_push_data:<decbin:src_2> Got data flow before segment event
(replaygain:1723): GStreamer-WARNING **: 11:55:36.510: ../gst/gstpad.c:4368:gst_pad_chain_data_unchecked:<conv:sink> Got data flow before segment event
(replaygain:1723): GStreamer-WARNING **: 11:55:36.510: ../gst/gstpad.c:4621:gst_pad_push_data:<conv:src> Got data flow before segment event
(replaygain:1723): GStreamer-WARNING **: 11:55:36.510: ../gst/gstpad.c:4368:gst_pad_chain_data_unchecked:<res:sink> Got data flow before segment event
(replaygain:1723): GStreamer-WARNING **: 11:55:36.510: ../gst/gstpad.c:4621:gst_pad_push_data:<res:src> Got data flow before segment event
(replaygain:1723): GStreamer-WARNING **: 11:55:36.510: ../gst/gstpad.c:4368:gst_pad_chain_data_unchecked:<rg:sink> Got data flow before segment event
(replaygain:1723): GStreamer-WARNING **: 11:55:36.510: ../gst/gstpad.c:4621:gst_pad_push_data:<rg:src> Got data flow before segment event
I'm updating from 1.0.0 to 1.1.0 in Debian unstable, and during my build/test procedure I found that an automated test was intermittently getting stuck. As a smoke-test for new versions, I run this script https://salsa.debian.org/python-team/packages/rgain3/-/blob/debian/master/debian/tests/replaygain in a virtual machine. The expected result is that it performs replay gain analysis on the four test audio clips found in the same directory as the script itself, as though they were an album (they're actually short clips taken from sound-theme-freedesktop), then terminates successfully.
However, the result I'm actually getting in the test VM is that it hangs, like this:
Message https://marc.info/?l=gstreamer-devel&m=138703546904972&w=2 on the GStreamer upstream mailing list suggests that this might be to do with the change in commit d5cfdd8 - maybe it shouldn't be sending a flush event?
Unfortunately I can't seem to reproduce this when not in the virtual machine, so perhaps it's timing-related.
The text was updated successfully, but these errors were encountered: