[HTCondor-users] Misspelt submit node classads - JobsWierdTimestamps and RecentJobsWierdTimestamps

[Greg.Hitchen@xxxxxxxx]

I happened to notice the following misspelt submit node classads today when running a condor_status âschedd âl command:

 

JobsWierdTimestamps

RecentJobsWierdTimestamps

 

It seems a bit âweirdâ that it hasnât been picked up previously! ;) J

 

It could lead to issues at some stage in the source if some modifications to the code start spelling it correctly.

 

Cheers

 

Greg

 

 

INCORRECT SPELLING

 

condor-per:/home/samba/logs/condor-8.5.8/src # grep -i wierd */*

 

condor_io/shared_port_endpoint.cpp:             // a bit wierd, but ConnectNamedPipe returns true on success. OR it

condor_procapi/procapi.cpp:             // This is a little wierd, so manually print this one out if

condor_schedd.V6/schedd.cpp:                            stats.JobsWierdTimestamps += 1;

condor_schedd.V6/schedd.cpp:                            OTHER.JobsWierdTimestamps += 1;

condor_schedd.V6/schedd.cpp:                            stats.JobsWierdTimestamps += 1;

condor_schedd.V6/schedd.cpp:                            OTHER.JobsWierdTimestamps += 1;

condor_schedd.V6/schedd_stats.cpp:   SCHEDD_STATS_ADD_RECENT(Pool, JobsWierdTimestamps,     if_poolverbose);

condor_schedd.V6/schedd_stats.h:   stats_entry_recent<int>    JobsWierdTimestamps;    // jobs which exited with questionable times for exec or post-exec

condor_scripts/ld:                      # wierd, I must failthfully translate it.

condor_shadow.std/shadow.cpp:           but for some reason the shadow exited wierdly and the

condor_shadow.std/shadow.cpp:                   do if a job suspends wierdly or some such thing. This function

condor_starter.V6.1/baseStarter.cpp:                            // a bit wierd here. we publish if there are any assigned, we also always

condor_tests/job_ckpt_signals_std.c:                            /* Wierd ones ... */

condor_tests/job_rsc_all-syscalls_std.c:                wierd behaviour of fread(). Notice the check in SUCCESS. */

 

 

CORRECT SPELLING

 

condor-per:/home/samba/logs/condor-8.5.8/src # grep -i weird */*

 

classad/aclocal.m4:# symlink; some systems play weird games with the mod time of symlinks

condor_daemon_core.V6/daemon_core.cpp:// which is necessary to encapsulate all the weird platform specifics

condor_daemon_core.V6/daemon_core_main.cpp:                       of NT weirdness with starting as a service, etc.  Also,

condor_dagman/job.cpp:                  "value is weird.\n");

condor_dagman/parse.cpp:                              // just something weird, which we'll print

condor_gridmanager/gahp-client.cpp:                     // something is very weird; log it and move on...

condor_gridmanager/proxymanager.cpp:            dprintf (D_ALWAYS, "WEIRD! MyProxyManager::GetDelegationReaper unable to find entry for pid %d", exitPid);

condor_gridmanager/proxymanager.cpp:                                    dprintf( D_ALWAYS, "WEIRD! Cannot read err file %s, "

condor_gridmanager/proxymanager.cpp:                    dprintf( D_ALWAYS, "WEIRD! Cannot open err file %s, "

condor_io/authentication.cpp:           // we had a mapfile, but we couldnt create one.  This just covers weird corner cases.

condor_procapi/procapi.cpp:             // There seems to be something weird about jiffie_start_time

condor_schedd.V6/qmgmt.cpp:             // I have seen a weird bug where the getMaxJobsSubmitted() returns

condor_startd.V6/ResMgr.cpp:            // the startd, or else too much weirdness is possible.

condor_startd.V6/ResState.cpp:                          // this is a little weird, but we can't just enter

condor_startd.V6/Resource.h:            // Since the preempting state is so weird, and when we want to

condor_startd.V6/claim.cpp:                     // a weird, invalid state.  don't rely on using any member

condor_startd.V6/vm_common.cpp:                         // weird, malformed ad.

condor_startd.V6/vm_common.cpp:                         // weird, malformed ad.

condor_starter.V6.1/vm_gahp_server.cpp:                 // something is very weird; log it and move on...

condor_sysapi/README:WEIRD THINGS

condor_tests/job_consumption_policies_basic_van.run:# currently (circa 8.1.1) there is some weird interaction between

condor_tests/job_core_env_java.run:# before the test let's throw some weird crap into the environment

condor_tests/job_core_env_java.run:$ENV{"weirdchars"} = "

 

condor_tests/job_core_env_sched.run:# before the test let's throw some weird crap into the environment

condor_tests/job_core_env_sched.run:$ENV{"weirdchars"} = "

 

condor_tests/job_core_env_van.run:# before the test let's throw some weird crap into the environment

condor_tests/job_core_env_van.run:$ENV{"weirdchars"} = "

 

condor_tests/job_core_getenv_van.run:# before the test let's throw some weird crap into the environment

PuTTYPuTTYPuTTYcondor_tests/job_cp_cclim_acctgrp_basic_van.run:# currently (circa 8.1.1) there is some weird interaction between

condor_tests/job_filexfer_streamerr_van.run:# before the test let's throw some weird crap into the environment

condor_tests/job_filexfer_streamout_van.run:# before the test let's throw some weird crap into the environment

condor_tests/lib_procapi_pidtracking-byenv.run:# before the test let's throw some weird crap into the environment

condor_tools/store_cred_main.cpp:       // and write it to a file (in our weirdo XORed format)

condor_tools/tool.cpp:                                          // weird, malformed ad.

condor_tools/tool.cpp:                                          // weird, malformed ad.

condor_utils/check_events.cpp:                          // weird combo that *should* be illegal?

condor_utils/check_events.cpp:                          // weird combo that *should* be illegal?

condor_utils/condor_crontab.cpp:                                // The day of week specifier is kind of weird

condor_utils/directory.cpp:             // it failed b/c of weird permissions in the sandbox

condor_utils/dprintf_setup.cpp:                 // we don't really expect this to happen, but things get weird of

condor_utils/file_lock.cpp:// not the same (in some very inconsistent and weird ways) as the fseek one,

condor_utils/iso_dates.h: *        which has the usual weirdness: the year is off by 1900, etc.

condor_utils/printf_format.cpp:                 /* Some weird special cases mentioned in the man page */

condor_utils/test_old_classads.cpp:                     printf("Failed: Evaluating int(weirdstring)  gives: %d in line %d\n",

condor_utils/test_old_classads.cpp:                     printf("Passed: Evaluating int(weirdstring) gave %d in line %d\n",

condor_utils/test_old_classads.cpp:                     printf("Failed: Evaluating real(weirdstring)  gives: %f in line %d\n",

condor_utils/test_old_classads.cpp:                     printf("Passed: Evaluating real(weirdstring) gave %f in line %d\n",

safefile/configure:# symlink; some systems play weird games with the mod time of symlinks

 

condor-per:/home/samba/logs/condor-8.5.8/src #