| Summary: | patchwork not sending emails on behalf of patchtest | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Patchwork/Patchtest | Reporter: | Leonardo Sandoval Gonzalez <leonardo.sandoval.gonzalez> |
| Component: | Patchwork | Assignee: | Michael Halstead <mhalstead> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | major | ||
| Priority: | High | CC: | ross.burton |
| Version: | 2.3 | ||
| Target Milestone: | 2.3 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Leonardo Sandoval Gonzalez
2017-03-02 14:58:05 UTC
We know that e-mail is leaving the server and arriving as expected in some cases. Can you provide a method to test sending of test results? Maybe a method I can call or an example POST that should trigger sending a new set of results? Append the below text into your openembedded-core/.git/config file
-------
[patchwork "default"]
url = https://patchwork.openembedded.org
project = oe-core
user = <user>
password = <passwd>
-------
Then, from the repo do the following
$ git pw post-result 19 test failure --summary 'test'
The above command is what actually patchtest does, except that it uses the real ID and the test name is different (patchtest instead of test)
I just ran the above steps and seems that it is working:
-------
From: Patchwork <patchwork@patchwork.openembedded.org>
Reply-to: <openembedded-core@lists.openembedded.org>
To: michael@yoctoproject.org, leonardo.sandoval.gonzalez@intel.com
Subject: ✗ test: failure for initramfs-framework enhancements
Date: Fri, 3 Mar 2017 20:00:47 +0000 (03/03/2017 02:00:47 PM)
== Series Details ==
Series: initramfs-framework enhancements
Revision: 1
URL : https://patchwork.openembedded.org/series/19/
State : failure
== Summary ==
test
-------
So, apparently, it the problem is when sending the email to the mailing list (perhaps the ML is blocking emails from patchwork?)
Let me know if this info is enough to progress in your side.
When I run git-pw as the patchtest user posts do appear. http://lists.openembedded.org/pipermail/openembedded-core/2017-March/134481.html However. even though patchtest/scripts/guest is running every 30 minutes and new patches have been posted I don't see any new e-mail from patchtest. Perhaps we just haven't had any failures to report. Leo and I will continue watching. (In reply to comment #3) > When I run git-pw as the patchtest user posts do appear. > http://lists.openembedded.org/pipermail/openembedded-core/2017-March/134481. > html > > However. even though patchtest/scripts/guest is running every 30 minutes and > new patches have been posted I don't see any new e-mail from patchtest. > Perhaps we just haven't had any failures to report. Leo and I will continue > watching. Right, no failures have occurred. I will monitor the list and the pw site, and check for failures results/emails in both places. I let you know if everything is back to normal as soon as possible. Confirmed working. Yay! |