Test timed out: LoopInButton_QuantizeEnabledNoBeats

[uklotzde]

Bug Description

https://koji.rpmfusion.org/kojifiles/work/tasks/3696/623696/build.log

The following tests FAILED:
	434 - LoopingControlTest.LoopInButton_QuantizeEnabledNoBeats (Timeout)

Build task: https://koji.rpmfusion.org/koji/buildinfo?buildID=27603

Version

2.4.0

OS

Fedora 40

[uklotzde]

I have disabled all LoopingControlTest to avoid future failures.

[ronso0]

maybe just a missing ProcessBuffer(); after

m_pButtonLoopIn->set(1);
m_pButtonLoopIn->set(0);

here

mixxx/src/test/looping_control_test.cpp

Lines 249 to 257 in dc22fd5

	TEST_F(LoopingControlTest, LoopInButton_QuantizeEnabledNoBeats) {
	m_pQuantizeEnabled->set(1);
	m_pClosestBeat->set(-1);
	m_pNextBeat->set(-1);
	setCurrentPosition(mixxx::audio::FramePos{50});
	m_pButtonLoopIn->set(1);
	m_pButtonLoopIn->set(0);
	EXPECT_FRAMEPOS_EQ_CONTROL(mixxx::audio::FramePos{50}, m_pLoopStartPoint);
	}

?
Can that be tested without a PR/merge?

[daschuer]

For my understanding a timeout happens when a call does not return for some reasons. All the calls in the test body should return immediately. So my guess is that something in the test setup got stuck or the test runner itself.

Was the time out a single instance or is it reproducible?

[uklotzde]

For my understanding a timeout happens when a call does not return for some reasons. All the calls in the test body should return immediately. So my guess is that something in the test setup got stuck or the test runner itself.

Was the time out a single instance or is it reproducible?

Not reproducible. But likely a race condition in Mixxx.