The test suite explicitly defines userids for test users that get added to a flux-accounting DB, submit and run jobs, edit the database, etc., but as discovered with #477, this explicit definition can sometimes cause conflict with already-defined userids and result in test failures.
A cleaner solution could be to check for the current uid in sharness.d/flux-accounting.sh and instead define some environment variables for some userids to be associated with the test users that get added throughout the test suite:
The test suite explicitly defines userids for test users that get added to a flux-accounting DB, submit and run jobs, edit the database, etc., but as discovered with #477, this explicit definition can sometimes cause conflict with already-defined userids and result in test failures.
A cleaner solution could be to check for the current uid in
sharness.d/flux-accounting.sh
and instead define some environment variables for some userids to be associated with the test users that get added throughout the test suite:and then reference these in a file: