No error messages or logging output in Stdout

Builder
23

I don’t know about closing the Runner - we never closed the Runner or never instructed our students to do so. But students sometimes are still able to surprise me :slight_smile: However, it is possible to reproduce the problem without closing the Runner.
We asked some students experiencing the problem to go back to version 2020.1.3 - it is the most recent version that does not have the issue.

24

This is the file we had problems with. The problem is with a typo in the text object when referencing excel column (“kolor” instead of “kolory”), but the error does not appear when running the experiment: the psychopy experiment screen is shown but then closes without errors shown. For this file the error is still hidden if we use “send to runner”.
We’ve just confirmed that opening PsychoPy (2020.2.3) first and then opening the file via file → open leads to errors being shown in the runner. We are now testing this with 2020.2.8 (you release versions fast!).
These are the files:
list.xlsx (4.7 KB) exercise2.psyexp (6.9 KB)

edit:
Good news: the problematic file works well on 2020.2.8, meaning the error is shown in the Runner! :slight_smile: We tested that file earlier on 2020.2.5 at some point and still had the problem so maybe something was fixed after 2020.2.5?). We will test some other files that produced this error and ask some students to see if 2020.2.8 works for them and will let you all know!

1 Like
25

Cool, thanks @mmagnuski
Basically, there are several routes by which the Runner window could be activated and it turned out we hadn’t included the check for stdout in all of them. I think we’re there now! :slight_smile:

1 Like