[14:56] <brendand> dobey, i finally got round to checking about that account creation. after the account creation has been attempted on the phone, my attempt to login to the same account on login.staging.ubuntu.com fails
[14:56] <brendand> dobey, so either the account creation failed or it was created in the wrong place
[14:57] <brendand> dobey, ok it seems it was actually created on production
[15:01] <dobey> ok, so the staging env wasn't created then
[15:02] <dobey> there may be some restrictions about team membership on the staging server too
[15:11] <brendand> dobey, setup-staging.sh has definitely been run, as i see the staging apps
[15:15] <dobey> then maybe you had something already running in the online-accounts system, and it didn't get restarted afterward
[15:18] <brendand> dobey, good point i'll check if that was started before i ran setup-staging.sh
[15:23] <brendand> dobey, setup-staging.sh itself doesn't start online-accounts-service right? it just sets the environment appropriately to make it use staging?
[15:23] <brendand> dobey, if so it shouldn't be a problem as we restart online-accounts-service with testability enabled after running it
[15:23] <dobey> right. it restarts scope-registry and pay-service
[15:24] <dobey> brendand: oh, are you running online-accounts-service with an infinite timeout, with testsability, for testing?
[15:24] <brendand> dobey, exactly
[15:25] <dobey> brendand: how is it run with testability? is that an env var?
[15:25] <brendand> dobey, initctl set-env QT_LOAD_TESTABILITY=1
[15:26] <brendand> dobey, so would setup-staging set the right variables to make online-accounts-service use staging or would we have to do more than that?
[15:27] <dobey> yes, it does set the right variables. but if online-accounts-service is already running, and has an infinite timeout, it won't get the env
[15:32] <brendand> dobey, it is running when i run setup-staging.sh, but then i kill it and restart it with testability
[15:32] <brendand> dobey, maybe to be safe i should kill it before running setup-staging
[15:48] <brendand> dobey, any way i can check online-accounts-service is running against staging? i don't see any upstart log for it at least
[15:49] <dobey> brendand: you'd have to poke at the env for it in /proc and verify that the env variables are set, i guess
[15:50] <dobey> brendand: do you actually need to keep onine-acocunts-service running all the time for some reason other than the qt testability?
[15:54] <brendand> dobey, i'm not sure we do really
[15:54] <brendand> dobey, what's the normal timeout?
[15:55] <dobey> i don't know, but it's a dbus-activated thing afaik
[15:56] <brendand> dobey, what environment variable am i looking out for here?
[15:56] <brendand> dobey, i don't see anything with STAGING in it anyway
[15:57] <dobey> U1_AUTH_BASE_URL
[15:57] <dobey> iirc
[16:00] <dobey> brendand: use this to set up the testability env: http://pastebin.ubuntu.com/12555779/
[16:00] <dobey> brendand: then, any programs launched, or any services activated by dbus after, will have the env var
[16:00] <dobey> and you don't need to manually run the online-accounts-service with an infinite timeout
[16:01] <dobey> you can expand that to have other variables set in the same manner, if they are needed