A mainframe deployment device for deploying code to a mainframe device in a stable, self-correcting manner is described. The mainframe deployment device is configured to receive a code section from the software management device, identify a set of valid sub-components from the code section using a dispatcher service associated with the dispatcher device, identify a set of elements in the code section identified for deployment, request the at least one testing service to perform at least one set of code diagnostics to determine whether the code section satisfies build requirements, attempt to create a deployment package from the code section, identify a production program running on the mainframe device, compare the production program to the deployment package to identify a set of synchronization errors, resolve the synchronization errors, and deploy the deployment package to the mainframe device upon resolving the set of synchronization errors.

Exposing and reproduction of race conditions is presented herein. A method identifies a synchronization mechanism of a grouping of operating system synchronization mechanisms; based on a tunable probability value, adjusts a race window associated with the synchronization mechanism; and based on the race window, raises a likelihood of revealing a race condition.

Managing concurrent accesses by a set of tasks to a shared resource of a computer system. Synchronizing the set of tasks for assigning and releasing a resource according to a predefined access period with flexibility of providing an extended access period where an external task is not detected during the predefined access period. Where an extended access period is provided, resynchronizing is performed, and the external task is identified and access is prevented when the external task is determined to be a particular type of task.

A data processing system adapted for securely debugging multiple different application instances in a single short-lived container includes a host computing platform having one or more computers, each with memory and at least one processor. The system also includes a container manager executing in the host computing platform, such that during execution, the container manager manages a multiplicity of different containers of a containerized environment. Finally, the system includes a debug server containerized within one of the containers. The debug server authenticates with the container manager for the one of the containers and establishes a communicative link over a computer communications network with a debug client disposed externally to the containerized environment, so that the debug server then proxies debug directives received from the debug client to selected ones of different application instances each executing within the one of the containers.

This document describes debugging multiple instances of code by detecting a variance in thread patterns of threads of execution relative to the multiple instances of executing code. A first instance of the code is executed and a first thread pattern is identified indicative of a first plurality of threads of execution of the first instance of the code. A second instance of the code is executed, the second instance of the code beginning executing prior to the first instance of the code completing executing, and a second thread pattern is identified indicative of a second plurality of threads of execution of the second instance of the code. A comparative representation of the first thread pattern and the second thread pattern is generated relative to each other. A variance between the first thread pattern and the second thread pattern relative to the comparative representation is identified, the variance typically being indicative of a bug in the code.

The present disclosure provides a multi-core processor. The multi-core processor comprises a plurality of cores and a debug circuit, the debug circuit comprising debug circuits in the same number as that of the cores, transmission controllers in the same number as that of the cores, and a master control circuit, each of the debug circuits being connected to one core and one transmission controller, respectively, and all transmission controllers being connected to the master control circuit. Each of the debug circuits is configured to generate a debug event signal and respond to the generated debug event signal or received debug event signals generated by other debug circuits. Each of the transmission controllers is configured to respectively control transmission of the debug event signal between the respectively connected debug circuit and the master control circuit. The master control circuit is configured to forward debug event signals among different transmission controllers. The present disclosure can realize rapid configuration and control of debug event signal transmission, and at the same time lower power consumption of a debug circuit.

The disclosed technology relates to a system configured to generate an initial tree state, wherein the initial tree state includes three tree data structures configured to aid in the synchronization of content items managed by a content management system. The system is configured to provide the initial tree state to a client synchronization service, retrieve a final tree state from the client synchronization service, and determine whether the final tree state is correctly synchronized.

A system and methods for contact center fault diagnostics, comprising a diagnostic engine and datastore of test cases used for testing components and services in a contact center, designed to operate on a contact center with a specified test campaign, allowing a contact center's various services and systems to be tested either internally or externally in an automated fashion with specified testcases being used to specify the format and expectations of a specific test, with reports of failures and points of failure being made available to system administrators.

Providing an enhanced continuous integration (CI)/continuous delivery (CD) build script debugging environment is disclosed. In one example, the CI/CD build script debugging environment inserts a breakpoint within a CI/CD build script that includes one or more build script steps. During execution of the CI/CD build script within the CI/CD build script debugging environment, execution is paused at the breakpoint, and a language-specific debugging environment suitable for debugging the next build script step is automatically identified and launched. Some examples may also provide that the CI/CD build script debugging environment allows the user to resume execution of the CI/CD build script within the CI/CD build script debugging environment without further pauses, and/or to step over a build script step by executing the build script step within the CI/CD build script debugging environment without launching a language-specific debugging environment.

Methods, apparatus, systems and articles of manufacture are disclosed to generate a graphics processing unit (GPU) long instruction trace (GLIT). An example apparatus includes at least one memory, and at least one processor to execute instructions to at least identify a first routine based on an identifier of a second routine executed by the GPU, the first routine based on an emulation of the second routine, execute the first routine to determine a first value of a GPU state of the GPU, the first routine having (i) a first argument associated with the second routine and (ii) a second argument corresponding to a second value of the GPU state prior to executing the first routine, and control a workload of the GPU based on the first value of the GPU state.