Weird, especially since it says there were no changes in the builds, and
since the build before and after are all correct...
Maybe some connection issues to another repo during the build? But then it
would have been notified in the console output...
Let us know if you find out!
On Sun, Jun 30, 2013 at 11:22 PM, Istimsak Abdulbasir
saqman2...@gmail.comwrote:
Must of been a mistake
On Sun, Jun 30, 2013 at 10:12 AM, Scott Kitterman ubu...@kitterman.comwrote:
This is the first Jenkins failure mail I've gotten. I can't make sense
of it.
Was there even a test run? Why was the mail sent?
Scott K
-- Forwarded Message --
Subject: Jenkins Failure - saucy-adt-python-qt4 5
Date: Sunday, June 30, 2013, 08:11:16 AM
From: Jenkins Notification devn...@canonical.com
To: ubuntu-testing-notificati...@lists.ubuntu.com, jean-
baptiste.lallem...@canonical.com, martin.p...@ubuntu.com,
ubu...@kitterman.com
saucy-adt-python-qt4 - Build # 5 - Failure:
Public Jenkins URL:
https://jenkins.qa.ubuntu.com/job/saucy-adt-python-qt4/5
to view the results.
Private Jenkins URL: http://10.189.74.2:8080/job/saucy-adt-python-qt4/5
-
--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
--
Pierre Equoy
--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
