logging_UserCrash failing on lakitu-incremental |
||||
Issue descriptionSince build #7794, the lakitu-incremental builders have been failing VMTest for the test logging_UserCrash. Links to a recent failed build: https://uberchromegw.corp.google.com/i/chromeos/builders/lakitu-incremental/builds/7811 I see the message: "core pattern should have been |/sbin/crash_reporter --user=%P:%s:%u:%e, not core" Snippet of the failure: 23:28:58 INFO | autoserv| AUTOTEST_STATUS::START ---- ---- timestamp=1459830538 localtime=Apr 05 04:28:58 23:28:58 INFO | autoserv| START ---- ---- timestamp=1459830538 localtime=Apr 04 23:28:58 23:28:58 INFO | autoserv| AUTOTEST_STATUS:: START logging_UserCrash logging_UserCrash timestamp=1459830538 localtime=Apr 05 04:28:58 23:28:58 INFO | autoserv| START logging_UserCrash logging_UserCrash timestamp=1459830538 localtime=Apr 04 23:28:58 23:28:59 INFO | autoserv| AUTOTEST_FETCH_PACKAGE:test-logging_UserCrash.tar.bz2:/usr/local/autotest/packages/test-logging_UserCrash.tar.bz2:/usr/local/autotest/tmp/_autotmp_o8RpbEharness-fifo/autoserv.fifo 23:28:59 INFO | autoserv| send_file. source: /build/lakitu/usr/local/build/autotest/packages/test-logging_UserCrash.tar.bz2, dest: /usr/local/autotest/packages/test-logging_UserCrash.tar.bz2, delete_dest: False,preserve_symlinks:False 23:28:59 INFO | autoserv| Using Rsync. 23:28:59 INFO | autoserv| Running 'rsync -L --timeout=1800 --rsh='/usr/bin/ssh -a -x -F /dev/null -i /dev/null -o ControlPath=/tmp/_autotmp_XLDfCassh-master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 9228' -az --no-o --no-g "/build/lakitu/usr/local/build/autotest/packages/test-logging_UserCrash.tar.bz2" "root@127.0.0.1:"/usr/local/autotest/packages/test-logging_UserCrash.tar.bz2""' 23:28:59 INFO | autoserv| Running (ssh) 'echo B > /usr/local/autotest/tmp/_autotmp_o8RpbEharness-fifo/autoserv.fifo' 23:28:59 INFO | autoserv| AUTOTEST_FETCH_PACKAGE:packages.checksum:/usr/local/autotest/packages.checksum:/usr/local/autotest/tmp/_autotmp_5r8UADharness-fifo/autoserv.fifo 23:28:59 INFO | autoserv| send_file. source: /build/lakitu/usr/local/build/autotest/packages/packages.checksum, dest: /usr/local/autotest/packages.checksum, delete_dest: False,preserve_symlinks:False 23:28:59 INFO | autoserv| Using Rsync. 23:28:59 INFO | autoserv| Running 'rsync -L --timeout=1800 --rsh='/usr/bin/ssh -a -x -F /dev/null -i /dev/null -o ControlPath=/tmp/_autotmp_XLDfCassh-master/socket -o StrictHostKeyChecking=no -o UserKnownHostsFile=/dev/null -o BatchMode=yes -o ConnectTimeout=30 -o ServerAliveInterval=900 -o ServerAliveCountMax=3 -o ConnectionAttempts=4 -o Protocol=2 -l root -p 9228' -az --no-o --no-g "/build/lakitu/usr/local/build/autotest/packages/packages.checksum" "root@127.0.0.1:"/usr/local/autotest/packages.checksum""' 23:28:59 INFO | autoserv| Running (ssh) 'echo B > /usr/local/autotest/tmp/_autotmp_5r8UADharness-fifo/autoserv.fifo' 23:28:59 INFO | autoserv| AUTOTEST_STATUS:: FAIL logging_UserCrash logging_UserCrash timestamp=1459830539 localtime=Apr 05 04:28:59 core pattern should have been |/sbin/crash_reporter --user=%P:%s:%u:%e, not core 23:28:59 INFO | autoserv| FAIL logging_UserCrash logging_UserCrash timestamp=1459830539 localtime=Apr 04 23:28:59 core pattern should have been |/sbin/crash_reporter --user=%P:%s:%u:%e, not core 23:28:59 INFO | autoserv| AUTOTEST_STATUS:: END FAIL logging_UserCrash logging_UserCrash timestamp=1459830539 localtime=Apr 05 04:28:59 23:28:59 INFO | autoserv| END FAIL logging_UserCrash logging_UserCrash timestamp=1459830539 localtime=Apr 04 23:28:59
,
Apr 5 2016
,
Apr 5 2016
This is caused by: https://chromium-review.googlesource.com/#/c/335264
,
Apr 5 2016
+jwerner, vapier This is breaking the incremental builder. I'd rather not revert your changes if it's a quick fix.
,
Apr 6 2016
Thanks, and sorry this happened. I've uploaded a CL that should hopefully fix it: https://chromium-review.googlesource.com/337302 It's a shame that this wasn't just caught by the CQ on submission. Do we not have a paladin for lakitu (if it's considered stable we should), or does the CQ no longer run VMTests these days? (Did it ever? Not quite sure...)
,
Apr 6 2016
No worries. We do have a lakitu paladin, but I don't think the CQ runs VMTests.
,
Apr 6 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/2fe1e4b4d8013a421af505620fde57cb65279bdd commit 2fe1e4b4d8013a421af505620fde57cb65279bdd Author: Julius Werner <jwerner@chromium.org> Date: Tue Apr 05 23:57:01 2016 crash-reporter: Revert inadvertent systemd change CL:335264 was really just supposed to change the userfeedback ebuild. Due to some rebasing and patch shuffling it seems that an incorrect change for the crash-reporter ebuild slipped in there and now breaks the systemd boards. This patch reverts that part. BUG= chromium:600774 TEST=None Change-Id: I14aa51fd676515cc8717f2de436b2ba3d9937fd5 Signed-off-by: Julius Werner <jwerner@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/337302 Reviewed-by: Aseda Aboagye <aaboagye@chromium.org> Reviewed-by: Andrey Ulanov <andreyu@google.com> [modify] https://crrev.com/2fe1e4b4d8013a421af505620fde57cb65279bdd/chromeos-base/crash-reporter/crash-reporter-9999.ebuild
,
Apr 6 2016
lakitu-incrementals are now passing. |
||||
►
Sign in to add a comment |
||||
Comment 1 by ameyd@google.com
, Apr 5 2016Owner: ameyd@google.com