TRQ-2044. Have TORQUE use an internal integer identifier to refer to jobs instead of the job id. This makes it so that we're performing int comparisons instead of string comparisons.
MOAB-6463. Enable the -Wextra warning by default for TORQUE builds.
TRQ-2590. Fix a regression around heterogeneous cray jobs caused by using job ids internally.
Fix the poor handling of task_save()'s return codes. Any non-PBSE_NONE error code means that it failed, but we were only handling the failure if it was -1. This is now rectified.
Cherry pick in the fix for threads not free'ing their memory when they scale back down. TRQ-2498.
Remove an unnecessary reference to things.
Make the server also give a busy message for mom updates when it is too busy. The moms have retry logic to handle this. Also, clear the status vector for strings that are getting sent to pbs_server so that it doesn't grow indefinitely larger.
Fix a crash when a mom update is received and pbs_server is too busy to service it.
Fix a bunch of issues reported by coverity.
Fix a few small leaks caught by valgrind.
Fix a few more valgrind issues.
Add another unit test for one of the refactored functions in process_request.c
Fix some classes that weren't being counted in our unit test numbers due to their .gcov files not getting generated.
Add a new file accidentally not included in the unit test changes.
Don't reference a freed variable after freeing it. TRQ-2608.
Port the updates to the job_container code to ascent to resolve some bugs in the iterator code.
Fixed a problem in job_clone_wt when printing
out a log message after a call to get the queue
for the job fails and the sprintf statement segfaults
because of a null pointer. TRQ-2593
AC-7188. Fix some valgrind issues.

Fix an uninitialized variable problem.
Also stop storing pointers to job usage info. In some race conditions the lock on the node is lost and
the job usage info object changes from beneath us.
Fix a few more memory leaks in pbs_server.
MOAB-6463. Background asynchronous requests.

Instead of handling asynchronous requests in the request threadpool we are going to start
handling them in the background or task threadpool so that requests are not limited by
the number of asynchronous requests that they make.