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

changes to mozilla/ipc do not show up on tinderbox [needs to be added to SeamonkeyAll ???]

RESOLVED WORKSFORME

Status

mozilla.org Graveyard
Server Operations
RESOLVED WORKSFORME
14 years ago
3 years ago

People

(Reporter: Darin Fisher, Assigned: Dawn Endico)

Tracking

Details

(Reporter)

Description

14 years ago
changes to mozilla/ipc do not show up on tinderbox [needs to be added to
SeamonkeyAll ???]

btw, mozilla/ipc just recently landed on the trunk.  it used to live on a
branch, so now that it is on the trunk, i think it makes sense for it to be
added to SeamonkeyAll (or whatever).  thx!
define what you mean by "changes don't show up"...  show up where?

Do they show up in Bonsai when you query on recent changes?  Tinderbox just uses
the checkin logs from Bonsai.

If there's a specific tinderbox testing this stuff then you probably need to
talk to whoever's running that tinderbox to configure it for a different tree page.
(Reporter)

Comment 2

14 years ago
dave: i'm sorry for not being clear.  i was referring to the list of checkins
shown on the main tinderbox page for mozilla:

http://tinderbox.mozilla.org/showbuilds.cgi?tree=SeaMonkey

i made a checkin today under mozilla/ipc/ipcd, and it did not show up on that
page.  however, when i go and look at bonsai, i see my changes listed under the
following modules:

  All Files in the Repository
  MozillaTinderboxAll
  SeamonkeyAll

here is the query run by that tinderbox page when i click on a timestamp over on
the left hand side of the page:

http://tinderbox.mozilla.org/bonsai/cvsquery.cgi?module=MozillaTinderboxAll&date=explicit&mindate=1068414660

it is strange that the tinderbox query would not show changes to
mozilla/ipc/ipcd because when i query changes to MozillaTinderboxAll directly
from bonsai.mozilla.org, i see the changes.
Darin: is this still true?

Gerv
(Reporter)

Comment 4

13 years ago
well, in fact.. no.  it seems to be fixed now.  or at least it worksforme now :-)
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → WORKSFORME
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.