Open Bugs:
http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2 Failing Tests: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/lastCompletedBuild/testReport/ and a failing build of non-Core: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/8/console Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
Marcus,
Here we have a "blue" build: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/11/ How did you manage that? :P Did you remove the test run from the build? Guille On Mon, Dec 13, 2010 at 1:54 PM, Marcus Denker <[hidden email]> wrote: Open Bugs: |
In reply to this post by Marcus Denker-4
On Dec 14, 2010, at 2:35 AM, Guillermo Polito wrote: Marcus,yes... I was wondering where exactly the process was failing (but then, one can see that fom the console)... Next step: remove the deprecated calls (or change deprecation warning setting) then I will turn on the tests again. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
In reply to this post by Marcus Denker-4
On Dec 13, 2010, at 5:54 PM, Marcus Denker wrote: > Open Bugs: > > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2 > All failing tests now have a bug tracker entry. There is now a bug milestone defined for the full image: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
Nice work!
Doru On 14 Dec 2010, at 11:09, Marcus Denker wrote: > > On Dec 13, 2010, at 5:54 PM, Marcus Denker wrote: > >> Open Bugs: >> >> http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2 >> > All failing tests now have a bug tracker entry. > > There is now a bug milestone defined for the full image: > > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage > > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- www.tudorgirba.com "It's not what we do that matters most, it's how we do it." |
In reply to this post by Marcus Denker-4
Nice work!
Doru On 14 Dec 2010, at 11:09, Marcus Denker wrote: > > On Dec 13, 2010, at 5:54 PM, Marcus Denker wrote: > >> Open Bugs: >> >> http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2 >> > All failing tests now have a bug tracker entry. > > There is now a bug milestone defined for the full image: > > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2-DevImage > > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > -- www.tudorgirba.com "It's not what we do that matters most, it's how we do it." |
In reply to this post by Marcus Denker-4
Why in the first link even with the selection "Open Issues", items marked "Fixed" or "Closed" are showing?
Just trying to understand... -- Cesar Rabak Em 13/12/2010 14:54, Marcus Denker < [hidden email] > escreveu: Open Bugs: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2 Failing Tests: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/lastCompletedBuild/testReport/ and a failing build of non-Core: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/8/console Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
In reply to this post by Marcus Denker-4
On Dec 14, 2010, at 9:34 PM, [hidden email] wrote: > Why in the first link even with the selection "Open Issues", items marked "Fixed" or "Closed" are showing? > Closed: a bug of the bug tracker. Highly annyoing. Fixed. This means: the entry contains something that is a propesed fix in a loadable form. Needs to be integrated. But sometimes, it means more something like "Stef wants to look at this later and if it's not tagged it will be lost". :-) Marus > Just trying to understand... > > -- > Cesar Rabak > > > > > > Em 13/12/2010 14:54, Marcus Denker < [hidden email] > escreveu: > Open Bugs: > > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2 > > Failing Tests: > > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/lastCompletedBuild/testReport/ > > > and a failing build of non-Core: > > https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/8/console > > > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. |
On Dec 14, 2010, at 9:39 PM, Marcus Denker wrote: > > On Dec 14, 2010, at 9:34 PM, [hidden email] wrote: > >> Why in the first link even with the selection "Open Issues", items marked "Fixed" or "Closed" are showing? >> > > Closed: a bug of the bug tracker. Highly annyoing. > Fixed. This means: the entry contains something that is a propesed fix in a loadable form. Needs to be integrated. > > But sometimes, it means more something like "Stef wants to look at this later and if it's not tagged it will be lost". :-) yes may be we should have that instead of FixedWaitingToBePharoed > > Marus > > > >> Just trying to understand... >> >> -- >> Cesar Rabak >> >> >> >> >> >> Em 13/12/2010 14:54, Marcus Denker < [hidden email] > escreveu: >> Open Bugs: >> >> http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.2 >> >> Failing Tests: >> >> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%20Core%201.2/lastCompletedBuild/testReport/ >> >> >> and a failing build of non-Core: >> >> https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.2/8/console >> >> >> >> Marcus >> >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> >> > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > |
Free forum by Nabble | Edit this page |