Stable Release Candidate Log

2020

2020-02-03

5.4.18

• Reported build regression on Arm 32-bits in <8h
• Reported no regressions in -rc3

4.14.170, 4.19.102, 4.9.213, 5.5.2

• Reported no regressions in <24h

4.4.213

• Reported no regressions in <48h

2020-01-30

4.19.101, 5.4.17, 5.5.1

• Reported no regressions in <24h

2020-01-28

4.9.212, 4.14.169

• Reported build regression in 4.9 pre-rc and 4.14 pre-rc
• Reported no regressions on rc2 in <24h

4.4.212, 4.19.100, 5.4.16

• Reported no regressions in <24h

2020-01-24

4.14.168, 4.19.99

• Reported no regressions in <8h

5.4.15

• Reported Perf build failure in <8h
• Reported no regressions for -rc2

2020-01-22

4.9.211, 4.14.167, 4.19.98, 5.4.14

• Reported build failure on 4.19 pre-rc
• Reported no regressions in <8h

4.4.211

• Reported no regressions in <24h

2020-01-16

4.14.166, 4.19.97, 5.4.13

• Reported no regressions in <24h

2020-01-14

4.4.210, 4.9.210, 4.14.165, 4.19.96, 5.4.12

• Reported no regressions in <24h

2020-01-11

4.4.209, 4.9.209, 4.14.164, 4.19.95, 5.4.11

• Reported an arm build failure on 4.4 pre-rc
• Reported no regressions in <24h

2020-01-07

4.14.163, 4.19.94, 5.4.9

• Reported an arm build problem on 5.4 before the release candidate was announced
• Reported no regressions in <24h

2020-01-02

4.4.208, 4.14.162, 4.19.93

• Reported a syscalls regression before the release candidate was announced
• Reported no regressions in <48h

4.9.208

• Reported no regressions in <8h

5.4.8

• Reported an arm64 regression, resulting in an -rc2
• Reported no regressions in <24h

2019

2019-12-29

4.14.161, 4.19.92, 5.4.7

• Reported no regressions in <24h

2019-12-19

4.4.207, 4.9.207, 4.14.160, 4.19.91, 5.4.6

• Reported no regressions in <24h

2019-12-17

5.3.18, 5.4.5

• Reported no regressions in <24h

2019-12-16

4.14.159, 4.19.90, 5.3.17, 5.4.4

• Reported an arm regression on 4.14, resulting in an -rc2
• Reported no regressions in <24h

2019-12-11

4.19.89, 5.3.16, 5.4.3

• Reported no regressions in <24h

2019-12-04

4.4.206, 4.9.206, 4.14.158

• Reported no regressions in <24h

2019-12-03

4.19.88, 5.3.15, 5.4.2

• Reported no regressions in <24h

2019-11-27

4.14.157, 4.19.87

• Reported an arm32 build failure and an x86_64 kernel panic in <8h

4.4.204, 4.9.204, 5.4.1

• Reported no regressions in <24h

5.3.14

• Reported no regressions in <48h

2019-11-22

4.4.203, 4.9.203, 4.14.156, 4.19.86, 5.3.13

• Reported no regressions in <24h

2019-11-19

4.14.155, 5.3.12

• Reported no regressions in <24h

2019-11-15

4.4.202, 4.9.202

• Reported no regressions in <24h

2019-11-11

4.4.201, 4.9.201, 4.19.84, 5.3.11

• Reported no regressions in <24h

4.14.154

• Reported a boot regression
• Subsequently reported no regressions in rc2 in <24h

2019-11-08

4.4.200, 4.9.200, 4.14.153, 4.19.83, 5.3.10

• Reported no regressions in <24h

2019-11-04

4.4.199, 4.9.199, 4.14.152, 4.19.82, 5.3.9

• Reported no regressions in <24h

2019-10-27

4.4.198, 4.9.198, 4.14.151, 4.19.81, 5.3.8

• Reported no regressions in <48h

2019-10-16

4.4.197, 4.9.197, 4.14.150, 4.19.80, 5.3.7

• Reported no regressions in <24h

2019-10-10

4.14.149

• Reported no regressions in <8h

4.19.79, 5.3.6

• Reported no regressions in <24h

2019-10-06

4.4.196, 4.9.196, 4.14.148, 4.19.78, 5.2.20, 5.3.5

• Reported no regressions in <24h
• Noted mismatch in kselftests 5.3.1 vs 5.3.5 for net/udpgso.sh

2019-10-03

4.4.195, 4.9.195, 4.19.77, 5.2.19, 5.3.4

• Reported no regressions in <24h

4.14.147

• Reported no regressions in <48h

2019-09-29

4.19.76, 5.2.18, 5.3.2

• Reported no regressions in <48h

2019-09-20

4.4.194, 4.9.194, 4.14.146, 4.19.75, 5.2.17, 5.3.1

• Reported no regressions in <24h

2019-09-18

4.14.145

• Reported no regressions in <8h

4.19.74, 5.2.16

• Reported no regressions in <24h

2019-09-13

4.4.193, 4.9.193, 4.14.144, 4.19.73, 5.2.15

• Reported no regressions in <24h

2019-09-08

4.4.192

• Reported no regressions in <48h

4.9.192, 4.14.143, 4.19.72, 5.2.14

• Reported no regressions in <24h

2019-09-04

4.4.191, 4.9.191, 4.14.142, 4.19.70, 5.2.12

• Reported no regressions in <24h

2019-08-27

4.19.69 5.2.11 4.14.141

• Reported no regressions in <24h

2019-08-22

4.4.190 4.9.190 4.14.140 4.19.68 5.2.10

• Reported no regressions in <24h

2019-08-14

4.14.139, 4.19.67, 5.2.9

• Reported no regressions in <24h

2019-08-09

4.4.189, 4.9.189

• Reported no regressions on 4.9 in <8h
• Reported no regressions on 4.4 in <48h
  • Delay due to the investigation of failed x86 QEMU jobs, which were due to a QEMU upgrade from 2.9 to 3.1 in the lab.

2019-08-08

4.14.138, 4.19.66, 5.2.8

• Reported no regressions in <24h

2019-08-05

4.4.188, 4.9.188, 4.14.137, 4.19.65, 5.2.7

• Reported no regressions in <24h

2019-08-02

4.4.187, 4.9.187, 4.14.136, 4.19.64, 5.2.6

• Reported no regressions in <24h

2019-07-29

4.14.135, 4.19.63, 5.2.5

• Reported no regressions in <24h

2019-07-26

4.19.62, 5.1.21, 5.2.4

• Reported no regressions in <24h
• Last 5.1 release

2019-07-24

4.19.61, 5.1.20, 5.2.3

• Reported no regressions on 4.19 and 5.1 in <24h
• Reported KVM regression caused by a test change, not a kernel change.

2019-07-17

4.4.186, 4.9.186, 4.14.134, 4.19.60, 5.1.19, 5.2.2

• Reported no regressions in <24h

2019-07-12

4.19.59, 5.1.18, 5.2.1

• First 5.2 stable release
• Reported no regressions in <24h

2019-07-08

4.4.185, 4.9.185, 4.14.133, 4.19.58, 5.1.17

• Reported no regressions in <24h

2019-07-02

4.14.132, 4.19.57, 5.1.16

• Reported no regressions in <24h

2019-06-26

4.4.184, 4.9.184, 4.14.131

• Single patch release, bringing the TCP fix from 2019-06-22 release back to 4.4, 4.9, and 4.14
• Reported no regressions in <24h

2019-06-24

4.14.130, 4.19.56, 5.1.15

• Reported no regressions in <24h

2019-06-22

4.19.55, 5.1.14

• No stable-review period; this was a hot fix release for “Steam does not connect on kernels newer than 2019-06-17”

2019-06-20

4.4.183, 4.9.183, 4.14.129, 4.19.54, 5.1.13

• Reported pre-rc arm 32/64 build failure on 4.9, suggesting a missing backport
• Reported no regressions in <24h

2019-06-17

4.14.128, 4.19.53, 5.1.12

• Reported no regressions in <24h
• Reported issue with ptrace in pre-rc results
• Noted v4l2 issue fixed in 4.14 thanks to requested backport
• Noted workqueue.c kernel warning fixed in 5.1

2019-06-17

4.4.182, 4.9.182, 4.14.127, 4.19.52, 5.1.11

• No stable-review period; this was a security release for TCP SACK

2019-06-13

4.14.126, 4.19.51, 5.1.10

• Reported no regressions in <24h

2019-06-09

4.4.181, 4.9.181, 4.14.125, 4.19.50, 5.1.9

• Reported no regressions in <8h

2019-06-07

4.14.124, 4.19.49, 5.1.8

• btrfs compile failure reported against 4.14, fixed in -rc2
• Reported no regressions in <24h

2019-06-03

4.19.48, 5.0.21, 5.1.7

• Reported no regressions in <24h
• Last 5.0 release

2019-05-29

4.9.180, 4.14.123, 4.19.47, 5.0.20, 5.1.6

• 4.9, 5.0 Reported no regressions in <24h
• 4.14, 4.19, 5.1 Reported no regressions in <48h

2019-05-23

4.9.179, 4.14.122, 4.19.46, 5.0.19, 5.1.5

• Reported no regressions in <24h

2019-05-20

4.9.178, 4.14.121, 4.19.45, 5.0.18, 5.1.4

• Reported no regressions on 4.9 and 4.14 in <24h
• Reported ext4 regression (thread) on 4.19, 5.0, 5.1 in <24h
  • Subsequently reported no regressions on 4.19, 5.0, 5.1

2019-05-15

4.4.180, 4.9.177, 4.14.120, 4.19.44, 5.0.17, 5.1.3

• Reported no regressions in <24h

2019-05-14

4.9.176, 4.14.119, 4.19.43, 5.0.16, 5.1.2

• Security release (without normal review round) for Microarchitectural Data Sampling (MDS)

2019-05-09

4.9.175, 4.14.118, 4.19.42, 5.0.15, 5.1.1

• Reported no regressions in <24h

2019-05-06

4.9.174, 4.14.117, 4.19.41, 5.0.14

• Reported no regressions in <24h

2019-05-04

4.19.40, 5.0.13

• Reported no regressions in <24h

2019-05-02

4.9.173, 4.14.116, 4.19.39, 5.0.12

• Reported no regressions in <24h
• Noted that v4l2-compliance kernel crash fixed as a result of LKFT report and subsequent backport of ed356f110403 (“media: vivid: check if the cec_adapter is valid”)

2019-04-30

4.9.172, 4.14.115, 4.19.38, 5.0.11

• Reported no regressions in <24h

2019-04-24

4.4.179, 4.9.171, 4.14.114, 4.19.37, 5.0.10

• Reported no regressions in <24h

2019-04-18

4.9.170, 4.14.113, 4.19.36, 5.0.9

• Reported perf-related build failures on 4.19 and 5.0[1][2]
• On 4.9 and 4.14, reported no regressions in <24h
• On 4.19 and 5.0, reported no regressions in <24h after perf issues were resolved

2019-04-15

4.9.169, 4.14.112, 4.19.35, 5.0.8

• Reported no regressions in <24h

2019-04-04

4.9.168, 4.14.111, 4.19.34, 5.0.7

• Reported no regressions in <24h

2019-04-01

4.4.178, 4.9.167, 4.14.110, 4.19.33, 5.0.6

• Reported no regressions in <24h

2019-03-26

4.9.166, 4.14.109, 4.19.32, 5.0.5

• Reported no regressions in <24h

2019-03-22

4.4.177, 4.9.165, 4.14.108, 4.19.31, 5.0.4

• Reported no regressions in <24h

2019-03-18

4.9.164, 4.14.107, 4.19.30, 4.20.17, 5.0.3

• 4.9, 4.14, 4.19 reported no regressions in <8h
• 4.20, 5.0 reported no regressions in <24h
• Last 4.20 release

2019-03-12

4.9.163, 4.14.106, 4.19.29, 4.20.16, 5.0.2

• Reported no regressions in <24h

2019-03-08

4.19.28, 4.20.15, 5.0.1

• Reported no regressions in <24h

2019-03-04

4.9.162, 4.14.105, 4.19.27, 4.20.14

• Reported no regressions in <24h

2019-02-25

4.9.161, 4.14.104, 4.19.26, 4.20.13

• Reported no regressions in <24h

2019-02-21

4.4.176, 4.9.160, 4.14.103, 4.19.25, 4.20.12

• Reported no regressions in <24h

2019-02-18

4.4.175, 4.9.159, 4.14.102, 4.19.24, 4.20.11

• Reported no regressions on 4.4, 4.9 in <8h
• Reported no regressions on 4.14, 4.19, 4.20 in <24h

2019-02-13

4.9.157, 4.14.100, 4.19.22, 4.20.9

• Reported no regressions in <24h

2019-02-11

4.9.156, 4.14.99, 4.19.21

• Reported no regressions in <24h

4.20.8

• Reported no regressions in <48h

2019-02-07

4.4.174

• Reported no regressions in <24h

2019-02-04

4.4.173, 4.9.155, 4.14.98, 4.19.20, 4.20.7

• LTP/fanotify09 fixed on 4.14.98 due to backport requested in 4.14.97
• Reported no regressions in <24h

2019-01-30

4.9.154, 4.14.97, 4.19.19, 4.20.6

• LTP upgraded to 20190115 for all branches
• Reported no regressions in <48h

2019-01-24

4.4.172, 4.9.153, 4.14.96, 4.19.18, 4.20.5

• kselftest upgraded to 4.20 for all LTS branches
• Reported no regressions in <24h

2019-01-21

4.9.152, 4.14.95, 4.20.4

• Reported crashes in v4.20.3-15-g5592f5bf010b which were intentional ‘canaries’ (the canary successfully died)
• Reported no regressions in <24h

4.19.17

• Reported no regressions in <48h

2019-01-15

4.4.171, 4.9.151, 4.14.94, 4.19.16, 4.20.3

• Reported no regressions in <24h

2019-01-11

4.4.170, 4.9.150, 4.14.93, 4.19.15, 4.20.2

• Reported no regressions in <24h

2019-01-07

4.9.149, 4.14.92, 4.19.14, 4.20.1

• Reported build failure on 4.9.149-rc1, resulting in -rc3
• Reported build failure on 4.14.92 pre-rc
• Reported build failure on 4.14.92-rc1, resulting in -rc2
• Reported no regressions in <24h

2018

2018-12-28

4.9.148, 4.14.91, 4.19.13

• Reported no regressions in <8h

2018-12-20

4.4.169, 4.14.90

• Reported no regressions in <24h

4.9.147, 4.19.12

• Reported no regressions in <8h

2018-12-18

4.19.11

• Reported no regressions in <8h

2018-12-14

4.4.168, 4.9.146, 4.14.89, 4.19.10

• Reported no regressions in <48h

2018-12-11

4.4.167, 4.9.145, 4.14.88, 4.19.9

• Noted that LTP syscalls:mlock203 has been fixed in all environments on 4.4.167
• Reported no regressions in <24h

2018-12-07

4.9.144

• Reported a hugetlbfs regression in -rc1 Verified fixed in -rc2.

4.14.87, 4.19.8

• Reported no regressions in <24h

2018-12-04

4.9.143, 4.14.86, 4.19.7

• Reported no regressions in <24h
• Reported a panic discovered on 4.19.7 (not a regression) related to TCP tail loss

2018-11-29

4.4.166, 4.9.142, 4.14.85, 4.19.6

• Reported no regressions in <24h

2018-11-26

4.4.165, 4.9.141, 4.14.84, 4.19.5

• Reported no regressions in <48h

2018-11-21

4.9.139, 4.14.83, 4.19.4

• Reported no regressions in <48h

2018-11-19

4.4.164, 4.9.138, 4.14.82, 4.18.20, 4.19.3

• Last 4.18 release
• Reported no regressions in <24h

2018-11-11

4.9.137, 4.14.81, 4.18.19, 4.19.2

• Rafael Tinoco reported a build problem on 4.9, resulting in patch f69ffc5d3db8 (“cpupower: Fix coredump on VMWare”) being dropped.
• Reported no regressions in <24h

2018-11-08

4.4.163, 4.9.136, 4.14.80, 4.18.18

• Reported no regressions in <24h

2018-11-02

4.14.79, 4.18.17, 4.19.1

• First 4.19 stable release
• Reported no regressions in <48h

2018-10-18

4.4.162, 4.9.135, 4.14.78, 4.18.16

• Reported no regressions in <24h

2018-10-16

4.9.134, 4.14.77, 4.18.15

• Reported no regressions in <24h

2018-10-11

4.4.161, 4.9.133, 4.14.76, 4.18.14

• Reported no regressions in <24h

2018-10-08

4.4.160, 4.9.132, 4.14.75, 4.18.13

• Reported no regressions in <48h

2018-10-02

4.9.131, 4.14.74, 4.18.12

• Reported no regressions in <48h

2018-09-27

4.4.159, 4.9.130, 4.14.73, 4.18.11

• Reported no regressions in <24h

2018-09-24

4.4.158, 4.9.129, 4.14.72, 4.18.10

• Bisected and reported regressions related to pinctrl on 4.14 and 4.18
• Bisected and reported regression related to rpmsg on db410c that was introduced in 4.14.71
• 4.4, 4.9 <24h
• 4.14, 4.18 <48h

2018-09-18

4.4.157, 4.9.128, 4.14.71, 4.18.9

• Reported no regressions in <24h
• Reported build failure on pre-rc tree

2018-09-13

4.4.156, 4.9.127, 4.14.70, 4.18.8

• Reported no regressions in <24h

2018-09-07

4.4.155, 4.9.126, 4.14.69, 4.18.7

• Reported no regressions on 4.9, 4.14, and 4.18 in <48h
• Reported regressions related to “userns: move user access out of the mutex” on 4.4 in <48h
  • Reported no regressions against 4.4.155-rc3 in <48h

2018-09-03

4.4.154, 4.9.125, 4.14.68, 4.18.6

• Reported no regressions on 4.4 and 4.9 in <24h
• Reported build failure on pre-rc tree
• 4.18 and 4.14 BUG found on - tlb_flush_mmu
  • Bad patch - mm/tlb, x86/mm: Support invalidating TLB caches for RCU_TABLE_FREE
  • Missing patch - mm: move tlb_table_flush to tlb_flush_mmu_free

2018-08-27

4.4.153

• Reported no regressions in <24h

2018-08-23

4.4.152, 4.9.124, 4.14.67, 4.17.19, 4.18.5

• Last 4.17 release
• Reported no regressions in <24h

2018-08-21

4.4.151, 4.9.123, 4.14.66, 4.17.18, 4.18.4

• Reported no regressions in <24h

2018-08-16

4.4.149, 4.9.121, 4.14.64, 4.17.16, 4.18.2, 4.4.150, 4.9.122, 4.14.65, 4.17.17, 4.18.3

• The initial set of RCs were announced on Thursday. On Friday, they were tagged for release and the second set of RCs, which contained 1 patch, were pushed but not yet announced. On Saturday, we reported our results based on both sets of RCs, and both were subsequently released and announced on the same day.
• Reported no regressions in <48h
• See related: Two rounds of stable kernels released (LWN)

2018-08-14

4.4.148, 4.9.120, 4.14.63, 4.17.15, 4.18.1

• First 4.18 stable release candidate
• Each branch had multiple pushes, for a total of ~18. This created a high queue depth in our build and test environments. After 24h, results were reported based on a manual review of the aggregated (but still incomplete) data that was available.
• Reported no regressions in <48h
• See related: Meltdown strikes back: the L1 terminal fault vulnerability (LWN)

2018-08-07

4.4.147, 4.9.119, 4.14.62, 4.17.14

• Reported no regressions in <48h

2018-08-06

4.4.146, 4.9.118, 4.14.61, 4.17.13

• Reported no regressions in <48h

2018-08-03

4.9.117, 4.14.60, 4.17.12

• Reported no regressions in <24h

2018-07-27

4.4.145, 4.9.116, 4.14.59, 4.17.11

• Reported no regressions in <24h

2018-07-23

4.4.144, 4.9.115, 4.14.58, 4.17.10

• Reported no regressions in <24h

2018-07-20

4.4.143, 4.9.114, 4.14.57, 4.17.9

• Reported no regressions in <24h

2018-07-18

4.4.142

• Reported no regressions in <8h

2018-07-17

4.17.8

• Reported no regressions in <24h

2018-07-16

4.4.141, 4.9.113, 4.14.56, 4.17.7

• Reported regression in creat and open syscalls in 4.17.7 within 24h
  • Regression in behavior was intentional, due to backport of 0fa3ecd87848 to fix CVE-2018-13405. LTP patch proposed.
• All remaining branches subsequently reported in <48h

2018-07-10

4.4.140, 4.9.112, 4.14.55, 4.17.6

• Reported no regressions in <24h

2018-07-06

4.14.54, 4.17.5

• Reported no regressions in <24h

2018-07-01

4.4.139, 4.9.111, 4.14.53, 4.17.4

• Reported no regressions in <24h

2018-06-24

4.14.52, 4.16.18, 4.17.3

• Reported no regressions in <24h
• Noted Kselftest test case mov_ss_trap_64 is causing kernel panic on qemu-system-x86_64 and PASS on real x86_64 hardware. Bug 3916. This is due to the version of the host kernel on the host running QEMU jobs.
• Last 4.16

4.9.110

• Reported no regressions in <24h

2018-06-18

4.14.51, 4.16.17

• Reported no regressions in <24h

2018-06-14

4.4.138

• Reported no regressions in <24h
• Noted that MAX_LFS_FILESIZE regression introduced in 4.4.137 has been fixed

4.9.109, 4.14.50, 4.16.16, 4.17.2

• Reported no regressions in <24h

2018-06-12

4.4.137

• Reported in <48h
• Regression in MAX_LFS_FILESIZE macro detected by ltp/cve-2011-2496
  • Fixed with backport of 0cc3b0ec23ce (“Clarify (and fix) MAX_LFS_FILESIZE macros”) in 4.4.138

4.9.108

• Reported no regressions in <24h

2018-06-09

4.14.49, 4.16.15

• Reported no regressions in <24h

4.17.1

• Reported no regressions in <48h

2018-06-05

4.4.136, 4.9.107

• Reported no regressions in <24h

2018-06-04

4.9.106, 4.14.48, 4.16.14

• Reported no regressions in <24h

2018-05-30

4.9.105, 4.14.46, 4.14.47

• Quick releases that did not go through the normal RC process
• 4.9.105 announcement
• 4.14.46 announcement
• 4.14.47 announcement

2018-05-28

4.4.134, 4.9.104, 4.14.45, 4.16.13

• Reported no regressions in <24h
• There was a regression noted in ltp/cve-2017-5669, which was expected. See the issue at Github for details.

2018-05-24

4.4.133, 4.9.103, 4.14.44, 4.16.12

• Reported no regressions in <24h

2018-05-21

4.9.102, 4.14.43, 4.16.11

• Reported no regressions in <24h

2018-05-18

4.9.101, 4.14.42, 4.16.10

• Reported no regressions in <24h

2018-05-14

4.4.132, 4.9.100, 4.14.41, 4.16.9

• Reported no regressions in <24h

2018-05-08

4.9.99, 4.14.40, 4.16.8

• Reported no regressions in <24h

2018-04-30

4.4.131, 4.9.98, 4.14.39, 4.16.7

• Reported no regressions in <24h

2018-04-27

4.4.130, 4.9.97, 4.14.38, 4.16.6

• Reported no regressions in <8h

2018-04-25

4.14.37

• Reported no regressions in <24h

4.16.5

• Reported no 4.16.5 regressions in <24h
• Noted regression in 4.16.4 on db410c

2018-04-22

• Rare Sunday morning push (first this year), complicated by Monday qa-reports scheduled outage.

4.4.129

• Reported no regressions in <24h

4.9.96

• Reported arm64 boot regression in <24h
• Manual bisection results reported in <48h
• Reported no regressions in <48h on RC3

4.14.36

• Shuah reported locking issue during boot
• Reported no regressions in <48h on RC3

4.16.4

• Shuah reported locking issue during boot
• Reported no regressions in <48h on RC3

2018-04-17

• All RC builds failed due to change in -next. Fixed via https://github.com/96boards/meta-rpb/pull/166

4.9.95

• First response in <48h.
• A network driver issue from 4.9.94 was discovered on x15 in the network stack, reported at https://lists.linaro.org/pipermail/linux-stable-mirror/2018-April/038977.html

4.14.35, 4.15.18, 4.16.3

• Reported no regressions in <24h

2018-04-11

4.4.128, 4.9.94

• Reported no regressions in <24h

2018-04-10

4.14.34, 4.15.17, 4.16.2

• Reported no regressions in <24h

2018-04-06

4.4.127, 4.14.33, 4.16.1

• Reported no regressions in <24h

4.9.93

• Reported in <24h
• db410c issue detected - bug 3723; cpu-on-off-test

4.15.16

• Reported no regressions in <8h

2018-03-29

4.4.126, 4.14.32

• Report no regressions in <24h

4.9.92, 4.15.15

• Report no regressions in <48h

2018-03-27

• Initially, all branches had a build error due to /COPYING changing on -next, and the checksum of said file being hard coded in our OE recipe.

4.4.125

• Build failure on arm64 reported in <8h
• Results in <48h

4.9.91

• Results in <24h

4.14.31

• Regression identified in libhugetlbfs/arm32 https://bugs.linaro.org/show_bug.cgi?id=3689
• Results in <48h

4.15.14

• Regression identified in libhugetlbfs/arm32 https://bugs.linaro.org/show_bug.cgi?id=3689
• Results in <48h

2018-03-23

4.4.124, 4.9.90

• Results in <8h

4.14.30, 4.15.13

• Build failed on arm32
• First response in <8h
• No results for hikey or db410c due to offline devices and limited support availability due to Connect (arm64 was still covered by juno devices)

2018-03-20

4.4.123

• Failed to build on arm32
• First response in <8h

4.9.89

• Failed to build on arm32,arm64.. 6 patches causing build issues
• First response in <8h

4.14.29

• Results in <24h

4.15.12

• Results in <24h

2018-03-16

4.4.122, 4.9.88

• Results in <24h

4.14.28

• rc1: arm/arm64 build error reported
• rc3: arm build error reported
• First response in <8h

4.15.11

• arm/arm64 build error reported
• rc3: arm build error reported
• First response in <8h

2018-03-13

• -rc1 contained arm64 boot breakage reported (as previously seen on next and mainline per https://bugs.linaro.org/show_bug.cgi?id=3676). Greg pulled the patch and released an -rc2.

4.14.27, 4.15.10

• Results in <48h

2018-03-10

• Results longer than 48h due to weekend availability. RC was pushed at Sat Mar 10 00:18:21 UTC 2018.
• Many infrastructure failures were mentioned with regard to the reported boot failures that we experience on db410c.
• Some incorrect results were sent and then corrected, due to manual nature of reporting.
• 4.4 x86_64 not reported due to build infrastructure error

4.4.121, 4.9.87, 4.14.26, 4.15.9

• Results in <72h

2018-03-07

• Self induced snapshots.linaro.org outage during build

4.14.25, 4.15.8

Results in <24h

2018-03-02

• git.yoctoproject.org outage caused build delays in 4.4 and 4.14
• db410c and qemu x86_64 reported for first time

4.4.120, 4.9.86, 4.14.24

• Results in <24h

2018-02-26

• Builds took ~2h. Needed to rebuild 4.9/hikey for ‘sstate_create_package’ infrastructure failure.

4.4.119, 4.9.85, 4.14.23, 4.15.7

• Results in <24h

2018-02-23

• All builds worked first time
• Limited availability (Friday evening push (UTC))
  • multiple pushes

4.4.118, 4.14.22

• Results in <8h

4.9.84, 4.15.6

• Results in <48h

2018-02-21

• Issue with lkft.v.l.o being slow. Squad had issues submitting jobs and fetching results.

4.4.117, 4.14.21

• Results in <8h

4.9.83

• Results in <8h
• arm64 legitimate build failure, reported, patch dropped

4.15.5

• Results in <8h
• infrastructure build failure on x15 “Function failed: sstate_create_package”

2018-02-15

• Builds took 7 hours. 13 total failures.
  • Some hikey failures caused by breakage introduced same day
  • Others caused by long standing git-related issues in jenkins environment
    • Fixed (hopefully permanently) with ‘bitbake -c cleanall edk2-hikey’

4.4.116, 4.14.20

• Results in <24h

4.9.82

• Results in <24h
• Noted getrusage04 intermittent failure https://bugs.linaro.org/show_bug.cgi?id=3507

4.15.4

• Results in <24h
• Noted netns_netlink failure on x15. See https://bugs.linaro.org/show_bug.cgi?id=3484

2018-02-09

• LTP was upgraded from 20170929 to 20180118, causing a falsely reported regression in fanotify06.

4.9.81, 4.14.19, 4.15.3

• Results in <8h

2018-02-05

4.14.18, 4.15.2

• Results in <8h

2018-02-02

4.4.115, 4.9.80, 4.14.17

• Results in <8h

4.15.1

• Results in <24h
• This was the first 4.15 RC.
• Report showed false failures because the new branch was not yet baselined, and also because we were running 4.14 kselftest against 4.15.
• 4.15 build was submitted for review but not yet merged when the branch was released, causing last minute Friday afternoon scramble (thanks Daniel). Should have had it building and baselined ahead of time.

2018-01-29

4.4.114, 4.9.79, 4.14.16

• Results in <24h

2018-01-22

4.4.113

• Results in <24h
• Issue with ‘main.sh’ kselftest on hikey due to missing patch on linaro’s hikey tree. Resolved.

4.9.78, 4.14.15

• Results in <24h

2018-01-15

• Greg requested verifying bpf in 4.4 and 4.9 but we did not have a good way to do so. Tests aren’t backported. We are looking at getting bcc running on hikey, as a means of manual verification.

4.4.112

• Results in <24h
• Build (infrastructure) failure with hikey, requiring manual intervention.
• 5 RCs

4.9.77

• Results in <24h
• 6 RCs

4.14.14

• Results in <24h
• Build (infrastructure) failure with hikey, requiring manual intervention.
• 4 RCs

2018-01-08

4.4.111

• Results in <24h
• Release candidate republished 4 times

4.9.76

• Results in <24h
• Release candidate republished 5 times

4.14.13

• Results in <24h
• Release candidate republished 3 times

2018-01-06

4.14.12

• Results in <24h.
• Build failure with x15, requiring manual intervention.

2018-01-05

4.4.110

• Results in <24h.
• LTP poll02 failure on x15. Not reproducible. Not considered a regression. (link)

4.9.75

• Results in <24h.
• Build failure with x15, requiring manual intervention.

2018-01-01

4.4.109, 4.9.74

• Results in <8h.

4.14.11

• Results in <8h.
• kselftest ldt_gdt_64 failure on x86, due to mismatch between kselftest version and kernel version. (link)