List Info

Thread: Rake Abort When Attempting to Sync an Uptodate Depot




Rake Abort When Attempting to Sync an Uptodate Depot
user name
2006-03-10 20:40:09
We're having problems performing a sync when the depot
is already up to date.  Here's the stacktrace that we
got when the rakefile checkout task attempted to sync
an already current depot:

[exec] ** Invoke checkout (first_time)
[exec] ** Execute checkout
[exec] rake aborted!
[exec] [P4#run] Warnings during command execution( "p4
sync" )
[exec]     [Warning]: File(s) up-to-date.
[exec] c:/ruby/lib/ruby/1.8/P4.rb:131:in `run'
[exec] c:/ruby/lib/ruby/1.8/P4.rb:131:in
`method_missing'
[exec] ../ruby-lib/perforce_transactions.rb:35:in
`sync'
[exec] C:/NGST/app/java/rakefile:101
[exec] C:/NGST/app/java/rakefile:98:in `call'
[exec]
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.0/lib/rake.rb:232:in
`execute'
[exec]
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.0/lib/rake.rb:232:in
`each'
[exec]
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.0/lib/rake.rb:232:in
`execute'
[exec]
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.0/lib/rake.rb:202:in
`invoke'
[exec]
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.0/lib/rake.rb:195:in
`synchronize'
[exec]
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.0/lib/rake.rb:195:in
`invoke'
[exec]
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.0/lib/rake.rb:1719:i
n
`run'
[exec]
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.0/lib/rake.rb:1719:i
n
`each'
[exec]
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.0/lib/rake.rb:1719:i
n
`run'
[exec]
c:/ruby/lib/ruby/gems/1.8/gems/rake-0.7.0/bin/rake:7
[exec] c:/ruby/bin/rake:18:in `load'
[exec] c:/ruby/bin/rake
[exec] c:/ruby/bin/rake:18

Anybody seen this before?  Suggestions?  Thanks much
in advance.

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection
around 
http://mail.yahoo.com 
_______________________________________________
p4ruby mailing list
p4rubyperforce.com

http://maillist.perforce.com/mailman/listinfo/p4ruby
Rake Abort When Attempting to Sync an Uptodate Depot
user name
2006-03-11 12:31:21
Hi Jim,

Jim Mitchell wrote:
> We're having problems performing a sync when the depot
> is already up to date.  Here's the stacktrace that we
> got when the rakefile checkout task attempted to sync
> an already current depot:
> 
> [exec] ** Invoke checkout (first_time)
> [exec] ** Execute checkout
> [exec] rake aborted!
> [exec] [P4#run] Warnings during command execution(
"p4
> sync" )
> [exec]     [Warning]: File(s) up-to-date.
> [exec] c:/ruby/lib/ruby/1.8/P4.rb:131:in `run'
> [exec] c:/ruby/lib/ruby/1.8/P4.rb:131:in
> `method_missing'

You're using exception level RAISE_ALL (the default) in
which exceptions
are raised on warnings as well as errors. The 'file(s)
up-to-date'
message is a warning.

To avoid this, either switch to exception level RAISE_ERRORS
globally or
just for the sync.:

(a)

	p4.exception_level = P4::RAISE_ERRORS
	p4.run_sync

(b)
	p4.at_exception_level( P4::RAISE_ERRORS ) do
		p4.run_sync
	end

Hope that helps!

Tony
_______________________________________________
p4ruby mailing list
p4rubyperforce.com

http://maillist.perforce.com/mailman/listinfo/p4ruby
[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )