Error tracing method and device based on error reporting information, equipment, medium and product

Abstract

The invention discloses an error tracing method and device based on error reporting information, equipment, a medium and a product, and belongs to the technical field of software. The method comprises the following steps: acquiring error information, wherein the error information is used for representing error description information corresponding to an error code; the error information is analyzed to obtain attribution information and a code position corresponding to the error code, the attribution information is used for representing a source code to which the error code belongs, and the code position is used for representing the position of the error code in the source code; based on the affiliation information and the code position, determining processing personnel information of the error reporting code; and based on the information of the processing personnel, sending error reporting information corresponding to the error reporting code to the processing personnel. Through the method, the source of the error code can be automatically detected, the personnel who have processed the error code can be traced and determined, the labor cost of manual error checking is saved, and the error repairing speed can be increased.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of software technology, and in particular to an error tracing method, device, equipment, medium and product based on error reporting information. Background Art

[0002] With the rapid development of software technology, the version update rate of software products is also getting faster and faster. In the process of software system development, various errors are inevitable at various stages.

[0003] In the related art, in order to troubleshoot the cause of an error code, a common practice is to manually analyze and determine the error type corresponding to the error code by checking the error log, and then perform error repair on the error code according to the error type.

[0004] In view of the above processing methods, manual error troubleshooting is time-consuming and inefficient, and does not analyze and locate the error problem from the source. Based on this, how to quickly and accurately process the error code has become an important technical problem that needs to be solved urgently by those skilled in the art. Summary of the invention

[0005] The present application provides an error tracing method, device, equipment, medium and product based on error reporting information, and the technical solution is as follows:

[0006] According to one aspect of the present application, a method for error tracing based on error reporting information is provided, the method comprising:

[0007] Obtain the error information, where the error information is used to indicate the error description information corresponding to the error code;

[0008] Parse the error information to obtain attribution information and code position corresponding to the error code, wherein the attribution information is used to indicate the source code to which the error code belongs, and the code position is used to indicate the position of the error code in the source code;

[0009] Determine, based on the attribution information and the code position, information about a person who has handled the error code, wherein the information about the person who has handled the error code;

[0010] Based on the processing personnel information, the error information corresponding to the error code is sent to the processing personnel.

[0011] According to one aspect of the present application, a device for tracing an error based on error reporting information is provided, the device comprising:

[0012] An acquisition module, used to obtain the error information, where the error information is used to indicate the error description information corresponding to the error code;

[0013] A parsing module, used to parse the error information to obtain the attribution information and code position corresponding to the error code, wherein the attribution information is used to indicate the source code to which the error code belongs, and the code position is used to indicate the position of the error code in the source code;

[0014] A determination module, configured to determine information of a person who has processed the error code based on the attribution information and the code position, wherein the information of the person who has processed the error code refers to information of a person who has processed the error code;

[0015] A sending module is used to send the error information corresponding to the error code to the processing personnel based on the processing personnel information.

[0016] According to another aspect of the present application, a computer device is provided, which includes: a processor and a memory, wherein at least one computer program is stored in the memory, and the at least one computer program is loaded and executed by the processor to implement the error tracing method based on error reporting information as described above.

[0017] According to another aspect of the present application, a computer storage medium is provided, in which at least one computer program is stored. The at least one computer program is loaded and executed by a processor to implement the error tracing method based on error reporting information as described above.

[0018] According to another aspect of the present application, a computer program product is provided, which includes a computer program stored in a computer-readable storage medium; the computer program is read and executed from the computer-readable storage medium by a processor of a computer device, so that the computer device executes the error tracing method based on error reporting information as described above.

[0019] The beneficial effects of the technical solution provided by this application include at least:

[0020] By obtaining the error information and parsing the error information, the attribution information and code position corresponding to the error code are obtained; based on the attribution information and code position, the person who has handled the error code is determined; after the person who has handled the error code is determined, the error information corresponding to the error code is sent to the person who has handled it. This application achieves the location and tracing of the error code by parsing the error information corresponding to the error code, and can automatically detect the source of the error code and trace back to determine the person who has handled the error code, which not only saves the manpower cost of manually troubleshooting errors, but also can be assigned to the person who has handled the error code, speeding up the error repair process. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0022] Figure 1 is a schematic diagram of an error tracing method based on error reporting information provided by an exemplary embodiment of the present application;

[0023] Figure 2 is a schematic diagram of the architecture of a computer system provided by an exemplary embodiment of the present application;

[0024] Figure 3 is a flow chart of an error tracing method based on error reporting information provided by an exemplary embodiment of the present application;

[0025] Figure 4 is a flow chart of an error tracing method based on error reporting information provided by an exemplary embodiment of the present application;

[0026] Figure 5 is a schematic diagram of an error log provided by an exemplary embodiment of the present application;

[0027] Figure 6 is a schematic diagram of an error information sheet provided by an exemplary embodiment of the present application;

[0028] Figure 7 is a flow chart of an error tracing method based on error reporting information provided by an exemplary embodiment of the present application;

[0029] Figure 8 is a flowchart of error information analysis and tracing provided by an exemplary embodiment of the present application;

[0030] Fig. 9 is a flow chart of managing error information provided by an exemplary embodiment of the present application;

[0031] Fig.10 is a schematic diagram of an error tracing method based on error reporting information provided by an exemplary embodiment of the present application;

[0032] Fig.11 It is a schematic diagram of a Web front-end display page provided by an exemplary embodiment of the present application;

[0033] Fig.12 is a flow chart of an error tracing method based on error reporting information provided by an exemplary embodiment of the present application;

[0034] Fig.13is a flow chart of an error tracing method based on game error information and applied to a game, provided by an exemplary embodiment of the present application;

[0035] Fig.14 is a block diagram of an error tracing device based on error reporting information provided by an exemplary embodiment of the present application;

[0036] Fig.15 It is a structural diagram of a computer device provided by an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0037] In order to make the purpose, technical scheme and advantages of the present application clearer, the implementation mode of the present application will be further described in detail below in conjunction with the accompanying drawings. The exemplary embodiments will be described in detail here, and examples thereof are shown in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation modes described in the following exemplary embodiments do not represent all implementation modes consistent with the present application. Instead, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the attached claims.

[0038] The terms used in this disclosure are for the purpose of describing specific embodiments only and are not intended to limit the disclosure. The singular forms of "a", "said" and "the" used in this disclosure and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0039] It should be understood that although the terms first, second, third, etc. may be used in the present disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other.

[0040] The present application embodiment provides a schematic diagram of an error tracing method based on error reporting information, such as Figure 1 As shown, the method can be executed by a computer device, which is an error information tracing device provided with an error information tracing function.

[0041] Exemplarily, the computer device obtains error information 30 corresponding to the client 10 and / or the server 20, and the error information 30 is used to indicate the error description information corresponding to the error code; after the computer device performs deduplication processing 40 on the error information 30, it then performs error information parsing 50 to obtain attribution information 60 and code position 70 corresponding to the error code, and the attribution information 60 is used to indicate the location of the source code to which the error code belongs, and the code position 70 is used to indicate the location of the error code in the source code; based on the attribution information 60 and the code position 70, the computer device determines the processing personnel information 80 of the error code, and the processing personnel information 80 refers to the personnel who have processed the error code. After determining the processing personnel, the computer device sends the error information corresponding to the error code to the processing personnel.

[0042] The error information 30 includes an error log corresponding to the error code and code running parameters.

[0043] The error log is used to record error information in the code.

[0044] The code running parameters are used to represent the parameters of the running error code. The code running parameters include at least one of the device environment parameters, code packaging parameters, and error reporting time during the code running process, but are not limited thereto, and the embodiments of the present application do not specifically limit this.

[0045] Optionally, the device environment parameters include at least one of a device name, a device identifier, central processing unit (CPU) information, and memory information, but are not limited thereto, and the embodiments of the present application do not make specific limitations on this.

[0046] Optionally, the code packaging parameters include at least one of packaging time, a project version to which the code belongs, and a project branch to which the code belongs, but are not limited thereto and are not specifically limited in this embodiment of the present application.

[0047] The source code refers to the software code package where the error code is located. For example, the error code is in the 42nd version of the software code package.

[0048] The deduplication process 40 includes deleting at least one of the time, address, and parameter data in the error log, but is not limited thereto, and the embodiment of the present application does not make specific limitations on this.

[0049] Exemplarily, after obtaining the deduplicated error information 30 , the computer device determines the source code to which the error code belongs based on the code running parameters in the error information 30 ; the computer device determines the code position 70 of the error code in the source code based on the error log in the error information 30 .

[0050] The attribution information 60 is determined in the following manner: the computer device determines the project version and project branch corresponding to the error code based on the code running parameters; the computer device determines the source code to which the error code belongs based on the project version and project branch.

[0051] The project version refers to the identifier corresponding to the code software package or source code during the software development process, such as the first version, the second version, and so on.

[0052] The project branch is used to indicate the functional category corresponding to the error code.

[0053] Project branches include main branches and functional branches. The main branch is used to save and record the functional codes that have been completed in the entire project. Therefore, programmers are not allowed to modify the code directly on the main branch. Functional branches refer to branches that are specifically used to develop new functions. They are forked from the main branch. When the new function is developed and tested, it needs to be merged into the main branch.

[0054] The method for obtaining code position 70 is as follows: the computer device traverses and analyzes the error log, extracts the file name where the error code is located and the code number corresponding to the error code through a regular expression, and obtains code position 70 based on the file name and the code number.

[0055] The code sequence number refers to the line number of the error code in the source code.

[0056] The processing personnel information 80 includes at least one of a submitting personnel and a testing personnel, but is not limited thereto, and the embodiment of the present application does not make any specific limitation on this.

[0057] After determining the attribution information 60 and code position 70 corresponding to the error code, the computer device searches for the submitter and submission log corresponding to the error code; the computer device extracts the development requirement sheet corresponding to the error code based on the submission log; the computer device determines the tester corresponding to the error code through the development requirement sheet.

[0058] The submitter is the person who writes the error reporting code.

[0059] Testers are people who test error reporting codes.

[0060] The submission log is used to record relevant information of the submitted error code, wherein the submission log includes at least one of the code development requirement form, submission time, and submission location, but is not limited to this. The embodiments of the present application do not make specific limitations on this.

[0061] The development requirement sheet is used to record at least one of the purpose of writing code, the requirements for writing code, the standards for testing the code, and the testers who test the code, but is not limited to these. The embodiments of the present application do not make specific limitations on this.

[0062] In summary, the method provided in this embodiment obtains the attribution information and code position corresponding to the error code by obtaining the error information and parsing the error information; based on the attribution information and code position, the person who has handled the error code is determined; after the person who has handled the error code is determined, the error information corresponding to the error code is sent to the person who has handled the error code. This application realizes the location and tracing of the error code by parsing the error information corresponding to the error code, and can automatically detect the source of the error code and trace back to determine the person who has handled the error code, which not only saves the manpower cost of manually troubleshooting errors, but also speeds up the error repair process.

[0063] Figure 2 The schematic diagram of the architecture of a computer system provided by an embodiment of the present application is shown. The computer system may include: a terminal 100, a server 200 and an error information tracing device 300.

[0064] The terminal 100 may be an electronic device such as a mobile phone, a tablet computer, a vehicle-mounted terminal (vehicle computer), a wearable device, a personal computer (PC), a vehicle-mounted terminal, an aircraft, an unmanned vending terminal, etc. The terminal 100 may be installed with a client that runs a target application, and the target application may be an application that can generate error information, or may be other applications that can provide the function of generating error information, which is not limited in this application. In addition, this application does not limit the form of the target application, including but not limited to an application (Application, App) installed in the terminal 100, a mini-program, etc., and may also be in the form of a web page.

[0065] The server 200 may be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services, cloud database, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (CDN), and cloud servers providing basic cloud computing services such as big data and artificial palm image recognition platforms. The server 200 may be a backend server of the above-mentioned target application, used to provide backend services for the client of the target application.

[0066] Among them, cloud technology refers to a hosting technology that unifies hardware, software, network and other resources in a wide area network or local area network to realize data computing, storage, processing and sharing. Cloud technology is a general term for network technology, information technology, integration technology, management platform technology, application technology, etc. based on the cloud computing business model. It can form a resource pool, which is used on demand and flexible and convenient. Cloud computing technology will become an important support. The background services of the technical network system require a large amount of computing and storage resources, such as video websites, picture websites and more portal websites. With the high development and application of the Internet industry, in the future, each item may have its own identification mark, and all need to be transmitted to the background system for logical processing. Data of different levels will be processed separately. All kinds of industry data require strong system backing support, which can only be achieved through cloud computing.

[0067] The error information tracing device 300 is a computer device with computing capabilities. The device type of the error information tracing device 300 includes but is not limited to a smart phone, a tablet computer, a desktop computer or a laptop computer, etc., and this embodiment of the application does not specifically limit this.

[0068] In some embodiments, the above-mentioned server can also be implemented as a node in a blockchain system. Blockchain is a new application mode of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, encryption algorithm, etc. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. Blockchain can include the underlying blockchain platform, the platform product service layer, and the application service layer.

[0069] The terminal 100 and the server 200 may communicate via a network, such as a wired or wireless network; the terminal 100 and the error information tracing device 300 may communicate via a network; the error information tracing device 300 and the server 200 may communicate via a network.

[0070] Figure 3 is a flowchart of an error tracing method based on error reporting information provided by an exemplary embodiment of the present application. The method can be executed by a computer device, which can be Figure 2 The method comprises:

[0071] Step 302: Obtain error information.

[0072] The error message is used to indicate the error description information corresponding to the error code.

[0073] When an error occurs during code execution, an error message will be given to indicate that there is an error code in the code.

[0074] The error information includes the error log corresponding to the error code and the code running parameters.

[0075] The error log is used to record error information in the code.

[0076] The code running parameters are used to represent the parameters of the running error code. The code running parameters include at least one of the device environment parameters, code packaging parameters, and error reporting time during the code running process, but are not limited thereto, and the embodiments of the present application do not specifically limit this.

[0077] The error log is generated when the code runs into an error on the client, or the error log is generated when the code runs into an error on the server, or the error log is generated when the code runs into an error on both the client and the server.

[0078] The code running parameters include the running parameters when the code is running on the client, or the code running parameters include the running parameters when the code is running on the server, or the code running parameters include the running parameters when the code is running on the client and the server at the same time.

[0079] Step 304: parse the error information to obtain the attribution information and code position corresponding to the error code.

[0080] The attribution information is used to indicate the source code to which the error code belongs.

[0081] The source code refers to the software code package where the error code is located. For example, the error code is in the software code package packaged in version 21.

[0082] The code position is used to indicate the location of the error code in the source code.

[0083] Exemplarily, the computer device parses the error information to obtain the source code to which the error code belongs and the specific location of the error code in the source code.

[0084] Step 306: Based on the attribution information and the code location, search and determine the information of the person who handled the error code.

[0085] Processing personnel information refers to the information of the processing personnel who processed the error code.

[0086] Optionally, the processing personnel information includes at least one of a submitting personnel and a testing personnel, but is not limited thereto, and the embodiments of the present application do not make specific limitations on this.

[0087] The submitter is the person who wrote the error code.

[0088] Testers are people who test the error code.

[0089] Exemplarily, the computer device finds the submitter and / or tester who has processed the error code based on the source code to which the error code belongs and the specific location of the error code in the source code, thereby determining the error corresponding to the error code from the source.

[0090] Step 308: Based on the processing personnel information, send error information corresponding to the error code to the processing personnel.

[0091] Exemplarily, the computer device sends the error code and / or the error information corresponding to the error code to the processing personnel, so as to modify the error code.

[0092] Optionally, the computer device sends the error code and / or error information corresponding to the error code to the submitter and / or the tester to modify the error code.

[0093] In summary, the method provided in this embodiment obtains the attribution information and code position corresponding to the error code by obtaining the error information and parsing the error information; based on the attribution information and code position, the person who has handled the error code is determined; after the person who has handled the error code is determined, the error code is assigned to the person who has handled it for repair. This application realizes the location and tracing of the error code by parsing the error information corresponding to the error code, and can automatically detect the source of the error code and trace back to determine the person who has handled the error code, which not only saves the manpower cost of manually troubleshooting errors, but also speeds up the error repair process.

[0094] Figure 4 is a flowchart of an error tracing method based on error reporting information provided by an exemplary embodiment of the present application. The method can be executed by a computer device, which can be Figure 2 The method comprises:

[0095] Step 402: Obtain error information.

[0096] The error message is used to indicate the error description information corresponding to the error code.

[0097] When an error occurs during code execution, an error message will be given to indicate that there is an error code in the code.

[0098] Optionally, the error includes, but is not limited to, a script layer code error, a compilation error, and a crash stack error during code runtime. Compilation errors include, but are not limited to, syntax errors, link errors, semantic errors, and the like.

[0099] Step 404: Based on the code running parameters, determine the source code to which the error code belongs.

[0100] The source code refers to the software code package where the error code is located. For example, the error code is in the software code package packaged in version 21.

[0101] The code position is used to indicate the location of the error code in the source code.

[0102] The code running parameters are used to represent the parameters of the running error code. The code running parameters include at least one of the device environment parameters, code packaging parameters, and error reporting time during the code running process, but are not limited thereto, and the embodiments of the present application do not specifically limit this.

[0103] The code running parameters include the running parameters when the code is running on the client, or the code running parameters include the running parameters when the code is running on the server, or the code running parameters include the running parameters when the code is running on the client and the server at the same time.

[0104] Optionally, the device environment parameters include at least one of device information, device identification, central processing unit (CPU) information, and memory information, but are not limited thereto, and the embodiments of the present application do not make specific limitations on this.

[0105] Optionally, the device information includes at least one of a terminal model, a terminal location, a server model, and a server location, but is not limited thereto, and the embodiments of the present application do not make specific limitations on this.

[0106] Optionally, the code packaging parameters include at least one of packaging time, a project version to which the code belongs, and a project branch to which the code belongs, but are not limited thereto and are not specifically limited in this embodiment of the present application.

[0107] The project version refers to the identifier corresponding to the code software package or source code during the software development process, such as the first version, the second version, and so on.

[0108] The project branch is used to indicate the functional category corresponding to the error code.

[0109] Project branches include main branches and functional branches. The main branch is used to save and record the functional codes that have been completed in the entire project. Therefore, programmers are not allowed to modify the code directly on the main branch. Functional branches refer to branches that are specifically used to develop new functions. They are forked from the main branch. When the new function is developed and tested, it needs to be merged into the main branch.

[0110] Exemplarily, the computer device determines the project version and project branch corresponding to the error code based on the code running parameters; the computer device determines the source code to which the error code belongs based on the project version and project branch.

[0111] The computer device sends a query instruction to the version control system, wherein the query instruction includes a project version and a project branch; the version control system queries the source code according to the project version and the project branch, and the computer device receives the source code returned by the version control system that matches the query instruction.

[0112] A version control system is a system that records changes to the contents of one or more files so that specific revisions can be referenced in the future.

[0113] Optionally, common version control systems include at least one of a centralized version control system (Subversion, Svn) and a distributed version control system Git, but are not limited thereto and are not specifically limited in the embodiments of the present application.

[0114] For example, the code running parameter collected by the computer device is the package compilation version, which refers to the version of the software package or library generated by compilation. For example, the package compilation version is executable file (exe) package-254, which represents the exe software package, and the package ID is 254. Based on this information, the corresponding project branch, packaging time and project version can be found. The computer device queries the project library through the version control system to obtain the source code that matches the project version and project branch.

[0115] The project library contains packaged software packages corresponding to different project branches and different project versions.

[0116] Step 406: Based on the error log, determine the code location of the error code in the source code.

[0117] The error log is used to record error information in the code.

[0118] The error log is generated when the code runs into an error on the client, or the error log is generated when the code runs into an error on the server, or the error log is generated when the code runs into an error on both the client and the server.

[0119] Exemplarily, the computer device traverses and analyzes the error log, extracts the file name where the error code is located and the code number corresponding to the error code through a regular expression, and obtains the code location based on the file name and the code number.

[0120] A regular expression is an expression used to match strings.

[0121] For example, in a regular expression, \d can match a number, \w can match a letter or number, and . can match any character. For example, the regular expression can be expressed as: r' / (.*)\:(\d+$)'. Different error reporting feature styles can be matched by a computer device with different regular expressions, which is not specifically limited in the embodiments of the present application.

[0122] The code sequence number refers to the line number of the error code in the source code, for example, line 389 in the source code.

[0123] For example, Figure 5 The schematic diagram of the error log shown in the figure shows an error log of a script language lua file. The content selected in the box in the figure is the error feature 501. The error feature 501 includes the file name where the error code is located and the code sequence number corresponding to the error code. For example, World / systems / interact system:28, the previous World / systems / interact system refers to the file name where the error code is located, and 28 refers to the code sequence number corresponding to the error code.

[0124] In some embodiments, before analyzing the error log, the computer device performs deduplication processing on the acquired error log to obtain a deduplicated error log.

[0125] Optionally, the computer device deletes at least one of the time, address, and parameter data in the error log to obtain a deduplicated error log.

[0126] After the computer device obtains the error log, the computer device analyzes the error stack data, identifies and removes irrelevant information such as time, address, parameter data, etc. in the error log, and obtains a deduplicated error log, thereby making the extraction of the file name and code serial number of the error code location more convenient and efficient.

[0127] Step 408: Based on the attribution information and the code location, search and determine the information of the person who handled the error code.

[0128] Processing personnel information refers to the information of the processing personnel who processed the error code.

[0129] Optionally, the processing personnel information includes at least one of a submitting personnel and a testing personnel, but is not limited thereto, and the embodiments of the present application do not make specific limitations on this.

[0130] The submitter is the person who wrote the error code.

[0131] Testers are people who test the error code.

[0132] Exemplarily, after determining the attribution information and code location corresponding to the error code, the computer device determines the submitter and submission log corresponding to the error code based on the attribution information and code location; the computer device extracts the development requirement sheet corresponding to the error code based on the submission log; the computer device determines the tester corresponding to the error code through the development requirement sheet.

[0133] The submitter is the person who writes the error reporting code.

[0134] Testers are people who test error reporting codes.

[0135] The submission log is used to record relevant information of the submitted error code, wherein the submission log includes at least one of the code development requirement form, submission time, and submission location, but is not limited to this. The embodiments of the present application do not make specific limitations on this.

[0136] The development requirement sheet is used to record at least one of the purpose of writing code, the requirements for writing code, the standards for testing the code, and the testers who test the code, but is not limited to these. The embodiments of the present application do not make specific limitations on this.

[0137] For example, after determining the attribution information and code location corresponding to the error code, the computer device determines the submitter and submission log corresponding to the error code through a centralized version tracing (Svn blame) instruction or a distributed version tracing (Git blame) instruction; the computer device extracts the development requirement sheet corresponding to the error code based on the submission log; the computer device determines the tester corresponding to the error code through the development requirement sheet, thereby determining the error source of the error code. In a possible implementation, after tracing back to the processing personnel information corresponding to the error code, if there is no error information sheet corresponding to the error information in the database, the computer device automatically creates an error information sheet and saves it to the database; the computer device scans the error information sheet in the database to obtain the status parameters corresponding to the error information sheet; if the computer device does not add the same error information sheet within the set time period, the application program interface (Application ProgramInterface, API) interface is called to close the error information sheet.

[0138] The status parameters include the last reporting time and repair status of the error information sheet.

[0139] The repair status refers to whether the error code corresponding to the error information sheet has been repaired.

[0140] If there is an error message sheet corresponding to the error information in the database and the error message sheet has not been closed, update the reporting time corresponding to the error information; scan the error message sheets in the database to obtain the status parameters corresponding to the error message sheets; if the same error message sheet is not added within the set time period, call the API interface to close the error message sheet.

[0141] The error information sheet includes at least one of an error code, code running parameters, and processing personnel information, but is not limited to this. The embodiments of the present application do not make specific limitations on this.

[0142] For example, the duration is set to 7 days, that is, if the same error information ticket is not added within 7 days, the error information ticket is considered to be closed, and the API interface is called to close the error information ticket.

[0143] For example, Figure 6 The schematic diagram of the error information sheet shown includes error information, submission record, package compilation version, machine name, related sheet (i.e., development requirement sheet), submitter, etc. The error information sheet can clearly show the location corresponding to the error code and the corresponding submitter.

[0144] Step 410: Based on the processing personnel information, send error information corresponding to the error code to the processing personnel.

[0145] Exemplarily, the computer device sends the error code and / or the error information corresponding to the error code to a processing personnel, and the processing personnel modifies the error code.

[0146] In some embodiments, the computer device sends the error information to at least one of the submitter and the tester based on the processing personnel information to repair the error code.

[0147] Optionally, after tracing back to the processing personnel information corresponding to the error code, based on the processing personnel information, the error information sheet corresponding to the error code is sent to the submitting person for repair.

[0148] Optionally, after tracing back to the processing personnel information corresponding to the error code, based on the processing personnel information, the error information sheet corresponding to the error code is sent to the tester for repair.

[0149] Optionally, after tracing back to the processing personnel information corresponding to the error code, based on the processing personnel information, the error information corresponding to the error code is sent to the submitter and the tester for joint repair.

[0150] Optionally, after tracing back to the processing personnel information corresponding to the error code, based on the processing personnel information, the error information corresponding to the error code is sent to the submitter for repair, and sent to the tester, who tests the code repaired by the submitter.

[0151] In summary, the method provided in this embodiment obtains the attribution information and code position corresponding to the error code by obtaining the error information and parsing the error information; based on the attribution information and code position, the person who has handled the error code is determined; after the person who has handled the error code is determined, the error information corresponding to the error code is sent to the person who has handled it for repair. This application realizes the location and tracing of the error code by parsing the error information corresponding to the error code, and can automatically detect the source of the error code and trace back to determine the person who has handled the error code, which not only saves the manpower cost of manually troubleshooting errors, but also speeds up the error repair process.

[0152] The method provided in this embodiment can automatically detect the source of the error code by parsing the error log and code running parameters in the error information, thereby determining the location of the error code from the source. This not only saves the manpower cost of manual error troubleshooting, but also speeds up error repair.

[0153] The method provided in this embodiment can automatically trace back the person who has handled the error code by searching for the submitter and tester corresponding to the error code through the location of the error code. This not only saves the manpower cost of manual error troubleshooting, but also can assign the person who has handled the error code, thereby speeding up error repair.

[0154] The method provided in this embodiment realizes the management of existing error reports by constructing and detecting error information sheets. When the same error report already exists, the status parameters are scanned and obtained, and the error information sheet is closed if the conditions are met. When there is no same error report, a new error information sheet is created, and the status parameters are scanned and obtained, and the error information sheet is closed if the conditions are met. The above-mentioned method realizes the monitoring and management of the processing of error codes, and the repair status of the error codes is timely monitored through the error information sheet, so that the error codes can be repaired in time, which improves the error repair efficiency and reduces the manpower cost of error follow-up.

[0155] The method provided in this embodiment makes the error log more concise by deduplicating the error log, improves the error log parsing efficiency, and further improves the error repair efficiency.

[0156] Figure 7 is a flowchart of an error tracing method based on error reporting information provided by an exemplary embodiment of the present application. The method can be executed by a computer device, which can be Figure 2 The error information tracing device includes a software development kit (SDK) end and a server end. The method includes:

[0157] Step 701: Collect error information.

[0158] The error message is used to indicate the error description information corresponding to the error code.

[0159] Exemplarily, the SDK end of the error information tracing device collects error information corresponding to the client end that runs the code and / or the server end that runs the code.

[0160] The error information includes the error log corresponding to the error code and the code running parameters.

[0161] The error log is obtained in the following manner: the SDK end of the error information tracing device obtains the error log by intercepting the error log output by the client end running the code and / or the server end running the code.

[0162] The code running parameters are obtained as follows: the SDK end of the error information tracing device finds the running parameters of the code when it is running in the client and / or server based on the error log.

[0163] Step 702: De-duplicate and save the error log.

[0164] After obtaining the error log, the server of the error information tracing device deduplicates the error log obtained by the SDK, obtains the deduplicated error log and saves it in the database.

[0165] Optionally, the server of the error information tracing device obtains a deduplicated error log by deleting at least one of the time, address, and parameter data in the error log.

[0166] In some embodiments, after the SDK side of the error information tracing device obtains the error log, the server side of the error information tracing device analyzes the error stack data, identifies and removes irrelevant information such as time, address, parameter data, etc. in the error log, and obtains a deduplicated error log, thereby making the extraction of the file name and code serial number of the error code location more convenient and efficient.

[0167] Step 703: Analyze and trace the error information.

[0168] After the server of the error information tracing device deduplicates the error log, the server parses the error information to obtain the attribution information and code position corresponding to the error code. The server traces the person who handled the error code based on the attribution information and code position.

[0169] The attribution information is used to indicate the source code to which the error code belongs, and the code position is used to indicate the position of the error code in the source code.

[0170] Optionally, the personnel who have processed the error code include at least one of a submitter and a tester, but are not limited to this, and the embodiments of the present application do not make specific limitations on this.

[0171] The submitter is the person who wrote the error code.

[0172] Testers are people who test the error code.

[0173] Exemplarily, the server queries and determines the project version and project branch corresponding to the error code based on the code running parameters; the server determines the source code to which the error code belongs based on the project version and project branch obtained by the query.

[0174] After determining the source code, the server traverses and analyzes the error log, and uses regular expressions to extract the file name where the error code is located, as well as the code number corresponding to the error code. The server obtains the code location based on the file name and code number.

[0175] After determining the source code and code location corresponding to the error code, the server determines the submitter and submission log corresponding to the error code based on the source code and code location; the server extracts the development requirement sheet corresponding to the error code based on the submission log; the server determines the tester corresponding to the error code through the development requirement sheet.

[0176] The development requirement sheet is used to record at least one of the purpose of writing code, the requirements for writing code, the standards for testing the code, and the testers who test the code, but is not limited to these. The embodiments of the present application do not make specific limitations on this.

[0177] Exemplarily, step 703 is implemented as steps 7031 to 7034, such as Figure 8 It is a flowchart of error information analysis and tracing provided by an exemplary embodiment of the present application.

[0178] Step 7031: Determine the project branch and project version based on the package version.

[0179] The package version refers to the version of the compiled software package or library.

[0180] The server determines the project branch and project version corresponding to the error code based on the package version information in the error message.

[0181] Step 7032: Update the project engineering library.

[0182] After the server determines the project version and project branch corresponding to the error code, the server updates the project project library to the corresponding project version and project branch based on the project version and project branch. The server searches for the source code corresponding to the error code based on the corresponding project version and project branch.

[0183] Step 7033: Extract the file name where the error code is located and the code line number corresponding to the error code.

[0184] Exemplarily, the server traverses and analyzes the error log, extracts the file name where the error code is located and the code number corresponding to the error code through a regular expression, and obtains the code location based on the file name and the code number.

[0185] Step 7034: Obtain the submitter and submission log corresponding to the error code.

[0186] Exemplarily, after determining the source code and code location corresponding to the error code, the server determines the submitter and submission log corresponding to the error code based on the attribution information and the code location; the server extracts the development requirement sheet corresponding to the error code based on the submission log; the server determines the tester corresponding to the error code through the development requirement sheet.

[0187] Step 704: Assign the error report and create an error information ticket.

[0188] The error information sheet includes at least one of an error code, code running parameters, and processing personnel information, but is not limited to this. The embodiments of the present application do not make specific limitations on this.

[0189] For example, after tracing back to the information of the handler corresponding to the error code, if there is no error information sheet corresponding to the error information in the database, the server automatically creates an error information sheet and saves it to the database; if there is an error information sheet corresponding to the error information in the database and the error information sheet is not closed, the reporting time corresponding to the error information is updated. After obtaining the error information sheet, the repair task corresponding to this error code is sent to the handler, that is, after determining the information of the handler corresponding to the error code, the error code is sent to the handler for repair.

[0190] The status parameters include the last reporting time and repair status of the error information sheet.

[0191] The repair status refers to whether the error code corresponding to the error information sheet has been repaired.

[0192] In some embodiments, the server creates an API interface corresponding to the error information form and creates the error information form. The server sends the API interface to the processing personnel, and the processing personnel can repair the error code by calling the API interface.

[0193] Exemplarily, step 704 may be specifically implemented as steps 7041 to 7047, such as Fig. 9 A flowchart for managing error information is shown.

[0194] Step 7041: Extract error features.

[0195] The error feature refers to the file name where the error code is located and the code sequence number corresponding to the error code.

[0196] The server extracts the file name where the error code is located and the code sequence number corresponding to the error code.

[0197] Step 7042: Determine whether the error reporting feature already exists.

[0198] After obtaining the file name where the error code is located and the code number corresponding to the error code, the server determines whether the error feature is already in the database. If the error feature is not available, execute step 7043; if the error feature is already available, execute step 7045.

[0199] Step 7043: Save the error information to the database.

[0200] In the absence of the error feature, the server saves the error information to the database for subsequent error information management services.

[0201] Step 7044: Analyze and trace the error information.

[0202] In the absence of the error feature, the server analyzes and traces the error information to obtain the information of the person who has processed the error code, and then enters and executes step 703.

[0203] Step 7045: Update the number of error reports and reporting time.

[0204] When the error reporting feature is present, the server updates the reporting time and reporting frequency corresponding to the error reporting information.

[0205] Step 7046: Determine whether the existing error message sheet is closed.

[0206] After the server updates the reporting time and reporting times corresponding to the error information, the server determines whether the existing error information sheet is closed. If the existing error information sheet is not closed, execute step 7047; if the existing error information sheet is closed, execute step 7044.

[0207] Step 7047: End.

[0208] Step 705: Scan the error information sheet and close the error information sheet.

[0209] The server scans the error information sheets in the database and obtains the status parameters corresponding to the error information sheets. If no identical error information sheets are added within the set time period, the error information sheet is considered to have been repaired, and then the API interface corresponding to the error information sheet is called to close the error information sheet.

[0210] In summary, the method provided in this embodiment obtains the attribution information and code position corresponding to the error code by obtaining the error information and parsing the error information; based on the attribution information and code position, the person who has handled the error code is determined. This application realizes the location and tracing of the error code by parsing the error information corresponding to the error code, and can automatically detect the source of the error code, which not only saves the manpower cost of manually troubleshooting errors, but also speeds up the error repair speed.

[0211] Fig.10 is a schematic diagram of an error tracing method based on error reporting information provided by an exemplary embodiment of the present application. The method can be executed by a computer device, and the computer device can be Figure 2 The method comprises:

[0212] The error information tracing device includes an SDK end 1001 and a server end 1002. The SDK end 1001 is used to collect error information corresponding to the client running the code and / or the server running the code. After collecting the error information, the SDK end 1001 stores the collected error information in a database 1003 in the server end 1002. The server end 1002 performs error information management services based on the error information in the database 1003. The error information management service runs in the background and can also be displayed on the Web front end 1004 and provide an API interface 1005 for calling.

[0213] Optionally, the error information management service includes at least one of data storage 1006, deduplication service 1007, error classification and statistics 1008, error location and dispatch 1009, error ticket creation 1010 and error repair status monitoring 1011, but is not limited to this, and the embodiments of the present application do not make specific limitations on this.

[0214] The deduplication service 1007 refers to the server 1002 performing deduplication processing on the error log obtained by the SDK 1001 to obtain a deduplicated error log.

[0215] Error classification and statistics 1008 refers to the server 1002 collecting statistics on error information, such as error time, error type, etc.

[0216] Error location and dispatch 1009 refers to the server 1002 parsing the error information, obtaining the attribution information and code position corresponding to the error code, and searching and determining the information of the person who handles the error code based on the attribution information and code position.

[0217] Error report creation 1010 means that when the server 1002 does not have an error information sheet corresponding to the error information in the database, that is, when this type of error occurs for the first time, the server 1002 automatically creates an error information sheet.

[0218] Error repair status monitoring 1011 means that the server 1002 obtains the status parameters corresponding to the error information sheet by scanning the error information sheet in the database; if the same error information sheet is not added within the set time period, the error information sheet is closed.

[0219] For example, Fig.11 The schematic diagram of the Web front-end display page shown in the figure shows the name of the machine generating the error, the machine ID, the error information, the error type, the first reporting time, the last reporting time, the repair status, the number of errors, the follow-up person, the compilation version, the code version, the code branch, the bug ticket link, etc. As shown in the error source classification 1101 in the figure, since the error information can come from the client or the server, by selecting the error information from different sources, the corresponding error information is displayed in the Web front-end.

[0220] In summary, the method provided in this embodiment obtains the attribution information and code position corresponding to the error code by obtaining the error information and parsing the error information; based on the attribution information and code position, the person who has handled the error code is determined. This application realizes the location and tracing of the error code by parsing the error information corresponding to the error code, and can automatically detect the source of the error code, which not only saves the manpower cost of manually troubleshooting errors, but also speeds up the error repair speed.

[0221] Fig.12 is a flowchart of an error tracing method based on error reporting information provided by an exemplary embodiment of the present application. The method can be executed by a computer device, which can be Figure 2 The method comprises:

[0222] Step 1201: Obtain client error information.

[0223] When an error occurs when the code is running on the client, the error information tracing device obtains the client error information.

[0224] Step 1202: Obtain the server error information.

[0225] When an error occurs while the code is running on the server, the error information tracing device obtains the error information on the server.

[0226] Step 1203: Deduplication processing.

[0227] The error information includes error log and code running parameters.

[0228] The error log is used to record error information in the code.

[0229] The code running parameters are used to represent the parameters of the running error code. The code running parameters include at least one of the device environment parameters, code packaging parameters, and error reporting time during the code running process, but are not limited thereto, and the embodiments of the present application do not specifically limit this.

[0230] Before analyzing the error log, the error information tracing device performs deduplication processing on the acquired error log to obtain a deduplicated error log.

[0231] Optionally, the error information tracing device deletes at least one of the time, address, and parameter data in the error log to obtain a deduplicated error log.

[0232] Step 1204: Analyze the error information.

[0233] After deduplicating the error information, the error information tracing device then parses the error information to obtain the attribution information and code position corresponding to the error code. The attribution information is used to indicate the location of the source code to which the error code belongs, and the code position is used to indicate the location of the error code in the source code. The error information tracing device determines the information of the person who handled the error code based on the attribution information and the code position. The person who handled the error code refers to the person who handled the error code.

[0234] Step 1205: Update the number of error reports and the last reporting time.

[0235] If there is an error information sheet corresponding to the error information in the database, the number of errors and the last reporting time corresponding to the error information are updated.

[0236] Step 1206: Determine whether the existing error information sheet is closed.

[0237] When there is an error message sheet corresponding to the error message in the database, determine whether the existing error message sheet is closed. If the existing error message sheet is not closed, execute step 1213; if the existing error message sheet is closed, execute step 1208.

[0238] Step 1207: Save the error information to the database.

[0239] After tracing back the processing personnel information corresponding to the error code, if there is no error information sheet corresponding to the error information in the database, the error information tracing device saves the error information sheet in the database.

[0240] Step 1208: Determine the project branch and project version according to the package version.

[0241] When there is no error information sheet corresponding to the error information in the database, or when there is no error information sheet corresponding to the error information in the database and the error information sheet is not closed, the error information tracing device determines the project branch and project version corresponding to the error code based on the package version information in the error information.

[0242] The package version refers to the version of the compiled software package or library.

[0243] Step 1209: extract the file name where the error code is located and the code line number corresponding to the error code.

[0244] After determining the project version and project branch corresponding to the error code, the error information tracing device updates the project library to the corresponding project version and project branch based on the project version and project branch, and finds the source code corresponding to the error code based on the corresponding project version and project branch. The error information tracing device traverses and analyzes the error log, extracts the file name where the error code is located, and the code sequence number corresponding to the error code through regular expressions, and obtains the code location based on the file name and code sequence number.

[0245] Step 1210: Obtain the submitter and submission log.

[0246] After determining the source code and code location corresponding to the error code, the error information tracing device determines the submitter and submission log corresponding to the error code based on the attribution information and code location; the error information tracing device extracts the development requirement sheet corresponding to the error code based on the submission log; the error information tracing device determines the tester corresponding to the error code through the development requirement sheet.

[0247] Step 1211: Create an error message ticket.

[0248] After tracing back the processing personnel information corresponding to the error code, if there is no error information sheet corresponding to the error information in the database, the error information tracing device automatically creates an error information sheet.

[0249] Step 1212: Save the error message to the database.

[0250] After the error information tracing device automatically creates the error information sheet, the error information tracing device saves the error information sheet to a database.

[0251] Step 1213: Scan the reporting time and repair status of the error information sheet.

[0252] After the error information tracing device automatically creates an error information sheet and saves it in a database, the error information tracing device scans the error information sheet in the database to obtain a status parameter corresponding to the error information sheet.

[0253] Status parameters include reporting time and repair status.

[0254] If there is an error information sheet corresponding to the error information in the database and the error information sheet is not closed, the reporting time corresponding to the error information is updated; then the polling state is entered, and the error information tracing device scans the error information sheet in the database to obtain the state parameters corresponding to the error information sheet.

[0255] Step 1214: The error message list is repaired or there is no new one for 7 days.

[0256] When the error code corresponding to the error information sheet has been fixed or the same error information sheet has not been added within 7 days, it is determined that the error code corresponding to the error information sheet has been fixed.

[0257] Step 1215: Close the error message form.

[0258] When it is determined that the error code corresponding to the error information sheet has been repaired, the error information tracing device calls the API interface to close the error information sheet.

[0259] Fig.13 A flowchart of an error tracing method based on game error information applied to a game provided by an exemplary embodiment of the present application is shown. The method can be executed by a computer device, which can be Figure 2 The error information tracing device in the error information tracing device includes the SDK end and the server end.

[0260] The error tracing method based on game error information provided in the embodiment of the present application is applied to games under the test service version or the official service version, but is not limited thereto. The game error information can come from the game client or the game server, which is not specifically limited in the embodiment of the present application. In this embodiment, the game client or the game server is used to provide support for any of the battle royale shooting games, virtual reality games, augmented reality games, first-person shooter games, third-person shooter games, multiplayer online tactical competitive games, and strategy games.

[0261] Step 1301: Collect game error information.

[0262] Game error information is used to indicate the game error description information corresponding to the game error code.

[0263] Exemplarily, the SDK end of the game error information tracing device collects error information corresponding to the game client running the code and / or the game server running the code.

[0264] Game error information includes the error log and code running parameters corresponding to the game error code

[0265] The error log is obtained in the following manner: the SDK end of the error information tracing device obtains the error log by intercepting the error log output by the game client running the code and / or the game server running the code.

[0266] The code running parameters are obtained as follows: the SDK end of the error information tracing device finds the running parameters of the code when it is running in the game client and / or game server based on the error log.

[0267] Step 1302: Deduplication and preservation of game error logs.

[0268] After obtaining the error log, the server of the error information tracing device deduplicates the error log obtained by the SDK, obtains the deduplicated error log and saves it in the database.

[0269] Optionally, the server of the error information tracing device obtains a deduplicated error log by deleting at least one of the time, address, and parameter data in the error log.

[0270] In some embodiments, after the SDK side of the error information tracing device obtains the error log, the server side of the error information tracing device analyzes the error stack data, identifies and removes irrelevant information such as time, address, parameter data, etc. in the error log, and obtains a deduplicated error log, thereby making the extraction of the file name and code serial number of the location of the game error code more convenient and efficient.

[0271] Step 1303: Analyze and trace game error information.

[0272] After the server of the error information tracing device deduplicates the error log, the server parses the game error information to obtain the attribution information and code location corresponding to the game error code. Based on the attribution information and code location, the server traces the person who handled the game error code.

[0273] The attribution information is used to indicate the source code to which the game error code belongs, and the code position is used to indicate the position of the game error code in the source code.

[0274] Optionally, the personnel who have handled the game error code include at least one of a submitter and a tester, but are not limited thereto, and the embodiments of the present application do not make specific limitations on this.

[0275] The submitter is the person who wrote the error reporting code for the game.

[0276] Testers are people who test the game's error code.

[0277] Exemplarily, the server queries and determines the project version and project branch corresponding to the game error code based on the code running parameters; the server determines the source code to which the game error code belongs based on the project version and project branch obtained by the query.

[0278] After determining the source code, the server traverses and analyzes the error log, and uses regular expressions to extract the file name where the game error code is located, as well as the code number corresponding to the game error code. The server obtains the code location based on the file name and code number.

[0279] After determining the source code and code location corresponding to the game error code, the server determines the submitter and submission log corresponding to the game error code based on the source code and code location; the server extracts the development requirement sheet corresponding to the game error code based on the submission log; the server determines the tester corresponding to the error code through the development requirement sheet.

[0280] The development requirement sheet is used to record at least one of the purpose of writing game code, the requirements for writing game code, the standards for testing the game code, and the testers who test the game code, but is not limited to these. The embodiments of the present application do not make specific limitations on this.

[0281] Step 1304: Assign the error report and create a game error information sheet.

[0282] The game error information sheet includes at least one of a game error code, code running parameters, and processing personnel information, but is not limited thereto, and the embodiments of the present application do not make specific limitations on this.

[0283] Exemplarily, after tracing back to the information of the handler corresponding to the error code, if there is no game error information sheet corresponding to the game error information in the database, the server automatically creates a game error information sheet and saves it to the database; if there is a game error information sheet corresponding to the game error information in the database and the game error information sheet is not closed, the reporting time corresponding to the game error information is updated. After obtaining the game error information sheet, the repair task corresponding to the current game error code is sent to the handler, that is, after determining the information of the handler corresponding to the game error code, the current game error code is sent to the handler for repair.

[0284] The status parameters include the last reporting time and repair status of the game error information sheet.

[0285] The repair status refers to whether the game error code corresponding to the game error information sheet has been repaired.

[0286] In some embodiments, the server creates an API interface corresponding to the game error information form and creates a game error information form. The server assigns the API interface to a processing personnel, and the processing personnel can repair the game error code by calling the API interface.

[0287] Step 1305: Scan the game error information sheet and close the game error information sheet.

[0288] The server scans the game error information sheet in the database and obtains the status parameters corresponding to the game error information sheet; if the same game error information sheet is not added within the set time period, it is considered that the game error information sheet has been repaired, and then the API interface corresponding to the game error information sheet is called and the game error information sheet is closed.

[0289] In summary, the method provided in this embodiment obtains the game error information and parses the game error information to obtain the attribution information and code location corresponding to the game error code; based on the attribution information and code location, the person who has handled the game error code is determined. This application realizes the location and tracing of the game error code by parsing the game error information corresponding to the game error code, and can automatically detect the source of the game error code, which not only saves the manpower cost of manually troubleshooting errors, but also speeds up the repair of the game.

[0290] Fig.14 A schematic diagram of the structure of an error tracing device based on error reporting information provided by an exemplary embodiment of the present application is shown. The device can be implemented as all or part of a computer device through software, hardware, or a combination of both. The device includes:

[0291] The acquisition module 1401 is used to acquire the error information, where the error information is used to indicate the error description information corresponding to the error code;

[0292] The parsing module 1402 is used to parse the error information to obtain the attribution information and code position corresponding to the error code, wherein the attribution information is used to indicate the source code to which the error code belongs, and the code position is used to indicate the position of the error code in the source code;

[0293] A determination module 1403 is used to determine information about a person who has processed the error code based on the attribution information and the code position, where the information about the person who has processed the error code refers to information about a person who has processed the error code;

[0294] The sending module 1404 is used to send the error information corresponding to the error code to the processing personnel based on the processing personnel information.

[0295] In some embodiments, the error information includes an error log and code running parameters corresponding to the error code; the parsing module 1402 is used to determine the source code to which the error code belongs based on the code running parameters; based on the error log, determine the code position of the error code in the source code.

[0296] In some embodiments, the parsing module 1402 is used to traverse and analyze the error log, extract the file name where the error code is located, and the code number corresponding to the error code through a regular expression; and obtain the code location based on the file name and the code number.

[0297] The code sequence number refers to the ranking line number of the error code in the source code.

[0298] In some embodiments, the parsing module 1402 is used to determine the project version and project branch corresponding to the error code based on the code running parameters; and determine the source code to which the error code belongs based on the project version and the project branch.

[0299] The engineering branch is used to represent the functional branch corresponding to the error code.

[0300] In some embodiments, the parsing module 1402 is used to send a query instruction to a version control system, wherein the query instruction includes the project version and the project branch; and receive the source code returned by the version control system that matches the query instruction.

[0301] In some embodiments, the determination module 1403 is used to determine the submitter and submission log corresponding to the error code based on the attribution information and the code location; extract the development requirement sheet corresponding to the error code based on the submission log; and determine the tester corresponding to the error code through the development requirement sheet.

[0302] In some embodiments, the sending module 1404 is used to send the error information corresponding to the error code to the processing personnel based on the processing personnel information.

[0303] In some embodiments, the device also includes a management module 1405, which is used to create and save the error information form to the database when there is no error information form corresponding to the error information in the database, and the error information form includes at least one of the error code, the code running parameters and the processing personnel information; scan the error information form in the database to obtain the status parameters corresponding to the error information form, and the status parameters include the reporting time and repair status corresponding to the error information form; if the same error information form is not added within the set time period, call the application programming interface API to close the error information form.

[0304] In some embodiments, the management module 1405 is used to update the reporting time corresponding to the error information when an error information sheet corresponding to the error information already exists in the database and the error information sheet has not been closed; scan the error information sheet in the database to obtain the status parameters corresponding to the error information sheet; and call the API to close the error information sheet when no identical error information sheet is added within the set time period.

[0305] In some embodiments, the device further includes a deduplication module 1406, and the deduplication module 1406 is used to perform deduplication processing on the acquired error log to obtain a deduplicated error log.

[0306] In some embodiments, the deduplication module 1406 is used to delete at least one of the time, address, and parameter data in the error log to obtain the deduplicated error log.

[0307] Fig.15 The structural block diagram of a computer device 1500 shown in an exemplary embodiment of the present application is shown. The computer device can be implemented as the server in the above-mentioned solution of the present application. The image computer device 1500 includes a central processing unit (CPU) 1501, a system memory 1504 including a random access memory (RAM) 1502 and a read-only memory (ROM) 1503, and a system bus 1505 connecting the system memory 1504 and the central processing unit 1501. The image computer device 1500 also includes a large-capacity storage device 1506 for storing an operating system 1509, an application program 1510 and other program modules 1511.

[0308] The mass storage device 1506 is connected to the central processing unit 1501 through a mass storage controller (not shown) connected to the system bus 1505. The mass storage device 1506 and its associated computer readable medium provide non-volatile storage for the image computer device 1500. That is, the mass storage device 1506 may include a computer readable medium (not shown) such as a hard disk or a compact disc read-only memory (CD-ROM) drive.

[0309] Without loss of generality, the computer-readable medium may include computer storage media and communication media. Computer storage media include volatile and non-volatile, removable and non-removable media implemented by any method or technology for storing information such as computer-readable instructions, data structures, program modules or other data. Computer storage media include RAM, Erasable Programmable Read Only Memory (EPROM), Electronically-Erasable Programmable Read-Only Memory (EEPROM) flash memory or other solid-state storage technology, CD-ROM, Digital Versatile Disc (DVD) or other optical storage, cassettes, tapes, disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that the computer storage medium is not limited to the above. The above-mentioned system memory 1504 and mass storage device 1506 can be collectively referred to as memory.

[0310] According to various embodiments of the present disclosure, the image computer device 1500 can also be connected to a remote computer on a network through a network such as the Internet. That is, the image computer device 1500 can be connected to a network 1508 through a network interface unit 1507 connected to the system bus 1505, or the network interface unit 1507 can be used to connect to other types of networks or remote computer systems (not shown).

[0311] The memory also includes at least one computer program, which is stored in the memory. The central processor 1501 implements all or part of the steps in the error tracing method based on error reporting information shown in the above embodiments by executing the at least one program.

[0312] An embodiment of the present application also provides a computer device, which includes a processor and a memory, wherein the memory stores at least one program, and the at least one program is loaded and executed by the processor to implement the error tracing method based on error information provided by the above-mentioned method embodiments.

[0313] An embodiment of the present application also provides a computer-readable storage medium, in which at least one computer program is stored. The at least one computer program is loaded and executed by a processor to implement the error tracing method based on error information provided by the above-mentioned method embodiments.

[0314] An embodiment of the present application also provides a computer program product, which includes a computer program, and the computer program is stored in a computer-readable storage medium; the computer program is read and executed from the computer-readable storage medium by a processor of a computer device, so that the computer device executes to implement the error tracing method based on error information provided in the above-mentioned method embodiments.

[0315] It will be understood that in the specific implementation of the present application, the data involved, historical data, and data related to user data processing such as portraits related to user identity or characteristics, when the above embodiments of the present application are applied to specific products or technologies, need to obtain user permission or consent, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions.

[0316] It should be understood that the "plurality" mentioned in this article refers to two or more. "And / or" describes the association relationship of the associated objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0317] A person skilled in the art will understand that all or part of the steps to implement the above embodiments may be accomplished by hardware or by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, and the above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0318] The above description is only an optional embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent switching, improvements, etc. made within the spirit and principles of the present application shall be included in the protection scope of the present application.

Claims

1. An error tracing method based on error reporting information, characterized in that: The method comprises: Obtain the error information, where the error information is used to indicate the error description information corresponding to the error code; Parse the error information to obtain attribution information and code position corresponding to the error code, wherein the attribution information is used to indicate the source code to which the error code belongs, and the code position is used to indicate the position of the error code in the source code; Determine, based on the attribution information and the code position, information about a person who has handled the error code, wherein the information about the person who has handled the error code; Based on the processing personnel information, the error information corresponding to the error code is sent to the processing personnel.

2. The method according to claim 1, characterized in that The error information includes the error log and code running parameters corresponding to the error code; The parsing of the error information to obtain the attribution information and the code position corresponding to the error code includes: Based on the code running parameters, determining the source code to which the error code belongs; Based on the error log, determine the code position of the error code in the source code.

3. The method according to claim 2, characterized in that The determining, based on the error log, the code position of the error code in the source code includes: Traverse and analyze the error log, and extract the file name where the error code is located and the code number corresponding to the error code through a regular expression; Based on the file name and the code sequence number, obtaining the code position; The code sequence number refers to the ranking line number of the error code in the source code.

4. The method according to claim 2, characterized in that: The determining, based on the code running parameter, the source code to which the error code belongs, includes: Based on the code running parameters, determine the project version and project branch corresponding to the error code; Based on the project version and the project branch, determine the source code to which the error code belongs; The engineering branch is used to represent the functional branch corresponding to the error code.

5. The method according to claim 4, characterized in that The determining the source code to which the error code belongs based on the project version and the project branch includes: Sending a query instruction to a version control system, wherein the query instruction includes the project version and the project branch; The source code matching the query instruction is received and returned by the version control system.

6. The method according to any one of claims 1 to 5, characterized in that: The determining, based on the attribution information and the code position, information of a person handling the error code includes: Based on the attribution information and the code location, determine the submitter and submission log corresponding to the error code; Extracting the development requirement sheet corresponding to the error code based on the submission log; The tester corresponding to the error code is determined through the development requirement sheet.

7. The method according to claim 6, characterized in that The sending the error information corresponding to the error code to the processing personnel based on the processing personnel information includes: Based on the processing personnel information, the error information is sent to at least one of the submitter and the tester to repair the error code.

8. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: If there is no error information sheet corresponding to the error information in the database, create the error information sheet and save it to the database, wherein the error information sheet includes at least one of the error code, the code running parameters and the processing personnel information; Scan the error information sheet in the database to obtain a status parameter corresponding to the error information sheet, wherein the status parameter includes a reporting time and a repair status corresponding to the error information sheet; When the same error message sheet is not added within the set time period, the application programming interface API is called to close the error message sheet.

9. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: If there is an error information sheet corresponding to the error information in the database and the error information sheet is not closed, updating the reporting time corresponding to the error information; Scan the error information sheet in the database to obtain the status parameter corresponding to the error information sheet; If the same error message sheet is not added within the set time period, the API is called to close the error message sheet.

10. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: The obtained error log is deduplicated to obtain a deduplicated error log.

11. The method according to claim 10, characterized in that The step of performing deduplication processing on the acquired error log to obtain a deduplicated error log includes: Delete at least one of the time, address, and parameter data in the error log to obtain the error log after deduplication.

12. An error tracing device based on error reporting information, characterized in that: The device comprises: An acquisition module, used to obtain the error information, where the error information is used to indicate the error description information corresponding to the error code; A parsing module, used to parse the error information to obtain the attribution information and code position corresponding to the error code, wherein the attribution information is used to indicate the source code to which the error code belongs, and the code position is used to indicate the position of the error code in the source code; A determination module, configured to determine information of a person who has processed the error code based on the attribution information and the code position, wherein the information of the person who has processed the error code refers to information of a person who has processed the error code; A sending module is used to send the error information corresponding to the error code to the processing personnel based on the processing personnel information.

13. A computer device, characterized in that: The computer device comprises: a processor and a memory, wherein at least one computer program is stored in the memory, and the at least one computer program is loaded and executed by the processor to implement the error tracing method based on error reporting information as described in any one of claims 1 to 11.

14. A computer storage medium, characterized in that: At least one computer program is stored in the computer-readable storage medium, and the at least one computer program is loaded and executed by the processor to implement the error tracing method based on error reporting information as described in any one of claims 1 to 11.

15. A computer program product, characterized in that The computer program product includes a computer program, which is stored in a computer-readable storage medium; the computer program is read and executed from the computer-readable storage medium by a processor of a computer device, so that the computer device executes the error tracing method based on error reporting information as described in any one of claims 1 to 11.

Images