upgrade to 2a stuck ? (6 days)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Sergei wrote:
> New question #113252 on Launchpad Bazaar Integration:
> https://answers.launchpad.net/launchpad-code/+question/113252
>
> mariadb 5.1 branch https://code.launchpad.net/~maria-captains/maria/5.1-converting
> is in the "An upgrade of this branch is in progress." for 6 days now.
> This seems to be too long even for a slow upgrading process.
>

Are you running without the extensions compiled? I agree that 6-days
seems excessive.

Another possibility is to grab most of the history from somewhere else,
and then branch in the remainder.

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkwGovAACgkQJdeBCYSNAANnSwCfZBvMFBlA8req+bsemo/0zkGO
WoQAoJz18Xcm0/NIZwvwaHJOXpySAjiS
=Q4qL
-----END PGP SIGNATURE-----

Eh, it's in this state in launchpad. See the url above.
Locally it usually takes 20-30 hours to convert this branch.

There is no process running on the server that does these upgrades.
I can't see anything pertinent in the logs for same either.
My 2c is that the state for this task has gotten confused within the database (or similar) and hence we see the invalid message.

Would suggest creating a bug report, linked to this question, for resolving same.

On Thu, 03 Jun 2010 13:10:54 you wrote:
> Question #113252 on Launchpad Bazaar Integration changed:
> https://answers.edge.launchpad.net/launchpad-code/+question/113252
>
> Status: Open => Needs information
>
> Steve McInerney requested for more information:
> There is no process running on the server that does these upgrades.
> I can't see anything pertinent in the logs for same either.
> My 2c is that the state for this task has gotten confused within the
> database (or similar) and hence we see the invalid message.
>
> Would suggest creating a bug report, linked to this question, for
> resolving same.

I talked this through with the developers this morning, and we think we know
the cause. It is a spurious error message.

On Thu, 03 Jun 2010 14:03:15 you wrote:
> Question #113252 on Launchpad Bazaar Integration changed:
> https://answers.launchpad.net/launchpad-code/+question/113252
>
> Status: Needs information => Answered
>
> Tim Penhey proposed the following answer:
>
> On Thu, 03 Jun 2010 13:10:54 you wrote:
> > Question #113252 on Launchpad Bazaar Integration changed:
> > https://answers.edge.launchpad.net/launchpad-code/+question/113252
> >
> > Status: Open => Needs information
> >
> > Steve McInerney requested for more information:
> > There is no process running on the server that does these upgrades.
> > I can't see anything pertinent in the logs for same either.
> > My 2c is that the state for this task has gotten confused within the
> > database (or similar) and hence we see the invalid message.
> >
> > Would suggest creating a bug report, linked to this question, for
> > resolving same.
>
> I talked this through with the developers this morning, and we think we
> know the cause. It is a spurious error message.

Actually this is different than what we thought. There was a job in our DB
saying it was running when it wasn't. We should try to figure out why it was
saying that.

This is, of course, great, that you have diagnosed the problem.

But the branch still has a warning about upgrade in progress.
What should we do ?
Wait ? I'm happy to, but the status of the question "Answered" looks confusing to me.
Or should we create a bug and track the problem there ?
Or something else ?

On Thu, 03 Jun 2010 19:53:36 you wrote:
> Question #113252 on Launchpad Bazaar Integration changed:
> https://answers.edge.launchpad.net/launchpad-code/+question/113252
>
> Status: Answered => Open
>
> Sergei is still having a problem:
> This is, of course, great, that you have diagnosed the problem.
>
> But the branch still has a warning about upgrade in progress.
> What should we do ?
> Wait ? I'm happy to, but the status of the question "Answered" looks
> confusing to me. Or should we create a bug and track the problem there ?
> Or something else ?

The branch is currently upgrading. Lets see if it finishes properly.

I think replying by email marks it answered for some reason.

Tim

It has finished, but not properly. The branch format hasn't changed.

We identified the problem with the upgrade job, and that has been released to production, so we shouldn't see this again (fingers crossed).

This branch is now showing 2a correctly.