One encouraging thing here is that 121 of these failures (more than half) involve the tools Helgrind, DRD and exp-Ptrcheck, which are three of the less-used tools in the Valgrind distribution, and which are all completely broken on the branch, and which I haven’t really looked at yet precisely because they are less-used. Once again, this is the most important metric, and it’s improving steadily, but there’s still a long way to go. Also, 20 extra tests are being run - a broken CPU feature-detection program meant that a number of tests that should have been running were not, and this has been fixed. the number of failures went from 265 to 213. The number of regression test failures on Mac was 402/213/52/0.Now that this metric is the same on the branch as the trunk, I won’t bother tracking it in the future.
In other words, the branch works on Linux as well as the trunk. the number of failures went from 5 to 1, and that one failure occurs on my machine even on the trunk (it’s a bad test). The number of regression test failures on Linux was: 484 tests, 4 stderr failures, 1 stdout failures, 0 post failures (which I’ll abbreviate as 484/4/1/0).Here are the current (as of r9455) values of the metrics I have been using as a means of tracking progress. I’ve done a lot of them, but Julian Seward has found some time to work on the DARWIN branch and so has been doing some as well. In that time 126 commits have been made to the DARWIN branch (and a similar number to the trunk).
#Valgrind for mac os sierra mac os x
Another month has passed since I last wrote about my work on the Mac OS X port of Valgrind.
0 kommentar(er)
