It is perhaps too much to go into. I should not have mentioned multirust or LOG etc. you should forget I did as it’s many lines to type and your questions mean you will have a a ton of hurt doing any of these things. You would need to know is rust working (can you run other crates), do you have nightly (is it latest) etc. then your script will work.
After that then play around with multirust and log on their own and understand them or don’t use them is really the best advice. You don’t need them it’s fine without, they just make your life much simpler.
Pulling the tip of tree in github is not always going to be great, it’s like diving into the deep end of a pool and asking how to swim. So you are brave, but it’s not easy to explain every line and tool, I hope you see my point. I love the fact you are helping, but perhaps let our CI tests do the job automatically and we will all move faster then.
We are very close to you having API’s etc. and there is where you want to be digging like mad.
That response is a bit condescending. This should be straightforward - there is some code, it gets compiled, the executable is tested against standard tests. I have been doing that sort of thing for more than 30 years . . if I can’t get it working then I suggest I am not getting enough useful information to find out where the problem(s) are . . Now maybe this stuff is SO new and it changes SO fast and your people are SO busy that none of you can document SIMPLE things properly - if that is really the case, then fine, I will give up until the installers are available . . but that is not my inclination . .
That is not the intention and it really is that easy and straightforward. However, I don’t know your OS, version, kernel version, cpu size, cpu type, terminal type, rust version etc. If you could not compile only a single library or all libraries, only maidsafe libraries or any rust library, it’s a lot of things to work though line by line.
I think you are on linux so /var/log/syslog|messages will help, strace a program you run and logging will also help, I am trying to save you going down a hole you are not comfortable with and your questions suggest you are not comfortable there. That’s all.
There is no intention to be condescending, but it’s a huge ask sometimes. I don’t even know what your script does and then if you post it if you want me to fix it etc. I am saying the CI scripts and machines run automatically with every commit and it seems you are trying to emulate that but it’s not working. It would be great to know if there is a particular OS combination that does not work, but also more info on what is wrong and is it specific to our libs or not.
So don’t take it personally and certainly not as an insult, but I do think you are asking something pretty hard to decipher. I doubt there is any program you can run on any machine under any circumstances, so we do need more info to solve the issue, but also we need to get launched and work on the proper installer versions to, so need to balance how much time we can spend on taking folk through very specific configurations blindly. It’s not easy trying to please everyone, I try but cannot no matter how I try, the clock hands keep going round and work needs done.
I just feel getting the API to folks is a huge deliverable we must make and make it asap. All help is great, but we do need info to resolve issues and also balance with getting launched, so forgive any shortness in answers.
These are still work in progress. Once everything is stable and tested, the source would be merged under the maidsafe repositories. The documentation on how to use them would be minimal right now, it would be explained better once complete.
So the only differences between what you do above and what I have been doing recently is:
that you are running curl without sudo (I run exactly what you do as root)
Prior to the change to rust, I used to always do a fresh glt clone because a “git pull” never worked properly, but since the change to rust and with some recent advice from the forum to try and resolve problems, I have been doing: cd crust ; git pull ; cargo clean ; cargo update ; cargo build ; export RUST_TEST_THREADS=1 ; cargo test
I repeated what I usually do - same error as before:
running 20 tests
test beacon::test::test_avoid_beacon … thread ‘test_avoid_beacon seek_peers 2’ panicked at ‘index out of bounds: the len is 0 but the index is 0’, …/src/libcollections/vec.rs:1047
I then renamed the crust dir (for a later comparison), did exactly what you do (except for running curl as root) and again, got exactly the same error . .
For the record (it appears that I should be saying this every time - despite my numerous posts on the Fedora x86_64 testing thread) - I am running Fedora x86_64.
Can you do this again on an another computer or VM to replicate this problem. I finally was able to build it on my side (Not the problem of course).
MY RESULT:
running 20 tests
test bootstrap_handler::test::serialisation … ok
test config_utils::test::read_config_file_test … FAILED
test bootstrap_handler::test::prune … FAILED
test bootstrap_handler::test::duplicates … FAILED
test bootstrap_handler::test::oldest … FAILED
test connection_manager::test::bootstrap_off_list_connects … ok
test connection_manager::test::network … ignored
test getifaddrs::test::test_filter_loopback … ok
test getifaddrs::test::test_getifaddrs … ok
test tcp_connections::test::test_multiple_nodes_small_stream … ok
test tcp_connections::test::test_small_stream … ok
test test::check_rust_unit_testing_is_not_parallel … FAILED
test transport::test::test_ord … ok
test beacon::test::test_beacon … ok
test bootstrap_handler::test::max_contacts … ok
test connection_manager::test::bootstrap_off_list_connects_multiple … ok
test beacon::test::test_avoid_beacon … ok
test connection_manager::test::bootstrap … ok
test connection_manager::test::connection_manager … ok
test connection_manager::test::connection_manager_start … ok
That’s with my all core. I did not do RUST_TEST_THREADS=1
@Maidsafe Thanks for updates Love the progress made so far. @dirvine It could by argued that this year things are moving faster than the previous ones @Krishna_Kumar thanks for point out the source for app.
Hi @philip_rhoades thanks for the update. Could you please raise this as a bug in the crust github issues? With as much info as you can about your env would help us replicate and work this issue - OS, machine spec, rust version, scripts used, output, etc. Thank you, hopefully together we can identify and resolve this. Cheers - capturing these bugs and resolving is essential.
