Some tests are flaky on develop

[Jacalz]

Checklist

• I have searched the issue tracker for open issues that relate to the same problem, before opening a new one.
• This issue only relates to a single bug. I will open new issues for any other problems.

Describe the bug

I, and likely many others, have noticed that a few tests are flaky on develop. We should get this fixed to avoid spending lots of time rerunning tests. The idea with this issue is that we can note down the ones as we find them and then tick them off:

• Objects are reported as not equal but printout says that they are the same:

  fyne/data/binding/preference_test.go

  Line 12 in 22234be

  func TestBindPreference_DataRace(t *testing.T) {

• This is sometimes nil:

  fyne/internal/driver/glfw/window_test.go

  Line 1131 in 22234be

  if e, _ := o.popSecondaryTapEvent().(*fyne.PointEvent); assert.NotNil(t, e, "tapped secondary") {

How to reproduce

1. Run tests. More noticeable on CI (and likely slower hardware).

Screenshots

No response

Example code

Tests are relevant. See list above.

Fyne version

22234be

Go compiler version

1.24.3

Operating system and version

Fedora Silverblue 41

Additional Information

No response

[andydotxyz]

One is nailed :) the other has been an issue for years and I was hopeful it was covered by race work but it seems not.

[Jacalz]

Nice one. Yeah, indeed. I think there also is one or two more inside the glfw tests that haven't been added to this list yet. We really need to get these squashed once for all :)