** Description changed: + [Impact] + + * Telemetry was relaying on time.time() to report duration of + installation and various step. This system clock though can be reset by + the installer, loading to negative time report. + + [Test Case] + + * Start an 18.04 live session and install ubiquity + * Start ubiquity + * Change the timezone to one "in the past" compared to your location + * Complete the installation and close ubiquity without rebooting the session + * Check that no values of the "Stages" hashmap in /target/var/log/installer/telemetry is negative + + [Regression Potential] + + * We are using /proc/upstime as a reference and it's not affected by the system clock. + * The worst case is that we still report negative telemetry data for time. + + ----- + time.time() is sensitive to system clock change after NTP sync. We should rather use /proc/uptime as a reference and test it's not affected by system clock (it shouldn't).
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771966 Title: Time measurement in telemetry can be negative To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1771966/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
