Project: email-test Build #: 29 Status: Still Failing Timestamp: 20190110T173515Z Check attached log for details. -------------------------------------------------------------------------------- Parameters P1: foo P2: bar

Project: email-test Build #: 31 Status: Still Failing Timestamp: 20190110T185259Z Check attached log for details. -------------------------------------------------------------------------------- Parameters P1: foo P2: bar

Apologies folks for the spam. That was the last one. I was just debugging the last link in the chain of getting build reports from CENGN to starlingx-discuss.  Turns out the only bug was to add my email to the receiver list.  Thunderbird happily merged the two e-mails onto one, using the direct mail's version of the Subject field (lacking [starlingx-discuss] prefix), thus tricking me into believing the messages weren't being accepted by the mailing list. Messages with *[build-report]* in the subject will now be from real build jobs.  Only build failures will be reported, plus the first successful build once the issue is corrected.  There will likely be two mails per failure, one from the master job, and one from the sub-job that had the failure. I encourage you to monitor these e-mails, particularly if you submitted code within 24 hours prior to a failure. Scott On 2019-01-10 2:49 p.m., build.starlingx@gmail.com wrote:

Project: email-test Build #: 32 Status: Still Failing

Timestamp: 20190110T194948Z

Check attached log for details. -------------------------------------------------------------------------------- Parameters

P1: foo P2: bar

_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss