[
https://issues.apache.org/jira/browse/MAHOUT-743?focusedWorklogId=1000413&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1000413
]
ASF GitHub Bot logged work on MAHOUT-743:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Jan/26 08:29
Start Date: 16/Jan/26 08:29
Worklog Time Spent: 10m
Work Description: Rutuja123-dos commented on PR #773:
URL: https://github.com/apache/mahout/pull/773#issuecomment-3758750048
Hi @ryankert01, apologies for the delay! I was busy with my university
semester exams over the last two weeks, so I couldn't get to this sooner.
I am back now and will be working on cleaning up the PR to remove the
unrelated commits and focus strictly on MAHOUT-743. I’ll have the updated,
clean version pushed by tomorrow. Thanks for your patience
Issue Time Tracking
-------------------
Worklog Id: (was: 1000413)
Time Spent: 50m (was: 40m)
> Allow use of random seeds during unit tests
> -------------------------------------------
>
> Key: MAHOUT-743
> URL: https://issues.apache.org/jira/browse/MAHOUT-743
> Project: Mahout
> Issue Type: Improvement
> Reporter: Lance Norskog
> Assignee: Sean R. Owen
> Priority: Major
> Fix For: 0.6
>
> Attachments: MAHOUT-743.patch, RandomWrapper.patch
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> The RandomUtils package has a trick for running unit tests repeatably. All
> random generators created with RandomUtils.getRandom() are started with seed
> 0. Unfortunately, all random generators started with
> RandomUtils.getRandom(seed) effectively run from a seed of 0. Thus, code
> which deliberately creates Random objects with seeds does not work correctly
> under unit tests.
> The problem is that the logic in RandomWrapper tests for unit test mode and
> settable seed mode in the wrong order.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
