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
Adding to #96 (comment), after the discussion with Barret and Shalu, we noticed that this specific instances of time out are due to 200-flexdashboard-render-text app's shinyjster test being stopped.
This started happening since the shinyjster test has been added for above app.
Browser is opened and immediately closed. Also, notice the time stamp after the last run of this app. The process waited for 3 hours to timeout. Is there a way not to wait for such a long period of time to timeout. Can we just return the test results for the apps which ran successfully similar to other builds (Mac and Ubuntu)?
The text was updated successfully, but these errors were encountered:
MadhulikaTanuboddi
changed the title
Windows builds timeout due to 200-flexdashboard-render-text shinyjster test's interruption
GHA: Windows builds timeout due to 200-flexdashboard-render-text shinyjster test's interruption
Apr 16, 2021
Have added temp patch in #137 to disable windows shinyjster checks. I've updated the tests there.
The tests are still failing due to random html being produced. 🙄
Adding to #96 (comment), after the discussion with Barret and Shalu, we noticed that this specific instances of time out are due to
200-flexdashboard-render-text
app's shinyjster test being stopped.This started happening since the shinyjster test has been added for above app.
Detailed logs below
starting from https://github.com/rstudio/shinycoreci-apps/runs/2285509215?check_suite_focus=true#step:31:26659
Browser is opened and immediately closed. Also, notice the time stamp after the last run of this app. The process waited for 3 hours to timeout. Is there a way not to wait for such a long period of time to timeout. Can we just return the test results for the apps which ran successfully similar to other builds (Mac and Ubuntu)?
The text was updated successfully, but these errors were encountered: