| Age | Commit message (Collapse) | Author |
|
bzr revid: vmt@openerp.com-20130327153843-u62ftp74qv01u1ww
|
|
When --test-enable is used, it is expected that test output is visible,
thus using log-level INFO is natural.
On the down side you lose the nice blue hint that tests did actually
run when --log-level test was given.
bzr revid: vmt@openerp.com-20130326155844-83e2tcqokvblr0ln
|
|
sys.moduls at their shortname.
bzr revid: vmt@openerp.com-20130218164839-2qludhn3znpdftq5
|
|
files.
bzr revid: vmt@openerp.com-20130212152328-flpn1tbz75lhi2m2
|
|
out-of-date registry.
bzr revid: vmt@openerp.com-20130212085311-o53wv7yful39kktd
|
|
bzr revid: chs@openerp.com-20121210132406-9ro3amw6s6pzeez4
|
|
bzr revid: al@openerp.com-20121209024618-cae0ux1vmo38ccwr
|
|
bzr revid: chs@openerp.com-20121201003326-j6n5r8juz16752j5
bzr revid: chs@openerp.com-20121204165557-u1oxocye3la4r6gf
bzr revid: chs@openerp.com-20121205143722-olswf8gsg8mhref3
|
|
execution.
bzr revid: vmt@openerp.com-20121203104228-8a5on97pn9r1klls
|
|
bzr revid: chs@openerp.com-20121114174352-a0xbech8o4dav16b
|
|
also, cleanup module file (remove extra imports, extra default key in manifest)
bzr revid: xmo@openerp.com-20121024105454-nqw9taxladjofz2v
|
|
bzr revid: chs@openerp.com-20121010115500-xz9oqr2g8vzr79jq
|
|
bzr revid: fp@tinyerp.com-20120926121536-9836j42ulu8wcir8
|
|
bzr revid: chs@openerp.com-20120905132230-0r6pv4nlegt3x0mb
|
|
Florent Xicluna
bzr revid: odo@openerp.com-20120904074105-ql796z5c8b6o4cyf
|
|
using cProfile).
bzr revid: vmt@openerp.com-20120903145828-8yflgc0lfqn6woai
|
|
Florent Xicluna
lp bug: https://launchpad.net/bugs/928376 fixed
lp bug: https://launchpad.net/bugs/928507 fixed
bzr revid: odo@openerp.com-20120903130536-5sqwp9tnhk1ntee3
|
|
bzr revid: chs@openerp.com-20120824142323-m503lc6tfj4vntop
|
|
bzr revid: jam@tinyerp.com-20120717085028-2jkbf9ymrftkui45
|
|
bzr revid: vmt@openerp.com-20120605095210-0t5bmlyxrtnoqvr0
|
|
ir.module object
bzr revid: mma@tinyerp.com-20120518052939-51ps201qaq51g2bp
|
|
bzr revid: vmt@openerp.com-20120302112834-n1zyqf1g4v61ivje
|
|
- pass around the assertion_report to the YAML importer
- removed TestReport, which was identical to assertion_report
- assertion_report is simpler (no more severity level)
- use the report to log a greppable sentence when some test failed.
Previously the runbot had to grep for a Traceback which was an
unreliable technique (e.g. an exception can be purposefuly
generated as part of a test and the associated traceback
visible in the logs). Now it can grep
"At least one test failed when loading the modules".
bzr revid: vmt@openerp.com-20120302110227-nqrl7i46ju28ntdr
|
|
- moved a few YAML tests to unittest2 for demonstration purpose
- changed --test-disable to --test-enable (and swapped its meaning)
bzr revid: vmt@openerp.com-20120301134608-szuktuj8imdhmn0r
|
|
removed unexisting column name, filter out more test outputs
bzr revid: vmt@openerp.com-20120301121611-1gieqehm9wqog2fx
|
|
bzr revid: vmt@openerp.com-20120210095946-dxs0e0cd4ffkccy9
|
|
This should be reverted for 6.2 when the openerp.addons namespace will
be the only option.
lp bug: https://launchpad.net/bugs/929466 fixed
bzr revid: vmt@openerp.com-20120209163016-1wiw1xsrppumjvfl
|
|
lp bug: https://launchpad.net/bugs/929466 fixed
bzr revid: vmt@openerp.com-20120209152732-24ud1f70krliv2k5
|
|
bzr revid: vmt@openerp.com-20120209141444-12261k6zd2ovnltd
|
|
resources
The previous behavior gave the precedence to zipped
modules, without any apparent reason, and this is
sub-optimal for several reasons:
1. The default is to have regular modules, not
zipped modules, so looking first for a regular
module is more efficient.
2. Keeping a zipped module next to a regular
module with the same name is not a documented
or supported feature.
3. Even if you were relying on this behavior
having the extracted module take precedence
is more practical: you could simply extract
the zipped module to test a quick fix.
We have another issue related to this feature
because the code looking for zipped modules
escapes the addons paths chroot and goes
up to the filesystem root looking for a zip
module at each step. This is described in
bug 928376 and a fix for it should follow.
lp bug: https://launchpad.net/bugs/928376 fixed
bzr revid: odo@openerp.com-20120208173932-pwhz53vxxdzbo8ja
|
|
Similar changes for the addons will be done after 6.1.
bzr revid: vmt@openerp.com-20120208105913-habqxas406osaz9z
|
|
4003 revid:xmo@openerp.com-20120202154532-tq9x07ujf0bn9mcp
bzr revid: al@openerp.com-20120208005252-ke2v5mtkxpmyml6d
|
|
bzr revid: vmt@openerp.com-20120206203151-3snkz7usngwtv1xt
|
|
case of zipped module) and StringIO are not contextmanagers.
So rollback the context management thingie
bzr revid: xmo@openerp.com-20120202154532-tq9x07ujf0bn9mcp
|
|
bzr revid: al@openerp.com-20120131211744-whzzo0dh6w1kptng
|
|
use the openerp.addons namespace), and correctly set the submodules in
sys.modules (instead of only the top-level package).
bzr revid: vmt@openerp.com-20120201152710-s7sxlgibwd3lwr5l
|
|
bzr revid: al@openerp.com-20120130210429-zw7aziwhkhi0yhqv
|
|
display a warning).
bzr revid: vmt@openerp.com-20120130113116-msjaej7jxp96tbvh
|
|
bzr revid: vmt@openerp.com-20120130095238-x2by4y11joeytipr
|
|
`auto_installable`. An auto-installable module is a module automatically
installed by the OpenERP server as soon as its dependencies are
satisfied, without explicit user action.
bzr revid: vmt@openerp.com-20120126164049-smrcvrojy0b1z6f8
|
|
bzr revid: vmt@openerp.com-20120124124252-91g3ysf33zsq4nhd
|
|
bzr revid: vmt@openerp.com-20120124102024-ziajbxfxjs1kyurv
|
|
name is now inaccurate).
bzr revid: vmt@openerp.com-20120110092730-rqewzuo1wa5wy2q5
|
|
instead of openerp-server).
bzr revid: vmt@openerp.com-20120109125243-qhtr070dvtc3akb5
|
|
openerp.modules as the namespace of the OpenERP addons.
bzr revid: vmt@openerp.com-20120109124120-06gguu3lzxv49i3j
|
|
(openerp.modules will be changed in openerp.addons in the next commit).
bzr revid: vmt@openerp.com-20120109123123-jt3canjbg0ozs05j
|
|
`import openerp.modules.<module_name>`.
bzr revid: vmt@openerp.com-20120109101647-4hvy3n6eifzeozzq
|
|
bzr revid: vmt@openerp.com-20120109083957-06ahuojw1d4m954g
|
|
bzr revid: vmt@openerp.com-20120109081206-p10yack8lhip11gt
|
|
individual module manifests
Having the sequence number living outside the module itself
causes various problems at initialization when modules are
missing (e.g. if creating a database with `base` only).
It is also cleaner to have the module sequence in the
module manifest, like other module metadata.
A corresponding commit in the addons project adds the
`sequence` field in the manifest of all modules who
have a non-default sequence (the main apps).
bzr revid: odo@openerp.com-20120107041745-tik3iu1b2qs4ym85
|