gjs is one of the better tested parts of GNOME. We run its build tests as part of the build and we use autopkgtest to run its installed tests (autopkgtests pass on all architectures except s390x). I talked briefly with the gjs maintainer today and he said that he estimates the test coverage at about 65%. He also tries to add tests when regressions are identified and fixed. (Although in this case, he had difficulty reproducing the gnome-shell crashes and therefore wasn't able to add much tests for them.)
But let me speak more about GNOME SRUs in general. GNOME SRUs are regularly accepted without needing to have automatic testing. This is good because much of GNOME does not have test coverage. Where tests exist, we do try to run them. Ubuntu runs more GNOME tests now than it did a year ago because of switching from cdbs to dh (with dh_auto_test) and as checked during the recent set of MIRs. There used to be a standing release exception from the Tech Board (TB) for GNOME microreleases but this explicit exception was dropped when the TB simplified the SRU policy in September 2015. https://wiki.ubuntu.com/StableReleaseUpdates?action=diff&rev1=231&rev2=232 https://wiki.ubuntu.com/StableReleaseUpdates/MicroReleaseExceptions?action=diff&rev1=59&rev2=60 I don't think it's good for our users to block reasonable microreleases for GNOME because tests do not exist. Is there a problem with how GNOME SRUs have been handled recently? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1698553 Title: Update gjs to 1.48.5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1698553/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
