As some of you may have already noticed, I released a small number of test workunits. These workunits are used to test various parts of the server software:

- validator/assimilator: checking if the server can support multiple ciphertexts and/or multiple dictionaries at once. It was designed that way, but some of the functionality was left (almost) unused, and the code has been rewritten at least 3 times (not counting minor fixes), so probably there are bugs waiting to be found.

- the backend used to add new data sets - really needs improvement, right now almost everything has to be added manually.

- the daemon used to add 'local' workunits needs testing/fixing a lot of things.

- the script that assigns fixed credits for workunits needs more data (runtime averages), so probably I'll release a small number of tasks with various ciphertext lenghts to gather some data.

Using a dummy text to do the testing would be a waste of CPU time, so I think I'll pick one of the unbroken M3 messages from the Frode Weierud's CryptoCellar to run additional tests. Any suggestions ? :-D

---

M4 Project homepage
M4 Project wiki

Do we get those test WU´s automatically? Haven´t seen the option to choose to run test WU´s in my preferences.

Thanks

Is the WU "dthyh80" one of the test WUs?

Have I cracked the chipertext?

By, Grubix.


PS: I'm using the "pentium3_sse2" optimized app. See this Thread.

There is only one app available, so the test workunits are ąutomatically assigned to it. There is no need to change anything. Also any optimized app should be compatible - if it works with awgly workunits, it will work with all the others.

---

M4 Project homepage
M4 Project wiki