Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 61
Posts: 61   Pages: 7   [ Previous Page | 1 2 3 4 5 6 7 ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 272168 times and has 60 replies Next Thread
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: C4CW Target 07 Beta Test (Issues Thread)

I have had "beta" in app_config before I received beta works and I am still receiving the same message.

Yesterday I checked client_state file and found out, that the recent beta's name was "beta12". So I kept "beta" in app_config and added "beta12", "beta13" and "beta14" (for check purposes - in case my logic is correct, next beta work could be "beta13"). Now I am receiving messages saying

app beta not found in app_config.xml
app beta13 not found in app_config.xml
app beta14 not found in app_config.xml


Cheers

For good order, the red-liners are because the application cannot be found in the project folder [just as the error says]. If you wish to anticipate an app that does not exist, than that's a user caused [non-critical] error, more of a warning. You'll have to do the maintenance if you wish to minimize these alerts, or just ignore them.

As noted before, if you wish to max out on CPU for beta's you don't need to specify anything in app_config.xml. If you wish to run more than 1 beta concurrent on a GPU, then you'll have to.
[Mar 1, 2013 5:19:41 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 61   Pages: 7   [ Previous Page | 1 2 3 4 5 6 7 ]
[ Jump to Last Post ]
Post new Thread