On 03/24/2015 04:41 AM, Robert Park wrote:
On Tue, Mar 24, 2015 at 1:18 AM, Alberto Mardegan
wrote:
Well, I think that this has bit me in the past too. The problem is that
if you pass "013" as the silo number, then it's taken as an octal
number. :-)
Maybe the citrain tool should strip leading 0
On Tue, Mar 24, 2015 at 1:18 AM, Alberto Mardegan
wrote:
> Well, I think that this has bit me in the past too. The problem is that
> if you pass "013" as the silo number, then it's taken as an octal
> number. :-)
> Maybe the citrain tool should strip leading 0s.
$ printf "%03d" 013
011
Well, I
On 03/23/2015 09:37 PM, Robert Park wrote:
> On Mon, Mar 23, 2015 at 7:33 AM, Tony Espy wrote:
>> I noticed over the weekend that 'citrain device-upgrade' was getting the
>> silo wrong ( ie. I'd specified ubuntu silo 13, and it started to process
>> silo 11 ).
>
> I have no idea how that could ev
On Mon, Mar 23, 2015 at 12:44 PM, Tony Espy wrote:
>> In short, neither of the issues you've described are possible.
>
> Never say never...
Right, sorry.
> Will let you know if I see either again.
Thanks.
The thing is, the spreadsheet is known to be largely unreliable, but
the problems you've
On 03/23/2015 03:37 PM, Robert Park wrote:
On Mon, Mar 23, 2015 at 7:33 AM, Tony Espy wrote:
I noticed over the weekend that 'citrain device-upgrade' was getting the
silo wrong ( ie. I'd specified ubuntu silo 13, and it started to process
silo 11 ).
I have no idea how that could even be remot
On Mon, Mar 23, 2015 at 7:33 AM, Tony Espy wrote:
> I noticed over the weekend that 'citrain device-upgrade' was getting the
> silo wrong ( ie. I'd specified ubuntu silo 13, and it started to process
> silo 11 ).
I have no idea how that could even be remotely possible. Unless your
pin is "0011" a
On 03/17/2015 08:58 PM, Robert Park wrote:
Hi everybody,
Just a quick status update regarding the CI Train Spreadsheet.
This issue has been known to bite us from time to time, we've been
fortunate not to run into this for a while now but since yesterday
it's back with a vengeance.
What's happe
On Wed, Mar 18, 2015 at 3:52 AM, Timo Jyrinki
wrote:
> I've restored all missing landings from the
> dashboards at the end of the spreadsheet with "description lost".
Ah, thanks for that. I started doing that towards the end of my shift
yesterday but I was still getting "Fatal errors" at that tim
On Wed, Mar 18, 2015 at 4:12 AM, Stephen M. Webb
wrote:
> On 15-03-18 05:19 AM, Łukasz 'sil2100' Zemczak wrote:
>> Once I feel better I'll also try
>> to add some optimizations to the old cow.
>
> Just out of curiosity, is there any new messaging on the replacement for this
> temporary tool other
On 15-03-18 05:19 AM, Łukasz 'sil2100' Zemczak wrote:
> Once I feel better I'll also try
> to add some optimizations to the old cow.
Just out of curiosity, is there any new messaging on the replacement for this
temporary tool other than "the beginning
of 2014"?
--
Stephen M. Webb
--
Mailing
Thanks for the link, Łukasz! Indeed the errors seem to have
disappeared so far. I've restored all missing landings from the
dashboards at the end of the spreadsheet with "description lost". The
link to the dashboard however works for all of them so status is
updated, the silo can be marked as teste
Hey Robert!
It seems to have somewhat helped, probably the Reconfigure links took
some load off from the spreadsheet. I noticed a decrease in the number
of error reports from the spreadsheet itself, so it should be once again
safe to use (for now). Thanks for that! Once I feel better I'll also try
12 matches
Mail list logo
