We are 23 commits behind: https://chromium-review.googlesource.com/c/chromium/src/+/924263


https://chromium-swarm.appspot.com/task?id=3bb85e6f61ac8c10&refresh=10&show_raw=1

  [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s 00ca940725cebace shell '( am force-stop org.chromium.chrome );echo %$?'
  [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s 00ca940725cebace shell '( ps | grep -F org.chromium.chrome; echo "PIPESTATUS: ${PIPESTATUS[@]}" );echo %$?'
  Browser is closed.
  [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/forwarder_host --adb=/b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb --serial-id=00ca940725cebace --unmap 49379
  [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s 00ca940725cebace shell '( ls /root );echo %$?'
  [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s 00ca940725cebace shell '( cd /sys/devices/system/cpu && for CPU in cpu0 cpu1 cpu2 cpu3 cpu4 cpu5; do test -e "${CPU}/cpufreq/scaling_available_governors" && grep -q ondemand ${CPU}/cpufreq/scaling_available_governors && test -e "$CPU/cpufreq/scaling_governor" && echo ondemand > "$CPU/cpufreq/scaling_governor"; echo -n "%~%$?%~%"; done );echo %$?'
  Successfully set cpufreq/scaling_governor to 'ondemand' on: cpu0 cpu1 cpu2 cpu3 cpu4 cpu5
  [host]> /b/swarming/w/ir/third_party/catapult/devil/bin/deps/linux2/x86_64/bin/adb -s 00ca940725cebace shell '( cd /sys/devices/system/cpu && for CPU in cpu0 cpu1 cpu2 cpu3 cpu4 cpu5; do cat "$CPU/online"; echo -n "%~%$?%~%"; done );echo %$?'
  Traceback (most recent call last):
    File "/b/swarming/w/ir/tools/perf/measurements/v8_detached_context_age_in_gc_unittest.py", line 102, in testWithSimplePage
      self.assertEquals(0, len(results.failures), msg=str(results.failures))
  AttributeError: 'PageTestResults' object has no attribute 'failures'

I think this is due to Ethan's test result refactoring work

This bug is P1 because it's blocking rolling out fixes to a failure on chromium waterfall ( issue 812639 )