Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Weird Bug #356

Open
Pixdigit opened this issue Aug 28, 2018 · 4 comments
Open

Weird Bug #356

Pixdigit opened this issue Aug 28, 2018 · 4 comments
Labels
area-for-improvement This issue highlights an area that could be improved on support This issue was posted by user to ask for help

Comments

@Pixdigit
Copy link

I have absolutely no idea what why or how. Technically it probably isnt even an error with go-sdl2 but I hope you have some insight.

I have worked on my Project (branch fix_renderer) for quite some time on my laptop now. However now coming back home when I run the tests on my desktop pc I don't get any output from the renderer at all. In testEnv I made a small sample program that just fills the renderer and presents. That program worked. So I made a small test func at the bottom of screen_test.go called TestRenderer2TMP that had the exact same code. This one didn't work when run in isolation or with all other tests. So I asked a friend and he had the exact same problem on his pc. Now I run this on my laptop. When I run the test in isolation it doesn't work either. As well as the small program I wrote. However when I run the test together with all other tests it magically works again. And all of this behaviour is stable. Meaning that it doesn't change from run to run. I am completely lost and I have no idea where to begin.

@veeableful veeableful added the support This issue was posted by user to ask for help label Aug 29, 2018
@veeableful
Copy link
Contributor

Hmm I think it's because of how Go run tests and how we setup SDL currently. If you initialize SDL in your test function, it should work.

This is certainly an area that we can improve on though. I'll keep this in mind for future development!

@veeableful veeableful added the area-for-improvement This issue highlights an area that could be improved on label Aug 29, 2018
@Pixdigit
Copy link
Author

SDL is initialized in all cases the same way. There should be no difference since the exact same code is run. Or are go tests run in their own goroutine?

@veeableful veeableful added the solved? This issue might have been solved but not tested label Sep 19, 2018
@Pixdigit
Copy link
Author

Depends on what you see as solved. The error still exists but not within go-sdl2 so you decide.

@veeableful
Copy link
Contributor

@Pixdigit Ack sorry! I labeled this one by mistake. I meant to label this one. Don't mind me!

@veeableful veeableful removed the solved? This issue might have been solved but not tested label Sep 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-for-improvement This issue highlights an area that could be improved on support This issue was posted by user to ask for help
Projects
None yet
Development

No branches or pull requests

2 participants