Closed Bug 833001 Opened 12 years ago Closed 12 years ago

commit issues on svn repo from Verbatim

Categories

(mozilla.org Graveyard :: Server Operations, task)

x86
Linux
task
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: pascalc, Assigned: dumitru)

References

Details

Besnik has this message today when committing to VCS, I also had the same message for French, the problem seems to be intermittent: Failed to commit file: [SVN] Error running SVN command '['svn', '-q', '--non-interactive', 'commit', '-m', u'Commit from Mozilla Verbatim by user besnik@programeshqip.org.: 358 of 360 messages translated (0 fuzzy).', '--with-revprop', u'translate:author=besnik@programeshqip.org <besnik@programeshqip.org>', u'/data/www/localize.mozilla.org/verbatim/pootle_env/Pootle/po/firefoxflicks/sq/LC_MESSAGES/ messages.po']': Connection to svn.mozilla.org closed by remote host. svn: Commit failed (details follow): svn: Network connection closed unexpectedly
Also happened to our Spanish localizer a few minutes ago, looks like Verbatim loses its svn network connection for a few minutes and then it works again.
Intermittent network errors? Over to IT.
Assignee: nobody → server-ops-webops
Component: Verbatim → Server Operations: Web Operations
Product: Webtools → mozilla.org
QA Contact: nmaul
Version: Trunk → other
Assignee: server-ops-webops → server-ops-devservices
Component: Server Operations: Web Operations → Server Operations: Developer Services
QA Contact: nmaul → shyam
Although I'm not sure which group this belongs in - if it's Zeus then Webops, if it's svn then Shyam's group, if it's a true network problem then Netops. Starting in webops for triage. How urgent is it to get this fixed? (ie should it page somebody today, on a US holiday, or will tomorrow or longer still be soon enough?)
Assignee: server-ops-devservices → server-ops-webops
Component: Server Operations: Developer Services → Server Operations: Web Operations
QA Contact: shyam → nmaul
Sorry for the midair, solarce.
Assignee: server-ops-webops → server-ops-devservices
Component: Server Operations: Web Operations → Server Operations: Developer Services
QA Contact: nmaul → shyam
I think tomorrow is OK because since it's intermittent, we can just wait a few minutes and try again and it works. It would be good to have it fixed tomorrow however, because we need to push to VCS translations for the Firefox Flicks release.
Has this happened again?
(In reply to Shyam Mani [:fox2mike] from comment #6) > Has this happened again? I continue to experience it.
Is this over ssh or https? Can you paste svn info here (for the directory you're trying to commit to?)
the problem is with the verbatim webapp (localize.mozilla.org) which allows committing the translations to the svn repo there: https://svn.mozilla.org/projects/l10n-misc/trunk I don't know if Verbatim uses svn+ssh or https protocol to commit.
(In reply to Pascal Chevrel:pascalc from comment #9) > the problem is with the verbatim webapp (localize.mozilla.org) which allows > committing the translations to the svn repo there: > https://svn.mozilla.org/projects/l10n-misc/trunk > > I don't know if Verbatim uses svn+ssh or https protocol to commit. I'll try some test commits there. The issue could be with verbatim then.
(In reply to Besnik Bleta from comment #7) > (In reply to Shyam Mani [:fox2mike] from comment #6) > > Has this happened again? > > I continue to experience it. Does this happen everytime? Or intermittently?
(In reply to Shyam Mani [:fox2mike] from comment #8) > Is this over ssh or https? Can you paste svn info here (for the directory > you're trying to commit to?) Here you are: Failed to commit file: [SVN] Error running SVN command '['svn', '-q', '--non-interactive', 'commit', '-m', u'Commit from Mozilla Verbatim by user besnik@programeshqip.org.: 358 of 360 messages translated (0 fuzzy).', '--with-revprop', u'translate:author=besnik@programeshqip.org <besnik@programeshqip.org>', u'/data/www/localize.mozilla.org/verbatim/pootle_env/Pootle/po/firefoxflicks/sq/LC_MESSAGES/messages.po']': svn: Commit failed (details follow): svn: File '/projects/l10n-misc/trunk/firefoxflicks/locale/sq/LC_MESSAGES/messages.po' is out of date
> Does this happen everytime? Or intermittently? I could say intermittently. I've seen it in the past, but not for all projects under Verbatim. Once fixed for a specific project, I don't recall having troubles for that project.
(In reply to Besnik Bleta from comment #12) > Here you are: > u'/data/www/localize.mozilla.org/verbatim/pootle_env/Pootle/po/firefoxflicks/ > sq/LC_MESSAGES/messages.po']': svn: Commit failed (details follow): svn: > File > '/projects/l10n-misc/trunk/firefoxflicks/locale/sq/LC_MESSAGES/messages.po' > is out of date This is not an issue with svn, it's an out of date file in Verbatim.
Assignee: server-ops-devservices → nobody
Component: Server Operations: Developer Services → Verbatim
Product: mozilla.org → Webtools
QA Contact: shyam
Summary: Network error when committing to VCS → Out of date file causes issues with svn commits on Verbatim
shyam, see first comment : "Connection to svn.mozilla.org closed by remote host. svn: Commit failed (details follow): svn: Network connection closed unexpectedly" Besnik's file today is out of date because new strings were added last night, but myself, Besnik and Inma got a network error message yesterday, not an out of date file one.
(In reply to Pascal Chevrel:pascalc from comment #15) > shyam, see first comment : > "Connection to svn.mozilla.org closed by remote host. svn: Commit failed > (details follow): svn: Network connection closed unexpectedly" > > Besnik's file today is out of date because new strings were added last > night, but myself, Besnik and Inma got a network error message yesterday, > not an out of date file one. Fair enough. I'd like you to clear the out of date error first and I'll look into the network thing, if it happens again.
Besnik, you should probably click on the button "update from VCS" before trying to commit again from Verbatim.
(In reply to Pascal Chevrel:pascalc from comment #17) > Besnik, you should probably click on the button "update from VCS" before > trying to commit again from Verbatim. So I did: Updated file firefoxflicks/sq/LC_MESSAGES/messages.po from version control working copy: 358 of 360 messages translated (0 fuzzy). remote copy: 358 of 360 messages translated (0 fuzzy). merged copy: 358 of 360 messages translated (0 fuzzy).
...and everybody lived happy and satisfied ever since... Committed file: <em>/data/www/localize.mozilla.org/verbatim/pootle_env/Pootle/po/firefoxflicks/sq/LC_MESSAGES/messages.po</em>
Now I got a "service unavailable" message from Verbatim and committing to the french repo gives an error (locked repo, we need somebody do run a svn-cleanup there=) Failed to commit file: [SVN] Error running SVN command '['svn', '-q', '--non-interactive', 'commit', '-m', u'Commit from Mozilla Verbatim by user pascal.chevrel@free.fr.: 362 of 362 messages translated (0 fuzzy).', '--with-revprop', u'translate:author=pascal.chevrel@free.fr <pascal.chevrel@free.fr>', u'/data/www/localize.mozilla.org/verbatim/pootle_env/Pootle/po/firefoxflicks/fr/LC_MESSAGES/messages.po']': svn: Working copy '/data/www/localize.mozilla.org/verbatim/pootle_env/Pootle/po/firefoxflicks/fr/LC_MESSAGES' locked svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details)
Summary: Out of date file causes issues with svn commits on Verbatim → commit issues on from Verbatim
Summary: commit issues on from Verbatim → commit issues on svn repo from Verbatim
marking as critical as we need that to work so as to commit all the translations ready for Firefox Flicks to the repo and be abme to launch today.
Blocks: 816746
Severity: normal → critical
Depends on: 833883
Assignee: nobody → server-ops
Severity: critical → normal
Component: Verbatim → Server Operations
Product: Webtools → mozilla.org
QA Contact: shyam
This should be fixed now. See bug 833883 for details.
Assignee: server-ops → dgherman
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.