Tobias Gruetzmacher

mambu: Hi, is this happening only for "parametrized" builds or for every kind of build? Just to know where to start investigating. Thanks

mambu: Is this still an issue? It seems that the dashboard is behaving correctly anyway because you said: In actuality, my main job has 4 tests, and the three sub...

scottdeagan: This is happening for both parameterized builds and every kind of build. It is particularly annoying for parameterized builds. For example: 1. I have a build-pipeline. 2. The default...

mambu: I'm closing this one. Reopen it, if still an issue.

mambu: Ok, but what happens when you do the same but starting with a view that is not a "dashboard-view"? Which page are you redirect to after hitting "build"? I...

ellisonch: It still seems like an issue to me. I will try to attach more information.

ikedam: This is a issue with "parameterized project", which is a project with parameters, not a project with parameterized-trigger plugin. If no fixes will be done in dashboard-view, please close...

ellisonch: I've added an attachment showing what I mean. If you add up all the child tests except for the csmith-tests, you get 1554. This number is being reported for...

mambu: I don't understand the behaviour either, but you said that this also happens when displaying the test results in jenkins. This is important because we don't do any special...

ellisonch: On the c-semantics project page, it says "Latest Test Result (85 failures / ±0)" without double counting that. If I click that link, it gives me "5 tests", which...