status.linaro.org

Emails about missing milestones

Bug #1017878 reported by Данило Шеган
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
status.linaro.org
Fix Released
High
Milo Casagrande
status.linaro.org 2012.07

Bug Description

I'm repeatedly getting emails with every run of the collect script that say:

https://launchpad.net/linaro-image-tools/+spec/linaro-platform-generic-bootloader-config
  [WARNING] milestone "2012.07" is unknown/invalid

Basically it doesn't see a new milestone.

Related branches

lp:~milo/launchpad-work-items-tracker/bug1017878
Данило Шеган (community): Approve
Diff: 213 lines (+43/-29)
2 files modified
collect (+32/-14)
lpworkitems/collect.py (+11/-15)
Milo Casagrande (milo)
Changed in linaro-status-website:
assignee: nobody → Milo Casagrande (milo)
Milo Casagrande (milo)
Changed in linaro-status-website:
status: Triaged → In Progress
Revision history for this message
Milo Casagrande (milo) wrote :

Just an update on this one.
Running it locally, now I get the same error with this:

 https://launchpad.net/gcc-linaro/+spec/backport-longlong-improvements
   [WARNING] milestone "4.7-2012.04" is unknown/invalid

And a couple more, all of 'gcc-linaro'. What I am doing now is running the debugger after applying Danilo's patch, but looks like there is no 'gcc-linaro' project name, so I have to dig a little bit deeper in the problem and see what is going on.

Revision history for this message
Milo Casagrande (milo) wrote : Re: [Bug 1017878] Re: Emails about missing milestones

The linked branch should fix the problem for the original report.
The error about gcc-linaro I think is related to the fact that there
is no 4.7 project in the configuration file. Locally testing and
refreshing the DB with 4.7, I no longer have those errors.

--
Milo Casagrande
Infrastructure Engineer
Linaro.org <www.linaro.org> │ Open source software for ARM SoCs

Milo Casagrande (milo)
Changed in linaro-status-website:
status: In Progress → Fix Committed
milestone: none → 2012.07
Revision history for this message
Milo Casagrande (milo) wrote :

Marking as fix released: status.linaro.org is automatically updated via a cron job, and looks like the problem is now fixed.
As per a brief IRC chat with Danilo, looks like no more warning emails are produced.

Changed in linaro-status-website:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.