Closed yurivict closed 3 years ago
what is wrong with the test harness?
It's probably bitrotten and doesn't work anymore with current mujs.
Is there an updated test harness?
See https://github.com/ccxvii/mujs/issues/49#issuecomment-821925719
Would it be better to not apply special patches to MuJS but run the mujs process separately for each test?
I'm not sure what you're saying/suggesting/implying. The patchset which I posted at the other issue do run each test in a new mujs instance because otherwise (like it was initially with one mujs instance for all tests) it causes more issues.
Your patch includes patch to main.c
. If tests are run in individual sessions there should be no need to patch C, no?
Test harness and instructions how to run it should be committed into the repository.
Sorry, I don't really understand what you're trying to say. Are you trying to clarify something for yourself? are you saying the patch has an issue or problem? are you making some suggestion?
Here's what I suggest:
And then if you have questions, or suggestions, or you notice issues, then please ask again, clearly.
Please do not be condescending.
I am sorry that your low level of intellect doesn't allow you an oppotunity to comprehend more advanced matters.
Perhaps you should quit commenting here and change to something more accessible to you.
Glad you could vent off. When you find the time to ask a question clearly to help me understand better what you want, I'll try to answer as best as I can.
I am trying to follow this method to run tests: https://github.com/ccxvii/mujs/issues/49#issuecomment-416935229
Individual cases run:
but they fail when both cases are run sequentially:
Is there an updated test harness, or what is wrong with the test harness?