Additional information inline. On Wed, Mar 16, 2016 at 9:28 AM, Alberto Pastor <[email protected]> wrote:
> Hi Chris! > > I’ll try to reply all your questions. Somebody correct me if I’m wrong: > > - *Is there anywhere one can see what tests are failing* -> > https://treeherder.mozilla.org/#/jobs?repo=gaia > The link posted above is for what is considered 'gaia-try'. Gaia master can be seen here -- https://treeherder.mozilla.org/#/jobs?repo=gaia-master https://treeherder.mozilla.org/#/jobs?repo=pine&filter-tier=1&filter-tier=2&filter-tier=3 is also a good place to see the overall status of the Transition Project's code + tests. > - *Are there any guidelines on what's changed and what's necessary to get > things working again?* > I don’t have a good answer for that. I think the main focus for the > transition is removing Packaged apps support, and some of the b2g specific > API’s, but that didn’t happen yet, so I’m not why the tests are currently > failing :/ > Neither do I honestly. But, what I can tell you is that the only build that will work is coming from the Pine branch and that the Kanikani branch will have good examples on how to update your application as we'll be updating System and Settings. > - *Where and what is kanikani?* -> Kanikani is the transition branch, > that will be merged back to master in June. > https://github.com/mozilla-b2g/gaia/tree/kanikani > > I would like to add a couple more questions in order to make it easier for > module owners to fix the tests. Aus, probably you are the right person to > answer these ones :) > > - *Are somehow the integration tests running differently in treeherder > than locally? In that case, what the differences are?* > There are minor differences but on the whole, if you are running the tests on Linux and in Xvfb you are running them the same way. > - *How can we replicate those errors locally?* > These errors should happen on the same platform with the same tests + build. Nothing else should be required to observe these failures. Unless the failures are related to the infrastructure, or environment settings specific to CI. We do use a few special environment variables to determine which gaia revision we will use for example, but those are only used by the tooling (e.g. mozharness and sub-modules). > > Thanks in advance! > > Alberto. > > > On 16 Mar 2016, at 16:45, Christopher Lord <[email protected]> wrote: > > Is there anywhere one can see what tests are failing, and are there any > guidelines on what's changed and what's necessary to get things working > again? Where and what is kanikani...? > > Some more details here would be really great, there are a lot of questions > that anyone that's reading this for the first time (like myself) are going > to need answering, would be good to have that done once, in one place. > > --Chris > > On 15 March 2016 at 23:15, Aus Lacroix <[email protected]> wrote: > >> tl;dr -- No action necessary unless you want your application to continue >> to work. >> >> Hi All, >> >> The Sunset project will require App owners that still want their >> applications to get built and tested during upon check-ins to update and >> fix their tests so that they are functional. >> >> Any application that doesn't have functional tests will not get merged >> back from kanikani to mainline. >> >> The ETA for this is May 2016. >> >> If no action is taken to fix the tests, the application will disappear >> from master when kanikani is merged back. >> >> word, >> --aus >> >> _______________________________________________ >> dev-fxos mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-fxos >> >> > _______________________________________________ > dev-fxos mailing list > [email protected] > https://lists.mozilla.org/listinfo/dev-fxos > > >
_______________________________________________ dev-fxos mailing list [email protected] https://lists.mozilla.org/listinfo/dev-fxos
