| Summary: | Patchtest seems to be off-line and not working | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Patchwork/Patchtest | Reporter: | Armin Kuster <akuster> |
| Component: | Patchwork | Assignee: | Changqing Li <changqing.li> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | High | CC: | randy.macleod, richard.purdie |
| Version: | unspecified | ||
| Target Milestone: | 2.8 M2 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Armin Kuster
2019-04-16 15:36:38 UTC
sorry, not sure if this a patchwork issue or some other resource. I am looking for the system that reviewed incoming patches and rejected them if not following proper format. is the server alive? last patch was Nov 2018 and I think this went off line in Feb http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe/commit/?id=f944f21b436dab48160d20e23b033bdf7acdaab0 last patchwork change was Nov 2017 did we move to group.io email services? Moved to M2 but we want this done ASAP. have switched patchtest to the new one yesterday, monitor for one day, seems work well, keep monitor for a while, if no problem, I will close this defect. Was the transition made? If so we could close this? Have implement on new server from 2019.7.9. Seems work well these days, so close this bug |