[
https://issues.apache.org/jira/browse/MAHOUT-743?focusedWorklogId=1000693&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1000693
]
ASF GitHub Bot logged work on MAHOUT-743:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 18/Jan/26 07:21
Start Date: 18/Jan/26 07:21
Worklog Time Spent: 10m
Work Description: Rutuja123-dos commented on PR #844:
URL: https://github.com/apache/mahout/pull/844#issuecomment-3765007536
Closing this for now. I've realized my local build environment is a bit too
limited for these GPU/Rust changes and it's becoming a major blocker. I’m going
to step back from this one and look for some other areas to contribute instead.
Thanks for the help
Issue Time Tracking
-------------------
Worklog Id: (was: 1000693)
Time Spent: 1h 50m (was: 1h 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: 1h 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)
