March 2014 - swift-bugs - mailman3.cels.anl.gov

[Bug 752] New: Coaster provider does not retry worker launches on qsub failures
by bugzilla-daemon＠mcs.anl.gov 18 Oct '14

18 Oct '14

https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=752 Summary: Coaster provider does not retry worker launches on qsub failures Product: Swift Version: 0.93 Platform: PC OS/Version: Mac OS Status: ASSIGNED Severity: normal Priority: P2 Component: Providers AssignedTo: hategan(a)mcs.anl.gov ReportedBy: wilde(a)mcs.anl.gov CC: hategan(a)mcs.anl.gov, davidk(a)ci.uchicago.edu, wozniak(a)mcs.anl.gov If a qsub to start a worker.pl job fails (in this case, due to the user having exceeded the maximum number of concurrently allowed job submissions, 32 on Eureka) then the coaster provider never tries again to start workers for those coaster slots. Hence, when the user is running multiple swift runs concurrently, and they fluctuate in the number of active workers, the swift run that encounters the worker failures stays forever at a very low active worker count. In the current situation, it stays so low (eg 1 worker out of an expected 32) that the run needs to be killed and restarted in order to get a sufficient number of workers. Logs are on eureka in /home/wilde/LZ/runNNN where NNN is between 020 and 058. -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 1

[Bug 722] New: fprintf presents hanging situation
by bugzilla-daemon＠mcs.anl.gov 18 Oct '14

18 Oct '14

https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=722 Summary: fprintf presents hanging situation Product: Swift Version: 0.93 Platform: PC OS/Version: Mac OS Status: NEW Severity: normal Priority: P2 Component: General AssignedTo: hategan(a)mcs.anl.gov ReportedBy: jonmon(a)utexas.edu CC: wilde(a)mcs.anl.gov If using %i and passing a float variable in the argument list, seems to have fprintf hang -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 2

[Bug 688] New: Testing env interactions
by bugzilla-daemon＠mcs.anl.gov 18 Oct '14

18 Oct '14

https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=688 Summary: Testing env interactions Product: Swift Version: trunk Platform: PC OS/Version: Mac OS Status: NEW Severity: normal Priority: P2 Component: Testing AssignedTo: jonmon(a)utexas.edu ReportedBy: jonmon(a)utexas.edu CC: wilde(a)mcs.anl.gov, skenny(a)uchicago.edu, davidk(a)ci.uchicago.edu, wozniak(a)mcs.anl.gov, ketan(a)mcs.anl.gov Testing and documenting interactions with setting environment variables using the env profile. Justin I believe had specific testing situation and questions. -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 1

[Bug 923] New: @toFloat() error gives no line number
by bugzilla-daemon＠mcs.anl.gov 12 Oct '14

12 Oct '14

https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=923 Summary: @toFloat() error gives no line number Product: Swift Version: 0.93 Platform: PC OS/Version: Mac OS Status: ASSIGNED Severity: minor Priority: P4 Component: Error messages AssignedTo: davidk(a)ci.uchicago.edu ReportedBy: wilde(a)mcs.anl.gov CC: wozniak(a)mcs.anl.gov In this expression, -startingjump was null, and the error message from @tofloat() gave no line number: (outfile,lossfile) = multi_annealing(best_filename, @tofloat(@arg("tstart", "2.0")), @tofloat(@arg("tend", "0.01")), @tofloat(@arg("trejection", "0.3")), @toint(@arg("evoreruns", "100")), @tofloat(@arg("startingjump", "2.3")), [ @tofloat(@arg("alphai", "0.0")), @tofloat(@arg("alpham", "0.0")), @tofloat(@arg("beta", "4.0")), @tofloat(@arg("gamma", "50.0")), @tofloat(@arg("delta", "-1.0")) ], @tofloat(target_innov), @toint(@arg("annealingcycles", "50")) ); } Need to see if this is still the case in 0.94. Log said: 2013-01-06 11:57:21,066-0600 INFO ExecutionContext Detailed exception: Could not convert value "" to type float at org.griphyn.vdl.karajan.lib.swiftscript.Misc.swiftscript_tofloat(Misc.java:318) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) stdout/err said: Swift 0.93 swift-r6113 (swift modified locally) cog-r3532 RunID: 20130106-1157-z0voc3r9 Progress: time: Sun, 06 Jan 2013 11:57:20 -0600 Execution failed: Could not convert value "" to type float -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 2

[Bug 919] New: Misleading error message when a structure type field is missing
by bugzilla-daemon＠mcs.anl.gov 12 Oct '14

12 Oct '14

https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=919 Summary: Misleading error message when a structure type field is missing Product: Swift Version: 0.94 Platform: PC OS/Version: Mac OS Status: ASSIGNED Severity: minor Priority: P2 Component: Error messages AssignedTo: davidk(a)ci.uchicago.edu ReportedBy: wilde(a)mcs.anl.gov CC: wozniak(a)mcs.anl.gov If an expression refers to a non-existent structure field, swift gives an error like: Compile error in assignment at line 134: Type Checkpoint is not defined. instead of: in expression ckpt.ref1: field ref1 of Type Checkpoint is not defined. -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 2

[Bug 1177] New: Coaster-C-Client automatic coasters [enhancement]
by bugzilla-daemon＠mcs.anl.gov 08 Sep '14

08 Sep '14

https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=1177 Summary: Coaster-C-Client automatic coasters [enhancement] Product: Swift Version: trunk Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: General AssignedTo: hategan(a)mcs.anl.gov ReportedBy: yadunandb(a)ci.uchicago.edu Splitting bug 1133, to move Automatic coasters as a separate enhancement request. Currently the Coaster-C-Client goes through a separately started persistent coaster service. This comes with a few limitations: 1. A persistent coaster service needs to be started separately. 2. Missing the key coaster feature of expanding and shrinking worker pool. 3. Coaster's and workers remain open after execution, which can be undesirable in some cases. These features would be needed for SwiftT to take full advantage of coasters and also for language unification in the future. Currently we use scripts to submit SwiftT to resources which is very clumsy compared to what coasters can do. -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 3

[Bug 907] New: Dangling coaster workers interfere with subsequent Swift runs
by bugzilla-daemon＠mcs.anl.gov 08 Sep '14

08 Sep '14

https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=907 Summary: Dangling coaster workers interfere with subsequent Swift runs Product: Swift Version: 0.94 Platform: PC OS/Version: Mac OS Status: ASSIGNED Severity: normal Priority: P2 Component: Providers AssignedTo: hategan(a)mcs.anl.gov ReportedBy: wilde(a)mcs.anl.gov CC: hategan(a)mcs.anl.gov, davidk(a)ci.uchicago.edu, wozniak(a)mcs.anl.gov Two problems here: - workers are not always cleaned up - such "dangling: workers interfere with subsequent runs Lorenzo has a log file (first message below) showing at least one manifestation of this problem. Second message indicates killing the abandoned workers solves the problems. Can we: - do a better job cleaning up abandoned workers? - make it so an abandoned worker cant connect to a subsequent server (or that if they do, no bad things, and only good things, happen?) --- ----- Forwarded Message ----- From: "Lorenzo Pesce" <lpesce(a)uchicago.edu> To: "Michael Wilde" <wilde(a)mcs.anl.gov> Sent: Saturday, December 15, 2012 12:43:06 PM Subject: 500 nodes failed again failed 500 node run: lpesce@login3:/lustre/beagle/GCNet/RG/Oreo/o080522_BS1> pwd /lustre/beagle/GCNet/RG/Oreo/o080522_BS1 -rw-rw-r-- 1 lpesce ci-users 549729889 2012-12-15 12:40 PackAndCausalTestCore_app-20121215-1801-2d9bnr57.log -rw-rw-r-- 1 lpesce ci-users 569522 2012-12-15 12:40 PackAndCausalTestCore_app.swift_2012-12-15_12:01:12_screen.log drwxrwxr-x 2 lpesce ci-users 4096 2012-12-15 12:40 PackAndCausalTestCore_app-20121215-1801-2d9bnr57.d In case you are interested in doing some post mortem. ----- Forwarded Message ----- From: "Lorenzo Pesce" <lpesce(a)uchicago.edu> To: "Michael Wilde" <wilde(a)mcs.anl.gov> Sent: Saturday, December 15, 2012 7:40:19 PM Subject: I know why it doesn't work sometimes I just realized that sometimes when swift gets killed or stops some jobs are left queued or running. These jobs create interference when the new jobs are sent. I tried a couple of times and if I clean up the queue, there seem to be no issues. I sent out a 500 nodes job and it has been happily churning for a while. -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 1

[Bug 871] New: Multiple client support for persistent coaster service
by bugzilla-daemon＠mcs.anl.gov 08 Sep '14

08 Sep '14

https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=871 Summary: Multiple client support for persistent coaster service Product: Swift Version: trunk Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: Medium Component: Providers AssignedTo: hategan(a)mcs.anl.gov ReportedBy: hategan(a)mcs.anl.gov CC: hategan(a)mcs.anl.gov, davidk(a)ci.uchicago.edu, wozniak(a)mcs.anl.gov A persistent coaster service should support multiple clients. There should be three modes of operation: 1. Manual workers - jobsPerNode (and possibly other relevant settings) should be specifiable either when the service is started or when the workers are started 2. Shared pool - clients would be able to re-use existing workers - all settings should be specified when starting the service and clients should not be able to override them 3. Per-client pool - each client will get its own pool of workers that is only used for one client connection - settings are specified by the client -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 2

[Bug 1223] New: Hang checker messages after task was completed
by bugzilla-daemon＠mcs.anl.gov 16 Aug '14

16 Aug '14

https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=1223 Summary: Hang checker messages after task was completed Product: Swift Version: 0.94 Platform: PC OS/Version: Mac OS Status: NEW Severity: normal Priority: P2 Component: General AssignedTo: hategan(a)mcs.anl.gov ReportedBy: davidk(a)ci.uchicago.edu I was just testing a simple script that runs hostname once and records the output to a file. The job was submitted to condor and ran, but the printed hang checker messages after it was finished. Log at http://web.ci.uchicago.edu/~davidk/logs/hostname-20140320-0141-8dscb5n4.log ... Final status: Thu, 20 Mar 2014 01:52:05 +0000 Finished successfully:1 No events in 10s. Finding dependency loops... Registered futures: Waiting threads: ---- No dependency loops found. Waiting JVM threads: Thread "Thread-12" (0x00000020) TIMED_WAITING Stack trace: java.lang.Thread.sleep org.globus.cog.abstraction.coaster.service.CoasterService$1.run:323 Thread "PullThread" (0x000000a5) TIMED_WAITING waiting for org.globus.cog.abstraction.coaster.service.job.manager.PullThread (0x4b8bbb61) Stack trace: java.lang.Object.wait org.globus.cog.abstraction.coaster.service.job.manager.PullThread.mwait:151 org.globus.cog.abstraction.coaster.service.job.manager.PullThread.run:122 Thread "Timer-3" (0x000000a3) TIMED_WAITING waiting for java.util.TaskQueue (0x2d9f90e3) Stack trace: java.lang.Object.wait java.util.TimerThread.mainLoop:531 java.util.TimerThread.run:484 Thread "Condor provider queue poller" (0x0000002a) TIMED_WAITING Stack trace: java.lang.Thread.sleep org.globus.cog.abstraction.impl.scheduler.common.AbstractQueuePoller.run:90 java.lang.Thread.run:679 Thread "Block Submitter" (0x00000028) WAITING waiting for java.util.LinkedList (0x46e13e7b) Stack trace: java.lang.Object.wait java.lang.Object.wait:502 org.globus.cog.abstraction.coaster.service.job.manager.BlockTaskSubmitter.run:56 Thread "Block Queue Processor" (0x00000027) TIMED_WAITING waiting for java.util.ArrayList (0x6dcd2197) Stack trace: java.lang.Object.wait org.globus.cog.abstraction.coaster.service.job.manager.BlockQueueProcessor.run:148 Thread "Timer-2" (0x00000026) WAITING waiting for java.util.TaskQueue (0x365878d2) Stack trace: java.lang.Object.wait java.lang.Object.wait:502 java.util.TimerThread.mainLoop:505 java.util.TimerThread.run:484 Thread "Piped Channel Sender" (0x00000025) WAITING waiting for java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject (0x6a643edd) Stack trace: sun.misc.Unsafe.park java.util.concurrent.locks.LockSupport.park:186 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await:2043 java.util.concurrent.LinkedBlockingQueue.take:386 org.globus.cog.karajan.workflow.service.channels.AbstractPipedChannel$Sender.run:113 Thread "Local Queue Processor" (0x00000023) WAITING waiting for java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject (0x29949f78) Stack trace: sun.misc.Unsafe.park java.util.concurrent.locks.LockSupport.park:186 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await:2043 java.util.concurrent.LinkedBlockingQueue.take:386 org.globus.cog.abstraction.coaster.service.job.manager.AbstractQueueProcessor.take:43 org.globus.cog.abstraction.coaster.service.job.manager.LocalQueueProcessor.run:37 Thread "Timer-1" (0x0000001f) WAITING waiting for java.util.TaskQueue (0x24d37b87) Stack trace: java.lang.Object.wait java.lang.Object.wait:502 java.util.TimerThread.mainLoop:505 java.util.TimerThread.run:484 Thread "Thread-10" (0x0000001e) TIMED_WAITING waiting for org.globus.cog.abstraction.coaster.service.CoasterService (0x3852eef4) Stack trace: java.lang.Object.wait org.globus.cog.abstraction.coaster.service.CoasterService.waitFor:251 org.globus.cog.abstraction.coaster.service.CoasterService.main:417 org.globus.cog.abstraction.impl.execution.coaster.ServiceManager$1.run:206 java.lang.Thread.run:679 Thread "NBS3" (0x00000017) WAITING waiting for java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject (0x2b302b69) Stack trace: sun.misc.Unsafe.park java.util.concurrent.locks.LockSupport.park:186 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await:2043 java.util.concurrent.LinkedBlockingQueue.take:386 java.util.concurrent.ThreadPoolExecutor.getTask:1069 java.util.concurrent.ThreadPoolExecutor.runWorker:1131 java.util.concurrent.ThreadPoolExecutor$Worker.run:615 java.lang.Thread.run:679 Thread "NBS2" (0x00000016) WAITING waiting for java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject (0x2b302b69) Stack trace: sun.misc.Unsafe.park java.util.concurrent.locks.LockSupport.park:186 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await:2043 java.util.concurrent.LinkedBlockingQueue.take:386 java.util.concurrent.ThreadPoolExecutor.getTask:1069 java.util.concurrent.ThreadPoolExecutor.runWorker:1131 java.util.concurrent.ThreadPoolExecutor$Worker.run:615 java.lang.Thread.run:679 Thread "NBS1" (0x00000015) WAITING waiting for java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject (0x2b302b69) Stack trace: sun.misc.Unsafe.park java.util.concurrent.locks.LockSupport.park:186 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await:2043 java.util.concurrent.LinkedBlockingQueue.take:386 java.util.concurrent.ThreadPoolExecutor.getTask:1069 java.util.concurrent.ThreadPoolExecutor.runWorker:1131 java.util.concurrent.ThreadPoolExecutor$Worker.run:615 java.lang.Thread.run:679 Thread "Scheduler" (0x00000010) TIMED_WAITING waiting for org.griphyn.vdl.karajan.VDSAdaptiveScheduler (0x6ac67a88) Stack trace: java.lang.Object.wait org.globus.cog.karajan.scheduler.LateBindingScheduler.sleep:303 org.globus.cog.karajan.scheduler.LateBindingScheduler.run:257 Thread "Progress ticker" (0x00000014) TIMED_WAITING Stack trace: java.lang.Thread.sleep org.griphyn.vdl.karajan.lib.RuntimeStats$ProgressTicker.run:183 Thread "Restart Log Sync" (0x00000012) WAITING waiting for org.globus.cog.karajan.workflow.nodes.restartLog.SyncThread (0x677210a5) Stack trace: java.lang.Object.wait java.lang.Object.wait:502 org.globus.cog.karajan.workflow.nodes.restartLog.SyncThread.run:47 Thread "Overloaded Host Monitor" (0x00000011) TIMED_WAITING Stack trace: java.lang.Thread.sleep org.globus.cog.karajan.scheduler.OverloadedHostMonitor.run:47 Thread "Timer-0" (0x0000000f) TIMED_WAITING waiting for java.util.TaskQueue (0x71a2f5b1) Stack trace: java.lang.Object.wait java.util.TimerThread.mainLoop:531 java.util.TimerThread.run:484 Thread "NBS0" (0x0000000e) WAITING waiting for java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject (0x2b302b69) Stack trace: sun.misc.Unsafe.park java.util.concurrent.locks.LockSupport.park:186 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await:2043 java.util.concurrent.LinkedBlockingQueue.take:386 java.util.concurrent.ThreadPoolExecutor.getTask:1069 java.util.concurrent.ThreadPoolExecutor.runWorker:1131 java.util.concurrent.ThreadPoolExecutor$Worker.run:615 java.lang.Thread.run:679 Thread "pool-1-thread-4" (0x0000000d) WAITING waiting for java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject (0x01b071c0) Stack trace: sun.misc.Unsafe.park java.util.concurrent.locks.LockSupport.park:186 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await:2043 java.util.concurrent.LinkedBlockingQueue.take:386 java.util.concurrent.ThreadPoolExecutor.getTask:1069 java.util.concurrent.ThreadPoolExecutor.runWorker:1131 java.util.concurrent.ThreadPoolExecutor$Worker.run:615 java.lang.Thread.run:679 Thread "pool-1-thread-3" (0x0000000c) WAITING waiting for java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject (0x01b071c0) Stack trace: sun.misc.Unsafe.park java.util.concurrent.locks.LockSupport.park:186 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await:2043 java.util.concurrent.LinkedBlockingQueue.take:386 java.util.concurrent.ThreadPoolExecutor.getTask:1069 java.util.concurrent.ThreadPoolExecutor.runWorker:1131 java.util.concurrent.ThreadPoolExecutor$Worker.run:615 java.lang.Thread.run:679 Thread "pool-1-thread-2" (0x0000000b) WAITING waiting for java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject (0x01b071c0) Stack trace: sun.misc.Unsafe.park java.util.concurrent.locks.LockSupport.park:186 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await:2043 java.util.concurrent.LinkedBlockingQueue.take:386 java.util.concurrent.ThreadPoolExecutor.getTask:1069 java.util.concurrent.ThreadPoolExecutor.runWorker:1131 java.util.concurrent.ThreadPoolExecutor$Worker.run:615 java.lang.Thread.run:679 Thread "pool-1-thread-1" (0x0000000a) WAITING waiting for java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject (0x01b071c0) Stack trace: sun.misc.Unsafe.park java.util.concurrent.locks.LockSupport.park:186 java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await:2043 java.util.concurrent.LinkedBlockingQueue.take:386 java.util.concurrent.ThreadPoolExecutor.getTask:1069 java.util.concurrent.ThreadPoolExecutor.runWorker:1131 java.util.concurrent.ThreadPoolExecutor$Worker.run:615 java.lang.Thread.run:679 Thread "AsyncAppender-Dispatcher-Thread-0" (0x00000008) WAITING waiting for java.util.ArrayList (0x66fbf51d) Stack trace: java.lang.Object.wait java.lang.Object.wait:502 org.apache.log4j.AsyncAppender$Dispatcher.run:548 java.lang.Thread.run:679 Thread "Finalizer" (0x00000003) WAITING waiting for java.lang.ref.ReferenceQueue$Lock (0x279977bd) Stack trace: java.lang.Object.wait java.lang.ref.ReferenceQueue.remove:133 java.lang.ref.ReferenceQueue.remove:149 java.lang.ref.Finalizer$FinalizerThread.run:189 Thread "Reference Handler" (0x00000002) WAITING waiting for java.lang.ref.Reference$Lock (0x4c842d9a) Stack trace: java.lang.Object.wait java.lang.Object.wait:502 java.lang.ref.Reference$ReferenceHandler.run:133 Thread "main" (0x00000001) WAITING waiting for org.globus.cog.abstraction.coaster.service.CoasterService$1 (0x5b6b9e62) Monitors held: java.lang.Class (0x79ce00b4) Stack trace: java.lang.Object.wait java.lang.Thread.join:1203 java.lang.Thread.join:1256 java.lang.ApplicationShutdownHooks.run:97 java.lang.Shutdown.runHooks:106 java.lang.Shutdown.sequence:150 java.lang.Shutdown.exit:195 -> locked java.lang.Class (0x79ce00b4) java.lang.Runtime.exit:107 java.lang.System.exit:923 org.griphyn.vdl.karajan.Loader.main:247 -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 3

[Bug 1173] New: Space at end of tc.data causes failure
by bugzilla-daemon＠mcs.anl.gov 12 Jul '14

12 Jul '14

https://bugzilla.mcs.anl.gov/swift/show_bug.cgi?id=1173 Summary: Space at end of tc.data causes failure Product: Swift Version: trunk Platform: PC OS/Version: Mac OS Status: NEW Severity: minor Priority: P2 Component: General AssignedTo: hategan(a)mcs.anl.gov ReportedBy: davidk(a)ci.uchicago.edu When a tc.data file has the line: "local-coasters sleep /bin/sleep " (with a space at the end) it fails with this error: On line 1in File tc.data java.lang.IllegalStateException: Error : Illegal TCType defined. Please specify one of the predefined types [INSTALLED, SOURCE, STATIC_BINARY, DYNAMIC_BINARY, PACMAN_PACKAGE, SCRIPT] at org.globus.swift.catalog.types.TCType.fromValue(TCType.java:73) at org.globus.swift.catalog.types.TCType.fromString(TCType.java:85) at org.globus.swift.catalog.transformation.File.populateTC(File.java:1073) at org.globus.swift.catalog.transformation.File.populateTC(File.java:1022) at org.globus.swift.catalog.transformation.File.<init>(File.java:143) at org.globus.swift.catalog.transformation.File.getNonSingletonInstance(File.java:110) at org.griphyn.vdl.karajan.VDSAdaptiveScheduler.setProperty(VDSAdaptiveScheduler.java:100) at org.globus.cog.karajan.compiled.nodes.grid.SchedulerNode.newScheduler(SchedulerNode.java:128) at org.globus.cog.karajan.compiled.nodes.grid.SchedulerNode.runBody(SchedulerNode.java:91) at org.globus.cog.karajan.compiled.nodes.InternalFunction.run(InternalFunction.java:153) at org.globus.cog.karajan.compiled.nodes.CompoundNode.runChild(CompoundNode.java:87) at org.globus.cog.karajan.compiled.nodes.FramedInternalFunction.run(FramedInternalFunction.java:63) at org.globus.cog.karajan.compiled.nodes.Import.runBody(Import.java:269) at org.globus.cog.karajan.compiled.nodes.InternalFunction.run(InternalFunction.java:153) at org.globus.cog.karajan.compiled.nodes.CompoundNode.runChild(CompoundNode.java:87) at org.globus.cog.karajan.compiled.nodes.FramedInternalFunction.run(FramedInternalFunction.java:63) at org.globus.cog.karajan.compiled.nodes.Main.run(Main.java:79) at k.thr.LWThread.run(LWThread.java:228) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:744) -- Configure bugmail: https://bugzilla.mcs.anl.gov/swift/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 4