[Systers-dev] Testing Request for Bug 583379

[kanika vats]

Hi Robin,

Yes I am sure that Change_email_test is a Dlist .I am not able to understand
how 506024 is running instance of the old code(as Kathy said) and other old
lists (like Change_email_test) are running instance of new code.Should not
all the list access same code?The error listed in error log occurs whenever
a particular email id is nor present in database.I will look into more
detail by today and let you know what I think the problem might be.

Thanks

On Mon, Jun 7, 2010 at 4:02 PM, Kathy Richardson <kjr at casaveracruz.com>wrote:

>
> Robin,
>
> You are accessing a running instance of the old code.
> 506024 was the bug we tested in Feb.
>
> I'm still not familiar with how all the pieces go together to fully
> understand how a new version is installed and the old instances are still
> running happily running.
>
> Kathy
>
>
> Sent from my iPad
>
> On Jun 6, 2010, at 7:48 AM, Robin Jeffries <robin at jeffries.org> wrote:
>
> I used 506024-dlist  Are you sure change_email_test is a dlist?
>
> Here is the error output
> admin(28067): Traceback (most recent call last):
> admin(28067):   File "/usr/local/mailman/scripts/driver", line 101, in
> run_main
> admin(28067):     main()
> admin(28067):   File "/usr/local/mailman/Mailman/Cgi/options.py", line 821,
> in main
> admin(28067):     options_page(mlist, doc, user, cpuser, userlang)
> admin(28067):   File "/usr/local/mailman/Mailman/Cgi/options.py", line 865,
> in options_page
> admin(28067):     subscriber_id =
> subscriber.getSubscriber_id_raw_or_die(user)
> admin(28067):   File "/usr/local/mailman/Mailman/DlistUtils.py", line 98,
> in
> getSubscriber_id_raw_or_die
> admin(28067):     raise ErrorsDlist.InternalError
>
>
> I also found this error output, which must relate to something you did and
> might be a clue (I think the time given is local time, which is UTC-7):
>
> Jun 06 03:40:18 2010 admin(3492):
> @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
> admin(3492): Traceback (most recent call last):
> admin(3492):   File "/usr/local/mailman/scripts/driver", line 101, in
> run_main
> admin(3492):     main()
> admin(3492):   File "/usr/local/mailman/Mailman/Cgi/admin.py", line 174, in
> main
> admin(3492):     change_options(mlist, category, subcat, cgidata, doc)
> admin(3492):   File "/usr/local/mailman/Mailman/Cgi/admin.py", line 1339,
> in
> change_options
> admin(3492):     whence='admin mass sub')
> admin(3492):   File "/usr/local/mailman/Mailman/MailList.py", line 979, in
> ApprovedAddMember
> admin(3492):     password=password, language=lang)
> admin(3492):   File "/usr/local/mailman/Mailman/DlistMemberships.py", line
> 128, in addNewMember
> admin(3492):     subscriber.subscribeToList(member)
> admin(3492):   File "/usr/local/mailman/Mailman/DlistUtils.py", line 52, in
> inner
> admin(3492):     self.store = Store(self.database)
> admin(3492):   File "/usr/lib/python2.5/site-packages/storm/store.py", line
> 68, in __init__
> admin(3492):     self._connection = database.connect()
> admin(3492):   File "/usr/lib/python2.5/site-packages/storm/database.py",
> line 353, in connect
> admin(3492):     return self.connection_factory(self)
> admin(3492):   File "/usr/lib/python2.5/site-packages/storm/database.py",
> line 168, in __init__
> admin(3492):     self._raw_connection = self._database.raw_connect()
> admin(3492):   File
> "/usr/lib/python2.5/site-packages/storm/databases/postgres.py", line 312,
> in
> raw_connect
> admin(3492):     raw_connection = psycopg2.connect(self._dsn)
> admin(3492): OperationalError: FATAL:  database "kanika_test_final" does
> not
> exist
>
>
>
> Robin
>
> On Sun, Jun 6, 2010 at 6:05 AM, kanika vats <kanika.krikan at gmail.com>
> wrote:
>
> Hi Robin,
>
> I tried to do the same on abiwt.org using Change_email_test list(which is
> an
> old one) and it was working fine.I also tried to do the same on old dlist
> at
> my local mailman setup and there also no problems are coming.Can you tell
> me
> which old dlist is giving the error?I checked out the error log but its not
> giving me complete information.
>
> Thanks
>
>
> On Sat, Jun 5, 2010 at 9:15 PM, Robin Jeffries <robin at jeffries.org> wrote:
>
> Oops, looks like the fix isn't a fix.
>
> I just tried to create a user with a mixed case address on abiwt.org(using
> one of the old dlists) and
>  - creating it worked fine (I didn't have to go munge the database or
> anything)
>  - when I tried to access the options page for this subscriber, I get
> the
> same bug.
>
> I did a cursory check and it looks like we are running on the new files
> (at
> least I looked at DlistUtils.py, which is where most of the changes are,
> and
> that looks correct to me).  *Kanika Vats*, can you take a look at
> abiwt.org and see if you can tell what's causing the problem?  You
> should
> be able to create a user with mixed case just by subscribing
> Kanika.Krikan at gmail.com (or one of your other email addresses, case
> adjusted) to any of the dlists on that machine.
>
> I'm pretty sure that we have the right fix, at least conceptually, but
> there must be something we are overlooking in the implementation.
>
> Robin
>
> On Fri, Jun 4, 2010 at 5:02 PM, Robin Jeffries <robin at jeffries.org>
> wrote:
>
> OH, I just looked more carefully.  You have the admin password there, so
> anyone can do admin tasks (and should learn how to use the admin
> interface).
>
> We don't need a non-dlist for this set of tests, since the problem is in
> the dlist database, and that doesn't even come into play for non-dlists.
> I
> removed all the tests that refered to non-dlists.
>
> Robin
>
>
> On Fri, Jun 4, 2010 at 4:39 PM, Robin Jeffries <robin at jeffries.org
> wrote:
>
> I made the instructions a bit more clear (in terms of what you see --
> the
> tester will see an error message about the crash if it happens).
>
> There are several tests that require admin access; you should publish
> the
> admin password for this list (and either delete the list or change the
> admin
> password after the testing is done, so it isn't a security hole) on the
> wiki. Make sure Kathyg knows what the admin password is, so that
> someone
> long term remembers it.
>
> Let me take SBT1 and SBT2, as they need the mixed case user and then I
> can test them in about 2 minutes after I create the user.
>
> Robin
>
> On Thu, Jun 3, 2010 at 7:36 AM, Jason Cox <jasonwilburcox at gmail.com
> wrote:
>
> Robin,
>
> On Thu, Jun 3, 2010 at 12:35 AM, Robin Jeffries <robin at jeffries.org
> wrote:
>
> One caveat.  The code changes haven't been uploaded to the
> development
> server yet.  Kanika Vats is doing that.  Don't start testing till she
> says
> that they are working (and then Jason will need to create testing
> lists
> using the new code, since part of what we are testing is whether the
> changed
> code messes up newly created lists)
>
>
> I created two tests specific to this bug. They are SBT1 and SBT2.
> Would
> you mind taking a look at them and see if they are descriptive enough
> and
> test the system the right way.
>
> Thanks,
>
> Jason
>
>
>
> But the enthusiasm is great.
>
> Robin
>
> On Wed, Jun 2, 2010 at 9:24 PM, Jaideep Khandelwal <
> jdk2588 at gmail.com>wrote:
>
> On Thu, Jun 3, 2010 at 9:14 AM, Jason Cox <jasonwilburcox at gmail.com
>
> wrote:
>
> Hey all,
>
> It is time for testing and luckily we already have many people
> interested!
> Here is a link to the wiki for the test:
>
>
> http://systers.org/systers-soc/doku.php/checklist_specific_for_bug_583379
> .
> When performing a test, read the description and expected
> behavior,
> then
> fill out the info in the table. You will need to join the email
> lists, be
> able to edit systers-dev wikis, and reply to this email below with
> what
> tests you want to do.
>
>
> I would like to do the testing for the following :
>
>  Administrative Interface      Subscribe using Mass Subscription -
> AMM1
>    Unsubscribe using Mass Removal   - AMM2
>
>   Posting Messages - Test on DLIST only       UPM1, UPM2, UPM3
>
>  If there are more test assigned to me , I would be happy doing it
> :)
>
>
>
> Some of the tests require several people working together at the
> same time.
> I am going to pick a couple of times to meet and see what works
> best
> for
> people. We will plan for about 3 hours, which it should take much
> less time
> but possibly more time (not likely). The testers are in many
> different time
> zones, so we may need to work a little bit to find a time that
> works. I am
> going to pick two times, and I would like anyone wanting to help
> with the
> group testing to vote on which time they can attend. If you can
> make
> both,
> please vote for both since some many will only be able to pick
> one,
> and I
> don't want to think a time doesn't work when it actually could.
> Also, if
> you
> can't make either but want to help with testing, please let me
> know.
> I want
> everyone that wants to help involved. Even though we only will
> need
> three
> for the multi-person tests, we can have more involved as a
> learning
> experience.
>
> The times are:
>
> Friday June 4 - 0:00 GMT - 3:00 GMT
>
> Friday June 4 - 12:00 GMT - 15:00 GMT
>
> I would prefer for the second time , as I would be busy writing my
> exam
> during the first phase  :
> Friday June 4 - 12:00 GMT - 15:00 GMT (IST will be June 4 - 17.30 -
> 20.30)
>
> Any suggestions would be great .
>
> Regards
>
> Thanks
> Jaideep
>
>
>
>
> For the tests that require one person, I will list them below.
> Reply
> back
> with which one you want to claim, if you want to claim one. I am
> splitting
> them up into groups:
>
> AMM1, AMM2, UOL2
> UOM1, UOM2, UOM3, UOM4, UOM5
> SBT1 (requires your name in the system to be mixed case)
>
>
> Svaksha and I will be doing the UPM1-11 tests, since she will be
> doing
> research for automated testing. I will do SBT2, since it requires
> the admin
> of the list.
>
> If you have any questsions, please let me know.
>
> Thank You,
>
> Jason
>
>
> To unsubscribe from this conversation, send email to <
> systers-dev+testing7+unsubscribe at systers.org<systers-dev%2Btesting7%2Bunsubscribe at systers.org>
> <systers-dev%2Btesting7%2Bunsubscribe at systers.org<systers-dev%252Btesting7%252Bunsubscribe at systers.org>
> >
> <systers-dev%2Btesting7%2Bunsubscribe at systers.org<systers-dev%252Btesting7%252Bunsubscribe at systers.org>
> <systers-dev%252Btesting7%252Bunsubscribe at systers.org<systers-dev%25252Btesting7%25252Bunsubscribe at systers.org>
> >
>
> <systers-dev%2Btesting7%2Bunsubscribe at systers.org<systers-dev%252Btesting7%252Bunsubscribe at systers.org>
> <systers-dev%252Btesting7%252Bunsubscribe at systers.org<systers-dev%25252Btesting7%25252Bunsubscribe at systers.org>
> >
> <systers-dev%252Btesting7%252Bunsubscribe at systers.org<systers-dev%25252Btesting7%25252Bunsubscribe at systers.org>
> <systers-dev%25252Btesting7%25252Bunsubscribe at systers.org<systers-dev%2525252Btesting7%2525252Bunsubscribe at systers.org>
> >
>
>
>
> or visit <
>
>
> http://systers.org/mailman/options/systers-dev?override=121&preference=0
>
> To contribute to this conversation, use your mailer's reply-all or
> reply-group command or send your message to
> systers-dev+testing7 at systers.org <systers-dev%2Btesting7 at systers.org><
> systers-dev%2Btesting7 at systers.org <systers-dev%252Btesting7 at systers.org>>
> <systers-dev%2Btesting7 at systers.org <systers-dev%252Btesting7 at systers.org><
> systers-dev%252Btesting7 at systers.org<systers-dev%25252Btesting7 at systers.org>
> >
> <
> systers-dev%2Btesting7 at systers.org <systers-dev%252Btesting7 at systers.org><
> systers-dev%252Btesting7 at systers.org<systers-dev%25252Btesting7 at systers.org>
> >
> <systers-dev%252Btesting7 at systers.org<systers-dev%25252Btesting7 at systers.org>
> <systers-dev%25252Btesting7 at systers.org<systers-dev%2525252Btesting7 at systers.org>
> >
>
>
> To start a new conversation, send email to <
> systers-dev+new at systers.org <systers-dev%2Bnew at systers.org> <
> systers-dev%2Bnew at systers.org <systers-dev%252Bnew at systers.org>> <
> systers-dev%2Bnew at systers.org <systers-dev%252Bnew at systers.org> <
> systers-dev%252Bnew at systers.org <systers-dev%25252Bnew at systers.org>>><
> systers-dev%2Bnew at systers.org <systers-dev%252Bnew at systers.org> <
> systers-dev%252Bnew at systers.org <systers-dev%25252Bnew at systers.org>> <
> systers-dev%252Bnew at systers.org <systers-dev%25252Bnew at systers.org> <
> systers-dev%25252Bnew at systers.org <systers-dev%2525252Bnew at systers.org>>>>
>
>
> To unsubscribe entirely from systers-dev, send email to <
> systers-dev-request at systers.org> with subject unsubscribe.
>
>
>
> To unsubscribe from this conversation, send email to <
> systers-dev+testing7+unsubscribe at systers.org<systers-dev%2Btesting7%2Bunsubscribe at systers.org>
> <systers-dev%2Btesting7%2Bunsubscribe at systers.org<systers-dev%252Btesting7%252Bunsubscribe at systers.org>
> >
> <systers-dev%2Btesting7%2Bunsubscribe at systers.org<systers-dev%252Btesting7%252Bunsubscribe at systers.org>
> <systers-dev%252Btesting7%252Bunsubscribe at systers.org<systers-dev%25252Btesting7%25252Bunsubscribe at systers.org>
> >
>
> or visit <
>
> http://systers.org/mailman/options/systers-dev?override=121&preference=0
>
> To contribute to this conversation, use your mailer's reply-all or
> reply-group command or send your message to
> systers-dev+testing7 at systers.org <systers-dev%2Btesting7 at systers.org><
> systers-dev%2Btesting7 at systers.org <systers-dev%252Btesting7 at systers.org>
> ><
> systers-dev%2Btesting7 at systers.org <systers-dev%252Btesting7 at systers.org><
> systers-dev%252Btesting7 at systers.org<systers-dev%25252Btesting7 at systers.org>
> >>
> To start a new conversation, send email to <
> systers-dev+new at systers.org <systers-dev%2Bnew at systers.org> <
> systers-dev%2Bnew at systers.org <systers-dev%252Bnew at systers.org>> <
> systers-dev%2Bnew at systers.org <systers-dev%252Bnew at systers.org> <
> systers-dev%252Bnew at systers.org <systers-dev%25252Bnew at systers.org>>>>
> To unsubscribe entirely from systers-dev, send email to <
> systers-dev-request at systers.org> with subject unsubscribe.
>
>
>
>
>
>
>
>
>
> --
> Best Regards
> Kanika Vats
>
>
> To unsubscribe from this conversation, send email to <
> systers-dev+testing7+unsubscribe at systers.org<systers-dev%2Btesting7%2Bunsubscribe at systers.org>
> <systers-dev%2Btesting7%2Bunsubscribe at systers.org<systers-dev%252Btesting7%252Bunsubscribe at systers.org>
> >>
> or visit <
> http://systers.org/mailman/options/systers-dev?override=121&preference=0>
> To contribute to this conversation, use your mailer's reply-all or
> reply-group command or send your message to
> systers-dev+testing7 at systers.org <systers-dev%2Btesting7 at systers.org> <
> systers-dev%2Btesting7 at systers.org <systers-dev%252Btesting7 at systers.org>>
> To start a new conversation, send email to <systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
> <systers-dev%2Bnew at systers.org <systers-dev%252Bnew at systers.org>>
>
> To unsubscribe entirely from systers-dev, send email to <
> systers-dev-request at systers.org> with subject unsubscribe.
>
>
>
> To unsubscribe from this conversation, send email to <
> systers-dev+testing7+unsubscribe at systers.org<systers-dev%2Btesting7%2Bunsubscribe at systers.org>>
> or visit <
> http://systers.org/mailman/options/systers-dev?override=121&preference=0>
> To contribute to this conversation, use your mailer's reply-all or
> reply-group command or send your message to
> systers-dev+testing7 at systers.org <systers-dev%2Btesting7 at systers.org>
> To start a new conversation, send email to <systers-dev+new at systers.org<systers-dev%2Bnew at systers.org>
> >
> To unsubscribe entirely from systers-dev, send email to <
> systers-dev-request at systers.org> with subject unsubscribe.
>
>
>


-- 
Best Regards
Kanika Vats