Abstract: A method and apparatus that schedules and manages a background task for device is described. In an exemplary embodiment, the device registers the background task, where the registering includes storing execution criteria for the background task. The execution criteria indicates a criterion for launching the background task and the execution criteria based on a component status of the device. The device further monitors the running state of the device for an occurrence of the execution criteria. If the execution criteria occurs, the device determines an available headroom with the device in order to perform the background task and launches the background task if the background task importance is greater than the available device headroom, where the background task importance is a measure of how important it is for the device to run the background task.

Abstract: A method for generating a program to run on multiple tiles. The method comprises: receiving an input graph comprising data nodes, compute vertices and edges; receiving an initial tile-mapping specifying which data nodes and vertices are allocated to which tile; and determining a subgraph of the input graph that meets one or more heuristic rules. The rules comprises: the subgraph comprises at least one data node, the subgraph spans no more than a threshold number of tiles in the initial tile-mapping, and the subgraph comprises at least a minimum number of edges outputting to one or more vertices on one or more other tiles. The method further comprises adapting the initial mapping to migrate the data nodes and any vertices of the determined subgraph to said one or more other tiles.

Abstract: Systems, methods and computer program products are described herein that can be used to help achieve a safe rollout of software in a production datacenter environment. In accordance with certain embodiments, cloud services requests from certain users of a cloud services system (e.g., users that are authorized to receive cloud services via computing devices running test versions of infrastructure software) are dynamically matched to clusters (groups of commonly-managed computing devices called nodes) that are capable of providing the requested services on nodes running test versions of infrastructure software. Within such clusters, the requested services are provided to the users on a subset of cluster nodes that run a test version of an infrastructure software component, while the remaining cluster nodes are not running the particular test version.

Abstract: A test management system utilizes an adaptive cohort selection technique to dynamically select and update a cohort of clients for testing a feature of a computer security application. The test management system selects an initial cohort based on high level parameters of the test including the feature to be evaluated and the statistical confidence level for the outcome. During the test, the test management system obtains real-time telemetry data relevant to evaluating the test. Depending on how the test is tracking relative to the test objectives, test management system may dynamically modify the cohort by expanding the size of the cohort or changing the cohort membership.

Abstract: A testing system and application performs validation testing on a media services delivery system by generating test transactions and validating test results at a plurality of support systems updated by the test transactions in a test environment. Support systems are independent systems that may be geographically and network distant, thus are cumbersome to access for validating corresponding updates based on a test transaction. The test system is accessible via an Internet or network portal for accessing an application that generates a test transaction, invokes a system under test for implementing the test transaction, and validates the results of the support system updates with known values for successful test completion. The test system automates the identification, retrieval and comparison of test generated values with known values corresponding to a successful transaction, and is operable to perform a suite of tests in succession from a set of predetermined test transactions and corresponding known values.

Abstract: A test case generation apparatus (10) analyzes test target software that is software to execute the process of one step for each input of a value, thereby generating, as a test case, a sequence of values that are input for a test of the software. In that case, an equivalent step checking unit (19) determines that when the value of a state variable after execution of one of a plurality of steps that share the state variable and the value of the state variable after execution of a different step are equal with respect to the state variable, those two steps are equivalent steps. A test case generation unit (20) analyzes the test target software, excluding one of the two steps determined to be the equivalent step by the equivalent step checking unit (19), thereby generating the value to be included in the test case.

Abstract: Provided is a system and method for generating an internal automated test for testing a software application. In one example, the method may include one or more of storing, via an application persistency, a plurality of application events that occur during a reference execution of an application, retrieving the plurality of application events of the reference execution of the application and timestamps indicating respective times when the plurality of application events occurred, from the application persistency, and in response to receiving a request to test the application, executing a recreation of the plurality of application events in an order based on the timestamps to perform an automated test of the application.

Abstract: The present disclosure pertains to automated software setup. In one embodiment, a first set of entity descriptors associated with a first entity is obtained. Similar entities to the first entity are determined by comparing the first set of entity descriptors to each of a plurality of sets of entity descriptors, each associated with a particular entity that previously setup the software. The percentage of the similar entities that selected a particular software functionality requirement is determined and a set of software functionality requirements for the first entity is determined based on the percentages. A user interface is provided for selecting the plurality of possible software functionality requirements and the first set of software functionality requirements are pre-selected in the user interface. Accordingly, software setup for a new entity is automated based on the software setup selections of similar entities.

Abstract: A computer-implemented method includes identifying a bad fix to a software product, where the software product includes a plurality of parts, and where the bad fix presents an error into a first part. A plurality of fixes to the software product, including the bad fix, are representable by a dependency graph indicating dependencies among the plurality of fixes. The dependency graph is recursively traversed to identify a subset of fixes that are dependent on the bad fix, where each fix in the subset of fixes includes a respective set of parts, and to add a reference to a respective most recent version of each part of each fix in the subset of fixes to a parts datastore. A remedial part and each part referenced in the parts datastore are packaged into a remedial fix, where the remedial part includes a correction to the error in the first part.

Abstract: The present disclosure provides a blockchain-based data processing method, device, and an electronic device thereof. The method includes the steps of acquiring a first block in a blockchain at a current node; broadcasting a first transaction to other nodes in the blockchain, wherein data related to the first transaction includes a model parameter; and creating a second block based on the model parameter and adding the second block into the blockchain in response to two or more second transactions corresponding to the first transaction, wherein data related to the second transactions include voting results corresponding to the first transaction.

Abstract: Software lifecycle management includes, searching, using a processor, historical development data including prior development tasks for a software system. The searching is performed according to a current development task for the software system. A determination is made as to whether the current development task has an affinity with a selected prior development task implemented within the software system. A recommendation is provided for the current development task based upon the selected prior development task.

Abstract: Methods, systems, and devices supporting joint code validation across code repositories are described. Some systems may store code across multiple code repositories, where the code repositories support repository-specific pull requests and validations. However, code stored in one repository may depend on code stored in a different repository. To accurately validate changes to such code, a system may identify a validation trigger for a first pull request (e.g., indicating one or more code changes to a first code repository), determine a second code repository or second pull request related to the first pull request, and generate a test build across the code repositories. For example, the test build may include code updates in the first code repository according to the first pull request and code from the second code repository (e.g., updated according to the second pull request). The system may perform joint validation tests on the test build.

Abstract: Software lifecycle management includes, searching, using a processor, historical development data including prior development tasks for a software system. The searching is performed according to a current development task for the software system. A determination is made as to whether the current development task has an affinity with a selected prior development task implemented within the software system. A recommendation is provided for the current development task based upon the selected prior development task.

Abstract: This disclosure relates generally to field of elimination of false positives during static analysis of an application code, and, more particularly, to a method and a system for identification and elimination of false positives from delta alarms. Existing static analysis tools report/generate numerous static alarms for a version and the same static alarm also gets reported for the subsequent versions, which are referred to as repeated alarms, while static alarms remaining after the suppression of the repeated alarms, are called delta alarms. In an embodiment, the disclosed method and system for identification and elimination of false positives from delta alarms, wherein the delta alarms are post-processed to identify of a set of false positives using a version aware static analysis technique based on a set of reuse computation techniques implementing conservative or an aggressive approach based on a dynamic configuration input.

Abstract: A method for executing a virtualized application on a computing system that includes a user-space and a kernel-space is disclosed. The method includes executing an application in the user-space, executing a user-level virtualization layer in the user-space, the user-level virtualization layer including a set of rules, performing, via the user-level virtualization layer, user-level hooking of events that are generated by the executing application according to the set of rules to identify events of interest, and determining whether to allow or block a function corresponding to an event that is identified as an event of interest based on the set of rules in the user-level virtualization layer.

Abstract: A data processing system includes a host device and a memory system including a controller and a memory device. The controller receives a command for the memory device from the host device, determines whether at least one slowdown event occurs due to an internal operation, and when it is determined that the slowdown event occurs, notifies the host device of occurrence of the slowdown event.

Abstract: Direct access to host memory for guests is disclosed. For example, a system includes a processor, a host memory, a filesystem daemon, a guest including a storage controller, and a filesystem queue accessible to the filesystem daemon and the storage controller. The storage controller receives a file retrieval request associated with a file stored in the host memory and forwards the file retrieval request to the filesystem daemon by adding the file retrieval request to the filesystem queue. The filesystem daemon retrieves the file retrieval request from the filesystem queue, determines a host memory address (HMA) associated with the file, and causes the HMA to be mapped to a guest memory address (GMA). The guest accesses the file in the host memory with the GMA, and later terminates access to the file, where the filesystem daemon is then configured cause the GMA to be unmapped.

Abstract: A function management method applied to a memory device includes obtaining a plurality of functions through a map file of a compiler, and parsing at least one source code of the memory device with the map file. The functions include at least one normal function and at least one API function. The parsing includes developing a mapping relationship between the at least one API function and the at least one normal function, and developing a calling relationship between the at least one normal function.

Abstract: A test suite is executed to test a computer program for a plurality of variables. A variable value is generated for each variable of the plurality of variables at a predetermined location of the computer program. Whether a test included in the test suite is successful is determined. If the test is successful, the variable value is recorded as part of a success value set. If the test is not successful, the variable value is recorded as part of a failure value set. A confidence metric is calculated for the variable value. A relevance metric for each variable of the plurality of variables is measured, based on a Jaccard distance between the success value set and the failure value set. The failure value set, the success value set, the confidence metric for the variable value, and the relevance metric for each variable of the plurality of variables are presented.

Abstract: A test suite is executed to test a computer program for a plurality of variables. A variable value is generated for each variable of the plurality of variables at a predetermined location of the computer program. Whether a test included in the test suite is successful is determined. If the test is successful, the variable value is recorded as part of a success value set. If the test is not successful, the variable value is recorded as part of a failure value set. A confidence metric is calculated for the variable value. A relevance metric for each variable of the plurality of variables is measured, based on a Jaccard distance between the success value set and the failure value set. The failure value set, the success value set, the confidence metric for the variable value, and the relevance metric for each variable of the plurality of variables are presented.