Bug #611
maus_per_commit_gcc bzr lock as root
100%
Description
maus_per_commit_gcc fails because root has lock the bzr repo. Just needs someone to go in as root and do bzr break-lock. I don't have enough permissions/passwords.
Updated by Tunnell, Christopher over 12 years ago
- Status changed from Open to Closed
- % Done changed from 0 to 100
fixed. if it comes back could it be caused by some, for example, doxygen script running as root?
chowned to jenkins:
/var/lib/jenkins/jobs/MAUS_per_commit_gcc/workspace
and did break-lock. it seems like some operation failed as root.
Updated by Tunnell, Christopher over 12 years ago
thanks. if it breaks, reopen (in meetings). just did what blocked you.
Updated by Tunnell, Christopher over 12 years ago
how do I find out where the most recent offending style change is?
Updated by Rogers, Chris over 12 years ago
? still fails if I click on "Build now" in jenkins web interface...
Updated by Tunnell, Christopher over 12 years ago
- Status changed from Closed to Open
- % Done changed from 100 to 0
Updated by Tunnell, Christopher over 12 years ago
- Assignee changed from Tunnell, Christopher to Rogers, Chris
yours or I can deal with it monday
Updated by Rogers, Chris over 12 years ago
Doing bzr update in MAUS_per_commit yielded
bzr: ERROR: This tree contains left-over files from a failed operation.
Please examine /var/lib/jenkins/jobs/MAUS_per_commit_gcc/workspace/.bzr/checkout/limbo to see if it contains any files you wish to
keep, and delete it when you are done.
limbo was empty, so did rmdir limbo and then had another go at bzr update successfully. Now rerunning MAUS_per_commit build.
Updated by Tunnell, Christopher over 12 years ago
What? I had already done that.... and can do it now without problems.
Updated by Rogers, Chris over 12 years ago
Shrug - doing bzr update after rmdir limbo thing yielded
+N src/common_cpp/Simulation/MAUSEventAction.cc +N src/common_cpp/Simulation/MAUSEventAction.hh +N tests/cpp_unit/Simulation/MAUSEventActionTest.cc M .bzrignore M SConstruct M run_tests.bash M src/common_cpp/Simulation/FieldPhaser.cc M src/common_cpp/Simulation/MAUSGeant4Manager.cc M src/common_cpp/Simulation/MAUSGeant4Manager.hh M src/common_cpp/Simulation/VirtualPlanes.cc M src/common_cpp/Simulation/VirtualPlanes.hh M src/common_py/Configuration.py M src/common_py/Go.py M src/map/MapCppSimulation/MapCppSimulation.cc M tests/cpp_unit/Simulation/MAUSGeant4ManagerTest.cc M tests/py_unit/test_core_configuration.py M tests/style/cpplint_exceptions.py M tests/style/test_python_style.py All changes applied successfully.
which are the changes from me for the last couple of days. So it obviously thinks it saw some new changes... and now I get a different error on the build (test geometries segmentation fault...) so progress?
Updated by Rogers, Chris over 12 years ago
Okay, I logged out, all yours (I'll have a look in the morning now I think).
Updated by Tunnell, Christopher over 12 years ago
- Status changed from Open to Closed
- % Done changed from 0 to 100
build works
Updated by Rogers, Chris over 12 years ago
- Target version changed from Future MAUS release to MAUS-v0.0.5