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 noticed that cctest.exe run failure doesn't show as test failure. For e.g. here is the CI run triggered for node-chakracore and it says test pass even if test case inside cctest hits an assert. Is there any reason of not having a post-build action step to parse cctest.tap output similar to test.tap output?
I think on non-windows, the make job will anyway fail if cctest fails, so this is only problem for windows.
Looks like cctest.tap was not added to the Windows job as it probably should have been when it was added to others. It can be easily added, but only when cctest passes on Windows, to avoid breaking all runs.
Activity
joaocgreis commentedon Jun 26, 2017
Looks like
cctest.tapwas not added to the Windows job as it probably should have been when it was added to others. It can be easily added, but only when cctest passes on Windows, to avoid breaking all runs.refack commentedon Jul 6, 2017
ping nodejs/node#14111
kunalspathak commentedon Jul 21, 2017
Updated jenkins job : https://ci.nodejs.org/job/node-test-binary-windows/jobConfigHistory/showDiffFiles?timestamp1=2017-06-25_20-05-00×tamp2=2017-07-21_12-36-26