Welcome!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

Sign up now!

Resolved Cannot Push SVN Update to Queue

Joined
Aug 23, 2015
Messages
1,970
When I hit "Push bot update to queue" the message "Your push request has been received and is being processed. You will receive further information via forum private message." pops up. After this, I never get a PM from Cloud, and the "Queued Revision" stays as "N/A"

Ive tried pushing from chrome, firefox, and mobile, other people are still able to push. I tried changing something pointless in my bot and re-uploading and pushing, and am still unable to push.

My SVN does have the most recent uploaded stuff inside of it.

The most recent time i got a response from pushing was at 11:08pm est on the 3rd, when the push was rejected because i forgot to remove 2 files from svn and the svn version didn't compile. After this I pushed to remove the files, and have been unable to push to queue since.
 
12 year old normie
Joined
Jan 8, 2015
Messages
2,769
Unfortunately, none of your bots have advanced to the next stage of review. Before you consider pushing another update, please review the following suggestions, warnings, and/or errors.
  • The Bot Pusher looked through your svn repository and wasn't able to find any bots. If you committed your code correctly than this is most likely caused by either a missing or invalid manifest. It's also common to see this occur when code has been packaged into multiple modules because it's unable to resolve a single source root.

This message has been automatically generated by RuneMate's Bot Pusher. If this was the result of a mistake or misclick on your part, please do not feel the need to respond/apologize. If you have any questions or concerns, just respond to this message and an Executive will review your comment shortly. Happy botting!

I DO get a message, but the end-result is the same. I've double-checked if the content is in the SVN, which it is. Making a byte-code change doesn't work either. The queue revision number stays at N/A.
 
Top