[hooks/syncschema] do not crash on double removal of a constraint
Some complicated migrations may entail a double constraint removal.
It is not yet known whether this is a genuine cw bug or the result
of a complicated migration story, but we should nevertheless
not crash.
Rather, emit a CRITICAL warning and proceed.
Closes #3595309.
from cubicweb.devtools.qunit import QUnitTestCase, unittest_main
from os import path as osp
class JScript(QUnitTestCase):
all_js_tests = (
("jstests/test_utils.js", (
"../../web/data/cubicweb.js",
"../../web/data/cubicweb.compat.js",
"../../web/data/cubicweb.python.js",
"jstests/utils.js",
),
),
("jstests/test_htmlhelpers.js", (
"../../web/data/cubicweb.js",
"../../web/data/cubicweb.compat.js",
"../../web/data/cubicweb.python.js",
"../../web/data/cubicweb.htmlhelpers.js",
),
),
("jstests/test_ajax.js", (
"../../web/data/cubicweb.python.js",
"../../web/data/cubicweb.js",
"../../web/data/cubicweb.compat.js",
"../../web/data/cubicweb.htmlhelpers.js",
"../../web/data/cubicweb.ajax.js",
), (
"jstests/ajax_url0.html",
"jstests/ajax_url1.html",
"jstests/ajax_url2.html",
"jstests/ajaxresult.json",
),
),
)
if __name__ == '__main__':
unittest_main()