Systems and methods are described for analyzing and verifying distributed application programs. In one embodiment, an application program is divided into as one or more independently executable components. During execution of the independently executable components, non-deterministic events are modified in order to effectuate deterministic results. The non-deterministic events may be modified in accordance with a predetermined set of constraints.

According to one aspect of the present disclosure, a computer-implemented method is disclosed. From a plurality of data sources, software development data is obtained that relates to development of a software application and includes a time and description of multiple types of events that occurred during a predefined time period during development of the software application. A view selection of one of a plurality of views is received, wherein each view has a respective predefined timeline display template. The software development data is formatted according to the predefined timeline display template of the view selection to obtain a timeline of the software development data. The timeline of the software development data is displayed on an electronic display.

A system for equivalence class analysis-based automated requirements-based test case generation includes a control processor, a data store containing textual design requirements, a textual converter unit structured to convert the textual design requirements to a machine-readable version of design requirements, a requirement partition unit configured to partition the machine-readable design requirements into one or more sets of related design requirements, an equivalence class partition unit configured to process the machine-readable design requirements and input/output variables into a set of equivalence classes, an equivalence class analyzer unit structured to analyze the set of equivalence classes to generate equivalence class tests and identify uncovered input space, and a boundary class analyzer unit structured to identify boundaries of the equivalence classes and generate boundary value tests and robustness tests. A method for equivalence class analysis-based automated requirements-based test case generation implementable on the system, and a non-transitory computer readable medium are also disclosed.

Methods, systems, computer program products, and articles of manufacture for performing a query are described. Context information for formulating a query is obtained. The query is performed to identify a first card based on the context information, the query being performed by comparing the context information and an attribute of the first card, the attribute defining context of the first card. The identification of the first card that satisfies the query is provided.

Methods and system to calculate a total container cost of each container of a data center are described. Methods compute a direct container cost of each container running in the data center based on container resource utilization and a resource utilization rate of each resource of a host. Methods also compute an indirect container cost of each container is calculated as a sum of indirect cost of each resource of the host used by the container and each resource of the host used by a monitor container that monitors each container utilization of host resources. For each container, a total container cost of the container is calculated as the sum of the direct container cost and the indirect container cost of the container. Total container costs are used to determine the cost of applications miming on the containers.

Techniques to create and use cluster models to predict build failures are provided. In one aspect, clusters in a set of builds may be identified. The identified clusters may be used to create a model. The model may be used to predict causes of build failures. In another aspect, a failed build may be identified. A clustering model may be retrieved. A cause of problems with the failed build may be predicted using the clustering model.

Techniques to create and use cluster models to predict build failures are provided. In one aspect, clusters in a set of builds may be identified. The identified clusters may be used to create a model. The model may be used to predict causes of build failures. In another aspect, a failed build may be identified. A clustering model may be retrieved. A cause of problems with the failed build may be predicted using the clustering model.

A processor comprising an instruction execution circuit to execute a second code stored at a second address of a memory, wherein the second code is translated from a first code stored at a first address of the memory and a translation table (TT) controller coupled to a translation table to store a TT entry comprising a mapping between the first address and the second address and an attribute field comprising an attribute value associated with execution of the second code, wherein the TT controller is to monitor execution of the second code by the instruction execution circuit and update, based on a performance metric of the execution, the attribute value of the TT entry.

A processor comprising an instruction execution circuit to execute a second code stored at a second address of a memory, wherein the second code is translated from a first code stored at a first address of the memory and a translation table (TT) controller coupled to a translation table to store a TT entry comprising a mapping between the first address and the second address and an attribute field comprising an attribute value associated with execution of the second code, wherein the TT controller is to monitor execution of the second code by the instruction execution circuit and update, based on a performance metric of the execution, the attribute value of the TT entry.

A computer-implemented method for managing a release of a software product includes obtaining a request for the release, the request including workflow action parameter data to define a release pipeline involving a plurality of software engineering systems configured to process data indicative of the software product, and executing, with a processor, a workflow to implement the release pipeline in accordance with the workflow action parameter data. Executing the workflow includes sending a series of instructions to the plurality of software engineering systems. A successive instruction in the series of instructions is sent based on whether a gating rule for the release is met.