Activity log for bug #1771966

Date Who What changed Old value New value Message
2018-05-18 07:51:52 Didier Roche-Tolomelli bug added bug
2018-05-18 08:53:40 Jean-Baptiste Lallement tags rls-bb-incoming
2018-05-18 08:53:47 Jean-Baptiste Lallement ubiquity (Ubuntu): importance Undecided High
2018-05-18 08:53:50 Jean-Baptiste Lallement ubiquity (Ubuntu): status New Triaged
2018-05-18 08:53:59 Jean-Baptiste Lallement ubiquity (Ubuntu): milestone ubuntu-18.04.1
2018-05-18 09:20:57 Launchpad Janitor branch linked lp:~didrocks/ubiquity/time-measurement-fix
2018-05-28 14:06:19 Launchpad Janitor merge proposal linked https://code.launchpad.net/~didrocks/ubiquity/+git/ubiquity/+merge/346975
2018-05-28 14:06:41 Didier Roche-Tolomelli nominated for series Ubuntu Bionic
2018-05-28 14:06:41 Didier Roche-Tolomelli bug task added ubiquity (Ubuntu Bionic)
2018-05-28 14:06:51 Didier Roche-Tolomelli ubiquity (Ubuntu Bionic): status New Triaged
2018-05-28 14:06:53 Didier Roche-Tolomelli ubiquity (Ubuntu Bionic): importance Undecided High
2018-05-28 14:06:58 Didier Roche-Tolomelli ubiquity (Ubuntu Bionic): milestone ubuntu-18.04.1
2018-05-28 14:07:01 Didier Roche-Tolomelli ubiquity (Ubuntu): milestone ubuntu-18.04.1
2018-05-28 14:10:15 Launchpad Janitor merge proposal linked https://code.launchpad.net/~didrocks/ubiquity/+git/ubiquity/+merge/346976
2018-05-29 14:12:56 Didier Roche-Tolomelli description 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). [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).
2018-05-29 14:22:14 Didier Roche-Tolomelli ubiquity (Ubuntu): assignee Didier Roche (didrocks)
2018-05-29 14:22:16 Didier Roche-Tolomelli ubiquity (Ubuntu Bionic): assignee Didier Roche (didrocks)
2018-06-11 13:49:11 Launchpad Janitor ubiquity (Ubuntu): status Triaged Fix Released
2018-06-14 20:42:33 Brian Murray ubiquity (Ubuntu Bionic): status Triaged Fix Committed
2018-06-14 20:42:35 Brian Murray bug added subscriber Ubuntu Stable Release Updates Team
2018-06-14 20:42:38 Brian Murray bug added subscriber SRU Verification
2018-06-14 20:42:42 Brian Murray tags rls-bb-incoming rls-bb-incoming verification-needed verification-needed-bionic
2018-06-15 09:13:03 Jean-Baptiste Lallement tags rls-bb-incoming verification-needed verification-needed-bionic rls-bb-incoming verification-done verification-done-bionic
2018-06-21 07:41:25 Launchpad Janitor ubiquity (Ubuntu Bionic): status Fix Committed Fix Released
2018-06-21 07:41:38 Ɓukasz Zemczak removed subscriber Ubuntu Stable Release Updates Team