jean-marie burel

Prior to change ``` tools/xmlvalid ~/Desktop/course_lif/output.ome.tiff Parsing schema path http://www.openmicroscopy.org/Schemas/OME/2016-06/ome.xsd Validating /Users/jmarie/Desktop/course_lif/output.ome.tiff Error parsing schema at http://www.openmicroscopy.org/Schemas/OME/2016-06/ome.xsd org.xml.sax.SAXParseException: s4s-elt-character: Non-whitespace characters are not allowed in schema elements other than 'xs:appinfo'...

I had it initially in https://github.com/ome/ome-resources-monitor but this was the only not based on GitHub action that's why I put it in this repository as an extra output.

@melissalinkert instead of hard-coding a value I have opted to compare start/end value. I will change the time when the job runs

https://merge-ci.openmicroscopy.org/jenkins/job/OMERO-test-integration/297 3 failures this morning

Adding a test resources similar to the one in omero-common could be an option but that means that we will have 2 packages providing test files. In terms of maintenance...

This is in the same spirit that what has been done in https://github.com/ome/openmicroscopy/blob/develop/components/tools/OmeroJava/test/integration/ModelMockFactory.java Another could be to handle an "xml" key in the name of the fake file i.e. ``testimg&xml=BlobOfOMEXML.fake``...

Thanks for the information we will update the autogenerated documentation accordingly Recorded at https://github.com/ome/omeroweb-install/issues/100

``builtins`` still present in ``clitest/test_tag.py`` Also in ``OmeroFS/test/drivers.py``

The changes look good One thing I noticed is that we do not test various Python version. This is only tested with Python 3.10 We will need to modify the...

It is when you build the gateway. Anyway I am doing some tests with various Python versions. I will push a commit