New issue
Advanced search Search tips

Issue 830841 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Closed: Dec 18
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Chromad: Add autotest for kpasswd

Project Member Reported by ljusten@chromium.org, Apr 9 2018

Issue description

We need to have an autotest for kpasswd, so that we can catch seccomp failures. There's no direct way to call authpolicyd to trigger a password change, so there might be some plumbing necessary.
 

Comment 1 Deleted

Labels: OS-Chrome
Cc: -rsorokin@chromium.org ljusten@chromium.org
Labels: M-73
Owner: rsorokin@chromium.org
Roman, didn't you do that?
Project Member

Comment 4 by bugdroid1@chromium.org, Dec 18

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/autotest-private/+/86858a0895b235e6ab1913ef583da924fa4db555

commit 86858a0895b235e6ab1913ef583da924fa4db555
Author: Roman Sorokin <rsorokin@chromium.org>
Date: Tue Dec 18 12:28:56 2018

Status: Fixed (was: Assigned)
Hi Roman, is this autotest available to use? I got "No test found" error:

10:31:24 ERROR| No test found, searching for possible tests with job name similar to enterprise_AuthPolicyDaemonServer
Traceback (most recent call last):
  File "/build/coral/usr/local/build/autotest/site_utils/test_that.py", line 371, in <module>
    sys.exit(main(sys.argv[1:]))
  File "/build/coral/usr/local/build/autotest/site_utils/test_that.py", line 367, in main
    return _main_for_local_run(argv, arguments)
  File "/build/coral/usr/local/build/autotest/site_utils/test_that.py", line 304, in _main_for_local_run
    pretend=arguments.pretend)
  File "/build/coral/usr/local/build/autotest/site_utils/test_runner_utils.py", line 828, in perform_run_from_autotest_root
    host_attributes=host_attributes)
  File "/build/coral/usr/local/build/autotest/site_utils/test_runner_utils.py", line 575, in perform_local_run
    ignore_deps=ignore_deps)
  File "/build/coral/usr/local/build/autotest/site_utils/test_runner_utils.py", line 222, in fetch_local_suite
    'following tests?\n  %s' % '\n  '.join(possible_tests))
ValueError: Found no tests. Check your suite name, test name, or test matching wildcard.
Did you mean any of following tests?
  enterprise_SmbProviderDaemon
  enterprise_KioskEnrollmentServer
  enterprise_RemoraRequisitionServer
  enterprise_CFM_AutotestSmokeTest
  enterprise_KioskPerf
  enterprise_CFM_HuddlyUpdater
  enterprise_CFM_HuddlyMonitor
  enterprise_CFM_AutoZoomSanity
  enterprise_PowerManagement
  enterprise_ClearTPM

Can you please take a look? Thanks!
This is a private test, you'll need a Chrome OS internal checkout. The test
also runs in a nightly suite, don't remember which one.

On Thu, Dec 27, 2018, 19:54 ibezmenov via monorail <
monorail+v2.208251540@chromium.org wrote:
Status: Verified (was: Fixed)
Ok, in stainless I see that it runs in the ent-nightly suite, marking as Verified. Thanks!

Sign in to add a comment