X2381-Wheel Slip
#11
Posted 03 August 2014 - 11:38 AM
Usually, I do my tests on electric locomotives. And in this case, there were important differences in the other type of locomotives.
I will have to be more cautious in the future.
#12
Posted 03 August 2014 - 11:44 AM
Serana, on 03 August 2014 - 11:38 AM, said:
Usually, I do my tests on electric locomotives. And in this case, there were important differences in the other type of locomotives.
I will have to be more cautious in the future.
That is what dedicated testers are for. There are some of us about.
#13
Posted 03 August 2014 - 01:33 PM
Serana, on 03 August 2014 - 11:38 AM, said:
I don't think this is the response Copperpen might have been hoping for.
The way I see it, he is encouraging you not to do more testing yourself before you release but to recruit some testers to help you. Some of the Dev Team are not coders but testers and there are others not on the Dev Team who also help with testing.
Just my thoughts,
#14
Posted 03 August 2014 - 02:15 PM
Thank you.
#15
Posted 03 August 2014 - 04:26 PM
Thank you for your quick response to the problem, much appreciated.
cheers
#16
Posted 04 August 2014 - 02:56 AM
copperpen, on 03 August 2014 - 11:29 AM, said:
But as a defense to Serana, it must be taken into account that an svn commit is not a code "release" technically. That is just a commit subject to testing, what was done by you, and based on that the code was corrected eventually. So nothing happened that is against the regular workflow...
#18
Posted 04 August 2014 - 05:08 AM
#19
Posted 04 August 2014 - 06:49 AM
beresford, on 04 August 2014 - 05:08 AM, said:
Not something I have seen, but no, this was a problem introduced by some code changes in 2381, since rectified to stop that particular error.
Looking at the situation described, it is a valid message because too much dynamic brake can cause the engine wheels to skid instead of brake specially if the train brake is also in use without bailing the engine brakes off.
#20
Posted 04 August 2014 - 10:05 AM
gpz, on 04 August 2014 - 02:56 AM, said:
James is looking into an automatic procedure where a commit is not posted to the public until it's a week old. The idea is that we have a week to find and then either fix any show-stoppers or block that commit from reaching the website.
This procedure is described on the website as the Safe Update Setting but not yet in place.