If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

FBTestFirebug.js is out of sync

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
--
blocker
RESOLVED FIXED
8 years ago
3 years ago

People

(Reporter: Honza, Assigned: aravind)

Tracking

Details

(Whiteboard: [firebug-p1])

(Reporter)

Description

8 years ago
Following file is still out of sync at getfirebug.com

Please compare following files:

/projects/getfirebug.com/tags/production/tests/content/FBTestFirebug.js
This file is up to date in my local rep (synced with SVN)

This online file is out of date.
http://getfirebug.com/tests/content/FBTestFirebug.js

Honza
(Reporter)

Updated

8 years ago
Whiteboard: [firebug-p1]
any idea what's going on here?

Jan, when did you do the initial commit? How long has it been out of sync?
Severity: normal → major
OS: Windows Vista → All
Hardware: x86 → All
(Reporter)

Comment 2

8 years ago
The last sync with fbg SVN is at R3971 (August 14).

I have committed changes into at R4065 (August 22) and since this revision it was not synced.

Honza

Comment 3

8 years ago
This bug prevents Firebug releases. I tried to contact arvind yesterday without success.
our automated test system is going to be coming online today or tomorrow. Without this, it's no good. raising priority to Critical.
Severity: major → blocker

Updated

8 years ago
Assignee: nobody → server-ops
Component: getfirebug.com → Server Operations
Product: Websites → mozilla.org
QA Contact: getfirebug-com → mrz
Version: unspecified → other
(Assignee)

Comment 5

8 years ago
looking into it.
Assignee: server-ops → aravind
(Assignee)

Comment 6

8 years ago
This is what we have on the server side.

[root@mradm02 content]# svn info FBTestFirebug.js 
Path: FBTestFirebug.js
Name: FBTestFirebug.js
URL: http://fbug.googlecode.com/svn/tests/content/FBTestFirebug.js
Repository Root: http://fbug.googlecode.com/svn
Repository UUID: e969d3be-0e28-0410-a27f-dd5c76401a8b
Revision: 4143
Node Kind: file
Schedule: normal
Last Changed Author: johnjbarton.com
Last Changed Rev: 4100
Last Changed Date: 2009-08-25 18:15:11 -0700 (Tue, 25 Aug 2009)
Text Last Updated: 2009-08-25 18:22:03 -0700 (Tue, 25 Aug 2009)
Checksum: 11279995cc366cf6aa073681f89301a2


I tried deleting the file and an svn up pulled the exact same rev back.

If it helps...

[root@mradm02 content]# md5sum FBTestFirebug.js 
11279995cc366cf6aa073681f89301a2  FBTestFirebug.js
[root@mradm02 content]# 

Is this whats in svn?

Comment 7

8 years ago
aravind, please try 
http://getfirebug.com/tests/content/testlists/firebug1.5.html

This is in svn at R4110, but the server does not see it.

Comment 8

8 years ago
Also
http://getfirebug.com/tests/content/FBTestFirebug.js
is not current, it is not what we have in svn.
(Assignee)

Comment 9

8 years ago
The website docroot was moved to a different location, but the cron job that updates it wasn't.  Fixed the cron job location to reflect the server layout.  Web site should be fixed in about 20 minutes.
Status: NEW → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → FIXED

Comment 10

8 years ago
Thanks, we made progress. But we get:

POST https://getfirebug.com/tests/content/console/1693/issue1693.php
	
500 Internal Server Error
	
Any chance the docRoot change is related?  We have trivial PHP scripts to test our net panel.
(Assignee)

Comment 11

8 years ago
[Fri Aug 28 16:31:14 2009] [error] [client 10.2.81.4] PHP Parse error:  syntax error, unexpected T_INC, expecting ')' in /data/www/getfirebug.com/tests/content/console/1693/issue1693.php on line 3, referer: https://getfirebug.com/tests/content/console/1693/issue1693.html
(Reporter)

Comment 12

8 years ago
Thanks for the info!
I have fixed the problem with issue1693.php.

The only problem is that I don't see:
http://getfirebug.com/releases/export/1.5/netExport-0.7a9.xpi

I have committed this file yesterday R50583 (September 1st, 17:47)

Honza
(Reporter)

Comment 13

8 years ago
Not sure if this is related to this bug, but I am seeing weird jumbled header "ntCoent-Length" for responses coming from getfirebug.com 

Try e.g: https://getfirebug.com/tests/content/net/2221/issue2221.html

Honza
(Reporter)

Comment 14

8 years ago
I am still seeing problems with syncing getfirebug.com

A new version of Firebug was committed yesterday and it is still not online.
http://getfirebug.com/releases/firebug/1.5X/firebug-1.5X.0a23.xpi

Here is a feedback from Firebug news group:
http://groups.google.com/group/firebug/browse_thread/thread/da530dfb07e18793
http://groups.google.com/group/firebug/browse_thread/thread/64b80c7910acb1c

Also the file mentioned in comment #12 is not online.

Should I reopen this bug or file a new one?

Honza
Jan,

I've pushed this out manually for now.

While the automated svn up works fine, there seems to be no automated git push for the generic cluster. I'm not sure if that's intentional or got left out by mistake.

I'll file another bug to track this internally within IT and CC you folks.
(Reporter)

Comment 16

8 years ago
> I've pushed this out manually for now.
Yes, I can verify, both files are now visible.

> I'll file another bug to track this internally within IT and CC you folks.
Thanks!

Honza
(In reply to comment #15)
> Jan,
> 
> I've pushed this out manually for now.
> 
> While the automated svn up works fine, there seems to be no automated git push
> for the generic cluster. I'm not sure if that's intentional or got left out by
> mistake.

I don't know what this means so I'm guessing this was left out by mistake.

Websites are now hosted in git but we're using SVN to manage the contents? Can I please have *another* vcs in this picture? ;)

> I'll file another bug to track this internally within IT and CC you folks.

thanks.
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.