The `t/integration/preload.t` test is broken on riscv64-linux (1.000155)

Open
#290 3 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
perl
Domain
testing

Research direction

Start with t/integration/preload.t and the failing yath command shown in the report, then inspect the linked full build log for the riscv64-linux failure details. Reproduce the TestSimplePreload and TestPreload subtests on riscv64-linux; done means the integration test passes on that platform.

Written by the indexing model from the issue text.

Description

The following jobs failed:
+------------------------+------------------------+------------------------+
| Job ID                 | Test File              | Subtests               |
+------------------------+------------------------+------------------------+
| 5A30AE1C-9D39-11F0-988 | t/integration/preload. | yath test t/integratio |
| 1-B696224FDDB8         | t                      | n/preload --ext=tx -A  |
|                        |                        | -PTestSimplePreload -P |
|                        |                        | TestPreload            |
+------------------------+------------------------+------------------------+

                                    Yath Result Summary
-------------------------------------------------------------------------------------------
     Fail Count: 1
     File Count: 61
Assertion Count: 1729
      Wall Time: 408.48 seconds
       CPU Time: 1218.76 seconds (usr: 45.87s | sys: 0.63s | cusr: 925.01s | csys: 247.25s)
      CPU Usage: 298%
    -->  Result: FAILED  <--

The full build log:

perl5.40.0-Test2-Harness-1.000155.drv.log

Dominant language
Perl
Stars
28
Forks
30
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Test-More/Test2-Harness

All issues in Test-More/Test2-Harness

Similar issues

More Perl issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.