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
I do not know whether this preexisting issue was the cause of the failure of my commit or not. But the test was passing for the previous commits I had made. The failure happened only in this commit where I add new functionality to add plots in the outer table even if the user wants fixed location for some plots and not for the others.
The same error is occurring even for chromote testing branch ( #126 ) as well. So I think it is preexisting issue in the main branch.
The text was updated successfully, but these errors were encountered:
I'm not sure about "Uncaught ReferenceError: animint is not defined"
but the test failure " ── Failure ('test-renderer1-global-variables.R:37:3'): animint.js only defines 1 object, called animint " in https://github.com/animint/animint2/actions/runs/10147526896/job/28058108659?pr=139 means that your new JS code is defining some global variables other than animint.
This test makes sure that we only define animint, and no other global variables, in JS code.
@tdhock @Faye-yufan
I noticed an error on browser console during the execution of test renderer1-global-variables.
The error on browser console is as follows:
animint-htmltest/:20 Uncaught ReferenceError: animint is not defined
at animint-htmltest/:20:18
But the test still passes in R.
This is the only failing test case for the following commit I made for the html table task(#139 ):
0a78f92
I do not know whether this preexisting issue was the cause of the failure of my commit or not. But the test was passing for the previous commits I had made. The failure happened only in this commit where I add new functionality to add plots in the outer table even if the user wants fixed location for some plots and not for the others.
The same error is occurring even for chromote testing branch ( #126 ) as well. So I think it is preexisting issue in the main branch.
The text was updated successfully, but these errors were encountered: