Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Restore Morning Email #17

Open
wmwolf opened this issue Sep 4, 2020 · 3 comments
Open

Restore Morning Email #17

wmwolf opened this issue Sep 4, 2020 · 3 comments
Assignees
Labels

Comments

@wmwolf
Copy link
Member

wmwolf commented Sep 4, 2020

Due to changes in the backend of the testhub, the morning e-mail will not work in the new testhub as is. The "all commits" page will be a decent substitute in the short term, but this is pretty critical.

@wmwolf
Copy link
Member Author

wmwolf commented Sep 4, 2020

The e-mail (even in the current "old" testhub) should also be sent to the slack testing channel so we aren't beholden to slow listserves.

@wmwolf
Copy link
Member Author

wmwolf commented Nov 18, 2020

Though this isn't completed, the current morning mailer has moved over to the mailgun service from sendgrid, which was causing problems. This actually makes development much easier due to weirdness we had with sendgrid, and we're also sending it to the slack now. Styling is stripped by slack, and their support tells me the only way to get it back is through building our own integration. Not worth it to me at this point.

@wmwolf
Copy link
Member Author

wmwolf commented Dec 17, 2020

With the launch of "new testhub" and the official mesa repo, the morning e-mail lives again, but not without cost. It has gained

  • ability to know when a commit has not been fully tested (indicates x out of y cases tested)
  • ability to indicate how many computers have tested at least one case vs all cases (x computers tested; y complete)

It is currently missing

  • memory leak detection
  • runtime bloat detection

These two are always more annoying to implement, and now they need to be aware of test instances running optional inlists or not. More to come, but it's no longer blocking development from resuming.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant