There are some boilerplate instructions that are given at the beginning of every testnet. These are very helpful to me.
Suggestion:
Can you add the following to these instructions, as I find myself forgetting to do it.
I find myself with multiple node processes running when I forget to do this, which may effect things and cause me to report bugs that are my fault.
It’s debatable that such an easy mistake is your fault rather than a bug.
It would be helpful if the command to start a node checked if any nodes were already running and had a flag if you wanted it to skip that check.
Added the above to the OP in the meantime to help stop anyone else tripping up due to lingering processes.
I am still uploading large file to 7 IP address all with same speed at a same time.
3 times 46.101.xxx.xx
3 times 188.166.xxx.xx
1 time 139.59
Some of these are/were elders ?
dont seem to be able to get my logs to see if I’m on the network. I must be doing something wrong. Please advise 
The network is no longer up.
Looks like AE was just merged, what are the chances of 3 tests in one day?
You’re asking your command shell to execute the log. If you want to see what is in it insert more and a space before the path to the log.
Big night of testing ahead?
Big 
CONGRATULATIONS to @bochaco!
Well deserved. Always been great seeing your creative mind at work and your ability to jump into seemingly anything and completely own it. Thanks for being so technically supportive to the community you are very much still a big part of!
Oo I just checked the forum, from a few days off in countryside. I wish I could have joined the tests ! Next week
So nice to see the work is going on !
Is there a testnet today?
I don’t expect a testnet today, still analysing results from yesterday afternoon.
As Savage points out, we merged AE into node yesterday. It seems we’ve resolved all the major bugs there but we still expect a few minor one’s to show up. We’ve got it upstream so we can ramp up the internal testing there so we’ll see how that goes.
EDIT - just my own view of it at the moment, as more of the team come online during the day I’ll get a clearer view and post in the “Update from MaidSafe HQ” thread.
Thanks so much Stephen for all of the work you and the rest of the staff do!
In the future, could you put calendar dates instead of saying “this week” it’s a little less confusing for people who read it later. Also if the posts in the update category could do this too.
When we can expect new testnet release?
Congratulations @bochaco on your well deserved promotion! Thank you for your many contributions that have brought us to this point in the network’s development.
As soon as possible. Not looking like this week though.
Suits me - gives me more time to refine my deduplication analysis tool
It would help if I could get some confirmation that
getting a large no of measurements of the time taken to PUT and GET standard data of various sizes will actually be of some real use. And what the sizes of that data should be.
I’m thinking 10, 20 50 100 200 500kb and 1 2 5 10 20 50 Mb std data testfiles. Anybody got better ideas?
Anecdotally - cos Im not organised enough yet to collect the results in a csv, I see that -on baby-fleming locally at least - the original put is a reasonable time but the subsequent put where no actual data is being stored - network refuses to store an identical chunk takes roughly 30-50% longer. Further runs attempting to store the same chunks usually take slightly longer each time. But this is working with data from at most a couple of dozen runs.
It’s a bug we have introduced in recent Ae work. Guys on it now.
Indeed, as watching pushes on github, @bochaco is doing pretty hard core job there. It is very motivating for all of us.
