Failed to remove clientlogs/memevent directory
Bug #1279744 reported by
Javier Collado
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ubuntu Test Cases |
In Progress
|
Low
|
Paul Larson | ||
Bug Description
Looking at the output of the last execution of the memevent job:
http://
I see a problem when trying to remove the clientlogs/memevent directory:
+ rmdir clientlogs/memevent
rmdir: failed to remove 'clientlogs/
The rmdir command comes from the jenkins job template
(./jenkins/
# move results to base directory as expected by dashboard:
mv clientlogs/
rmdir clientlogs/{{test}}
Related branches
lp://staging/~pwlars/ubuntu-test-cases/touch-rmrf
- Javier Collado (community): Approve
-
Diff: 12 lines (+1/-1)1 file modifiedjenkins/templates/touch-base.xml.jinja2 (+1/-1)
- Ubuntu Test Case Developers: Pending requested
-
Diff: 6374 lines (+5848/-0) (has conflicts)98 files modifiedREADME-cli.rst (+80/-0)
jenkins/production.py (+95/-0)
jenkins/setup_jenkins.py (+213/-0)
jenkins/staging.py (+22/-0)
jenkins/templates/touch-base.xml.jinja2 (+93/-0)
jenkins/templates/touch-master.xml.jinja2 (+121/-0)
jenkins/templates/touch-smoke.xml.jinja2 (+163/-0)
jenkins/testconfig.py (+176/-0)
scripts/assert-image (+28/-0)
scripts/combine_results (+94/-0)
scripts/dashboard.py (+295/-0)
scripts/device (+191/-0)
scripts/get-adb-id (+39/-0)
scripts/jenkins.sh (+186/-0)
scripts/junit2utah.py (+70/-0)
scripts/provision.sh (+131/-0)
scripts/reboot-and-wait (+41/-0)
scripts/run-autopilot-tests.sh (+215/-0)
scripts/run-smoke (+357/-0)
scripts/run-touch-upgrade.sh (+46/-0)
scripts/statsd.py (+35/-0)
selftests/test_junit2utah.py (+49/-0)
selftests/test_reboot_and_wait.py (+66/-0)
selftests/test_run_smoke.py (+143/-0)
selftests/test_statsd.py (+64/-0)
tests/click_image_tests/check_preinstalled_list/check_preinstalled_list.py (+61/-0)
tests/click_image_tests/check_preinstalled_list/tc_control (+10/-0)
tests/click_image_tests/master.run (+5/-0)
tests/click_image_tests/tslist.run (+1/-0)
tests/customizations/master.run (+5/-0)
tests/customizations/setup.sh (+10/-0)
tests/customizations/ts_control (+1/-0)
tests/customizations/tslist.auto (+4/-0)
tests/default/ifconfig/tc_control (+13/-0)
tests/default/install/tc_control (+12/-0)
tests/default/master.run (+5/-0)
tests/default/netstat/tc_control (+12/-0)
tests/default/ping/pingtest.sh (+12/-0)
tests/default/ping/tc_control (+12/-0)
tests/default/pwd/tc_control (+9/-0)
tests/default/pwd/test.sh (+18/-0)
tests/default/route/tc_control (+12/-0)
tests/default/systemsettle/systemsettle.sh (+120/-0)
tests/default/systemsettle/tc_control (+9/-0)
tests/default/ts_control (+3/-0)
tests/default/tslist.run (+10/-0)
tests/default/uname/tc_control (+12/-0)
tests/default/unity8/tc_control (+9/-0)
tests/default/vmstat/tc_control (+12/-0)
tests/eventstat/eventstat/eventstat.sh (+5/-0)
tests/eventstat/eventstat/setup.sh (+7/-0)
tests/eventstat/eventstat/tc_control (+12/-0)
tests/eventstat/master.run (+5/-0)
tests/eventstat/tslist.run (+1/-0)
tests/memevent/master.run (+5/-0)
tests/memevent/setup.sh (+8/-0)
tests/memevent/ts_control (+1/-0)
tests/memevent/tslist.auto (+7/-0)
tests/memevent/ubuntu_test_cases/__init__.py (+6/-0)
tests/memevent/ubuntu_test_cases/memory_usage_measurement/__init__.py (+1/-0)
tests/memevent/ubuntu_test_cases/memory_usage_measurement/apps/__init__.py (+21/-0)
tests/memevent/ubuntu_test_cases/memory_usage_measurement/apps/browser.py (+103/-0)
tests/memevent/ubuntu_test_cases/memory_usage_measurement/apps/camera.py (+58/-0)
tests/memevent/ubuntu_test_cases/memory_usage_measurement/apps/gallery.py (+41/-0)
tests/memevent/ubuntu_test_cases/memory_usage_measurement/apps/media_player.py (+53/-0)
tests/memevent/ubuntu_test_cases/memory_usage_measurement/matchers.py (+37/-0)
tests/memevent/ubuntu_test_cases/memory_usage_measurement/probes.py (+170/-0)
tests/memevent/ubuntu_test_cases/memory_usage_measurement/smem-tabs (+687/-0)
tests/memevent/ubuntu_test_cases/memory_usage_measurement/tests/__init__.py (+1/-0)
tests/memevent/ubuntu_test_cases/memory_usage_measurement/tests/test_memory_usage.py (+79/-0)
tests/sdk/master.run (+5/-0)
tests/sdk/run_test.sh (+20/-0)
tests/sdk/setup.sh (+12/-0)
tests/sdk/ts_control (+1/-0)
tests/sdk/tslist.auto (+3/-0)
tests/security/master.run (+5/-0)
tests/security/run_test.sh (+25/-0)
tests/security/setup.sh (+12/-0)
tests/security/ts_control (+1/-0)
tests/security/tslist.auto (+6/-0)
tests/smem/master.run (+15/-0)
tests/smem/smem/smem-tabs (+687/-0)
tests/smem/smem/smem.sh (+12/-0)
tests/smem/smem/tc_control (+11/-0)
tests/smem/tslist.run (+1/-0)
tests/systemsettle/systemsettle-after/tc_control (+9/-0)
tests/systemsettle/systemsettle-before/tc_control (+9/-0)
tests/systemsettle/systemsettle.sh (+119/-0)
tests/systemsettle/tslist.run (+2/-0)
utils/host/adb-shell (+23/-0)
utils/host/autopilot-list (+18/-0)
utils/host/autopilot-run (+7/-0)
utils/host/prepare-autopilot-test.sh (+5/-0)
utils/target/autopilot-list (+13/-0)
utils/target/autopilot-run (+6/-0)
utils/target/prepare-autopilot-test.sh (+17/-0)
utils/target/unlock_screen.py (+98/-0)
utils/target/unlock_screen.sh (+8/-0)
Revision history for this message
| Paul Larson (pwlars) wrote | #1 |
| Changed in ubuntu-test-cases: | |
| assignee: | nobody → Paul Larson (pwlars) |
| status: | New → In Progress |
| Changed in ubuntu-test-cases: | |
| importance: | Undecided → Low |
To post a comment you must log in.
Yeah, it looks like there was a .lock file in that directly. I think we should just rm -rf that directory rather than rmdir.