After a VTK commit is made, CDash sends out emails to the committer if any build or test failures occur in nightly builds. This was enabled presumably to help point out errors that may have been introduce, but typically the emails include unrelated persistent failures on the dashboards and cause con…

It is rarely usefull and when it is, gets discarded as the usual “spam from the nightly”. I’d say to disable it, someone would still need to monitor the nightly dashboard to see new failures. Ideally, the nightly should be part of the CI or at least triggered on merge, not during the night.

Ideally, the nightly should be part of the CI or at least triggered on merge, not during the night. Latest master builds are triggered by changes to master. External sites (e.g., RogueResearch machines) run nightly.

I don’t like the idea of disabling them. It would be preferable to make them more useful. Already I have the suspicion that people just trash them, which is unfortunate. Every once in a while I fix all the warnings reported by my bots (or git blame and ping people), but then next I look there are…

My proposal was poorly worded. Instead of disabling emails altogether, I meant, should we disable automatically sending contributors email even though they haven’t opted in to receiving emails from CDash? In this day and age, it seems problematic to send emails that are not specifically requested. T…

This might be wishful thinking but is it not possible for CDash to identify the erroneous file(s) and only email developers whose change sets include that file/those files?

[image] seanm: It feels to me like people only pay attention to gitlab and not CDash. Definitely not. People are looking at the CDash of their own MR, they are not looking at the whole CDash 24hours after merging to check if they broke something, and imo, they should not be expected to. CDa…

[image] toddy: This might be wishful thinking but is it not possible for CDash to identify the erroneous file(s) and only email developers whose change sets include that file/those files? Ideally, but it’s hard enough for a human to track down which changes may have contributed to a particula…

Mathieu, I should have been clearer, when I said I felt people ignored cdash, I indeed meant nightly submissions (like mine). I disagree that developers shouldn’t be expected to check the nightly dashboards. As you know, VTK supports many platforms and many build option permutations, and the build…

[image] seanm: Cory, if you’re not a cdash admin for vtk, who is? @ben.boeckel

[image] seanm: Would really help to know the current setting for the purposes of this discussion. That box is currently unchecked.

VTK

Emails from CDash

Development

show post in topic

Home
Categories
Guidelines
Terms of Service
Privacy Policy

Powered by Discourse, best viewed with JavaScript enabled